obophenotype / obophenotype/uberon

Identify all proxy merges (mappings) and make issues on external ontology trackers

Open
#2,834 8 comments 0 reactions 1 assignee View on GitHub

@matentzn is already working on this.

Since Mar 12, 2023.

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

Description

We have a bunch of cases like:

Uberon:nerve --[sempav:crossSpeciesExactMatch]--> Xenopus:nerve 
Uberon:nerve --[sempav:crossSpeciesExactMatch]--> Xenopus:peripheral_nerve

This means that an external ontology considered two concepts distinct that Uberon believes are the same.

As @cmungall commented in #2833, we should probably review these proxy merges and make issue tracker items for all of these, encouraging the external ontologies (like in this case XAO) to merge the terms.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.