obophenotype / obophenotype/uberon
Document SOP for all Uberon curators
Open
@shawntanzk is already working on this.
Since Jun 12, 2022.
documentation issue
Stale
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
- Changes to classifications of terms from the 2x, 3x and 4x range should be reviewed by @cmungall https://github.com/obophenotype/uberon/issues/2514#issue-1258390659
- The higher up you are in the ontology, the more care/oversight required. Changes to the classification of terms higher than leaf nodes and their direct parents should be reviewed by @cmungall
- Don’t trust a term to mean what you expect by the label. Think through implications (make sure you understand the semantic diff, i.e. the new inferred axioms. - if there are many axioms in the diff more care is required)
More to add. We need a general getting started guide for editors which cover some of these secrets.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.