Afternoon

• putting cwl tools with shared jupyter notebooks
• Malte wants to extract which paragraph describes which model
• Rennie: a taxonomy builder would be useful (or at least documentation about how to create taxonomies)
• Robert: usecase descriptions of taxonomy development would be good for that
• mandala.shanti.virginia.edu is an example of how to build flexible taxonomies and uses a tool for linking audio files with transcriptions (and every interview has location attached)
• Ulrike: tmf could benefit from modularization → workflow language (cwl)
• eveline: might be relevant: digilib, GIles, Quadriga, Jupyter Notebooks with Dataverse
• crystal: how to balance building up infrastructure and taxonomy for research question with changing research question?
• crystal: how do you test your prototypes? pay undergrads, in a class setting, ...
• Rennie: could we develop a standard for (tool) documentation?
• Julia: could we start a list of tools that we know are maintained with a brief description what they do?
• Carsten: 
  • CLARIAH-NL has guidelines for documentation → https://github.com/CLARIAH/software-quality-guidelines
  • Berlin conference on Software Sustainability in October https://calenda.org/411096
  • Recommendations to encourage best practices in research software: https://softdev4research.github.io/recommendations/
• Rennie: we have documentation example and will share link : https://wiki.shanti.virginia.edu/display/KB/Home
  • also happy to collaborate with tool owners to write and house documentation–please contact rcm7e@virginia.edu
• Netherlands eScience Center Software Development and Project Guide

Future collaboration

• organize a session at next DH conference
• organize a meeting at UVa
• create Slack channel
• blog with updates
• create github organization with a repo with list of tools
• link to best practices guidelines
• one day a month everybody commits to being on Slack (first Monday of every month)
• create mission statement in the GitHub organization