Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Inject web page link into header & Document differences to UMLS/BioPortal rendering #50

Open
cmungall opened this issue Dec 16, 2020 · 1 comment

Comments

@cmungall
Copy link
Member

We have this page on the obo rendering, where we have tried to make this as transparent as possible, but always room for improvement:

http://obofoundry.org/ontology/ncbitaxon

I think we at least need to make clear on this page that there is a separate bioportal/UMLS rendering. And we should document differences in content, PURLs, and release cycle.

We also need to inject metadata into the header that links to this page. Someone landing here:
https://www.ebi.ac.uk/ols/ontologies/ncbitaxon

is none the wiser that they are looking at a specific OBO rendition

I like how on the bioportal page it's (more or less) clear that this comes from UMLS
http://bioportal.bioontology.org/ontologies/NCBITAXON

However, there is a lot that is undocumented on both sides. For example, Bioportal/UMLS excludes non-organismal metagenome entries, excludes the fake 'root' class; OBO has a faithful rendering of every NCBI taxonomy ID. There are pros and cons of both approaches.

@cmungall
Copy link
Member Author

oh I see there is a similar ticket here: OBOFoundry/OBOFoundry.github.io#1383

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant