obophenotype / obophenotype/uberon
UBERON:0023867 islands of Calleja of olfactory tubercle, relationship and taxon constraint
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
Dear Uberon Team,
Regarding UBERON:0023867 (islands of Calleja of olfactory tubercle):
relationship: part_of UBERON:0001881 {source="NIFSTD"} ! island of Calleja
relationship: part_of UBERON:0001883 {source="NIFSTD"} ! olfactory tubercle
As far as I understand, the relationship to UBERON:0001881 (island of Calleja) should be is_a rather than part_of.
In addition, it seems that the current relationship structure may, through inference propagation, produce the assertion that:
islands of Calleja of olfactory tubercle part_of nucleus accumbens,
which appears to be incorrect.
To prevent this, I believe that UBERON:0023867 (islands of Calleja of olfactory tubercle) requires a taxon constraint similar to the one already present for UBERON:0001881 (island of Calleja), for example:
relationship: part_of UBERON:0001883 {gci_relation="part_of", gci_filler="NCBITaxon:9989", source="MP"} ! olfactory tubercle
Could you please review whether an appropriate taxon constraint should be added for UBERON:0023867 as well?
Thank you in advance for your help.
Best regards,
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 reviewing the axioms for UBERON:0023867 and comparing them with UBERON:0001881, especially the proposed is_a relationship and taxon constraint. Check whether the current relationships infer a part_of link to the nucleus accumbens; the work is done when the reviewed ontology structure avoids that incorrect assertion.
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
- Mostly clear
- Newbie friendliness
- 50/100