Thanks @chris-grove, we'll work to make this more clear. Let me know if the following makes sense:
Every OBO ontology has an OBO registry file in the ontology/ directory of this GitHub repository. I think you're specifically interested in ontology/wbphenotype.md. That page has an Edit button with a pencil icon, which takes you to this editing interface where you can update the entry. When you're done, you add a description of your change at the bottom under "Commit changes", select "Create a new branch...", and click "Propose file change". This will make a Pull Request that will be checked by our technical people, then merged.
To pass the specific Plurality of Users check, wbphenotype.md needs a tracker field, like this:
Note that this fix won't be reflected in the dashboard until we rebuild it. Currently we're rebuilding on an ad hoc basis, but we plan to rebuild on a regular scheduled.
There is now a process for this:
Thanks @chris-grove, we'll work to make this more clear. Let me know if the following makes sense:
Every OBO ontology has an OBO registry file in the ontology/ directory of this GitHub repository. I think you're specifically interested in ontology/wbphenotype.md. That page has an Edit button with a pencil icon, which takes you to this editing interface where you can update the entry. When you're done, you add a description of your change at the bottom under "Commit changes", select "Create a new branch...", and click "Propose file change". This will make a Pull Request that will be checked by our technical people, then merged.
To pass the specific Plurality of Users check, wbphenotype.md needs a tracker field, like this:
tracker: https://github.com/obophenotype/c-elegans-phenotype-ontology/issues This process is explained more fully here. But if you haven't done it before, it's a lot to take in at one time.
Note that this fix won't be reflected in the dashboard until we rebuild it. Currently we're rebuilding on an ad hoc basis, but we plan to rebuild on a regular scheduled.