obophenotype / obophenotype/uberon
obsolete processual entity still classified under occurrent
Open
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
Bug description
As the issue is only on the full uberon, it might be coming from an import, as this term has been used by many ontologies, see list in ontobee.
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.
Research direction
Start by inspecting Uberon term UBERON_0000000 in the full Uberon release and comparing it with the imported source ontologies listed through Ontobee. Trace which import supplies the obsolete processual classification and confirm what classification the release should contain.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100