samanthacsik
commented
3 years ago Just gathering some useful resources to draw inspiration from (ENVO has some really well defined protocols for contributors). I see a few different options, though we may want to provide a couple different ways for editors to contribute depending on their level of familiarity (with Protégé, formalized ontology development, etc.) and the number of terms requested.
Option 1: Request that a small number of terms (e.g. one or few terms) be added as an Issue
- We will need to provide a structured template (I'm envisioning something like the metacatui Bug Report Issue template for any necessary information (e.g. term label, definition, dbXref/source, parent class, comment, etc.) regarding the requested term.
Option 2: Ask contributors to use GitHub's fork-and-pull approach
-
This may be appropriate for contributors who already have familiarity with Protege/formal ontology development and who may want to add many terms. Opening a line of communication/discussion via a GitHub issue prior to submitting a PR is likely important. See ENVO's Steps for contributions by non-editors for well-detailed steps.
-
NOTE: This would also require that we have a detailed description of our design pattern for contributors to follow.
Option 3: Provide a .csv template, which we can ingest into Protégé
- See ENVO's Robot template & tutorial or Protégé's Cellfi plugin as two potential options to explore.
mbjones
We need a model for how people can contribute new terms to the salmon ontology, and how we review and vet those for inclusion in a new release of the ontology. This could be as simple as a CONTRIBUTING.md file modeled on our existing ones from other repositories.