obophenotype / obophenotype/uberon
Uberon should make use of xrefs in other ontologies
@gouttegd is already working on this.
Since Feb 14, 2023.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
Historically uberon was the only SOT for mappings, but we have not kept the mapping pipelines up to date and there are now sometimes mappings curated in external AOs (e.g. XAO #2796).
We should add a step to include these. I suggest a periodic slurp into the edit file where they will be visible to editors rather than just at release time.
Before doing we should make sure there are checks in place to avoid introducing non 1-1 mappings. The SOP is that if on running a slurp the editor finds these, to raise an issue on either this tracker (if uberon mapping is questionable) or external AO tracker.
This could be done as part of a boomer-like workflow but this is probably overkill.
perhaps the script that generates bridge files for CL can be adapted (in contrast to Uberon, CL treats many upstreams as SOT).
Or it might be easiest to do in OAK. Basically just query the upstream for X-to-Uberon and flip that into
id: UBERON:...
xref: X:....
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.