obophenotype / obophenotype/uberon

Classes inherited from AAO needing review

Open
#407 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

phenoscape
Dominant language
Emacs Lisp
Stars
163
Forks
43
Avg merge
1d 17h
Merged PRs (30d)
5

Description

The following are one-word classes from UBERON:3xxx (ie AAO). Whilst not wrong, a one-word label is often a marker. No terms should be adjectives. E.g. "vertebral" should not be the name of a class - this needs merged with vertebral artery. I suspect many or most of these need action

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reviewing the listed UBERON:3xxx classes and their linked OBO entries, then determine the appropriate action for each term, including whether any should be merged or renamed. Done means every listed class has a documented disposition and the ontology reflects the agreed changes.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.