Skip to content

Redirect NCBITaxon PURLs to official NCBI site#1066

Merged
jamesaoverton merged 1 commit intomasterfrom
ncbitaxon
Dec 12, 2025
Merged

Redirect NCBITaxon PURLs to official NCBI site#1066
jamesaoverton merged 1 commit intomasterfrom
ncbitaxon

Conversation

@jamesaoverton
Copy link
Copy Markdown
Member

@jamesaoverton jamesaoverton commented Nov 20, 2025

Resolves #1010 from obophenotype/ncbitaxon#117

I found this issue at the bottom of my inbox and decided to finally take care of it.

Note that there are non-numeric IDs for ranks and stuff in NCBITaxon, some using # fragments. I think that none of them ever resolved. Most were replaced by TAXRANK terms. If someone wants to do a forensic analysis of this, be my guest.

Copy link
Copy Markdown
Contributor

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

Copy link
Copy Markdown
Contributor

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jamesaoverton
Copy link
Copy Markdown
Member Author

Interesting. I'd never seen those before.

@lubianat
Copy link
Copy Markdown

just to mention that either look great & better than current :)

I tried to resolve a NCBITaxon term now and it took several minutes for the Ontobee page to resolve.

https://www.ncbi.nlm.nih.gov/datasets/taxonomy/9606/ looks really clean (both page and URI), so I'd vote for that

@jamesaoverton
Copy link
Copy Markdown
Member Author

I would like to hear from @cmungall and @anitacaron before proceeding with this.

@anitacaron
Copy link
Copy Markdown
Contributor

anitacaron commented Dec 11, 2025

The new pages look great, but I've noticed that the definitions are not part of the set of files that we use to generate the OBO version; the information for the new page is coming from other files. The images are not the same either. I don't know whether this will affect the terms of the OBO release, like a discrepancy between the terms available or not.

@anitacaron
Copy link
Copy Markdown
Contributor

What about this 'about' prefix?

- prefix: /about/
  replacement: http://www.ontobee.org/browser/rdf.php?o=NCBITaxon&iri=http://purl.obolibrary.org/obo/
  tests:
  - from: /about/NCBITaxon_1
    to: http://www.ontobee.org/browser/rdf.php?o=NCBITaxon&iri=http://purl.obolibrary.org/obo/NCBITaxon_1

@matentzn
Copy link
Copy Markdown
Contributor

The new pages look great, but I've noticed that the definitions are not part of the set of files that we use to generate the OBO version; the information for the new page is coming from other files. The images are not the same either. I don't know whether this will affect the terms of the OBO release, like a discrepancy between the terms available or not.

Interesting @anitacaron - in this case, we should probably go with the reference to the old pages and do a thorough investigation first..

Copy link
Copy Markdown
Contributor

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given @anitacaron observations of various discrepancies on the new site I think we need a more prinicpled investigation if we can link to that safely.

@jamesaoverton
Copy link
Copy Markdown
Member Author

@anitacaron I figured that we would leave the /about/ unchanged.

What definitions are you referring to? Things like "Human (Homo sapiens) is a species of primate in the family Hominidae (great apes)." I bet those are generated automatically using a handful of patterns.

@anitacaron
Copy link
Copy Markdown
Contributor

@jamesaoverton I think so too, but they're not sharing, at least I couldn't find the generated definition.

@jamesaoverton
Copy link
Copy Markdown
Member Author

@anitacaron I think that you're saying that we should not use the new pages because they have automatically generated textual definitions, but I don't understand why that's a problem.

@anitacaron
Copy link
Copy Markdown
Contributor

@jamesaoverton, the OBO release artefacts don't have the definitions shown on that page.

@jamesaoverton
Copy link
Copy Markdown
Member Author

@anitacaron That's true. But why is it a problem?

@jamesaoverton jamesaoverton merged commit 2622062 into master Dec 12, 2025
1 check passed
@jamesaoverton jamesaoverton deleted the ncbitaxon branch December 12, 2025 16:05
@jamesaoverton
Copy link
Copy Markdown
Member Author

I merged this. It changes NCBITaxon redirects from Ontobee to the old NCBI Taxonomy pages. I guess well change to the new NCBI Taxonomy pages at some point -- someone else can take care of that.

candleindark pushed a commit to dandi/dandi-cli that referenced this pull request Dec 16, 2025
…DF representation on Ontobee

obolibrary changed the redirection target of a PURLs
identifying an entity on NCBITaxon from an RDF
representation on Ontobee to an HTML representation
on the NIH official site as of
OBOFoundry/purl.obolibrary.org#1066.
Our logic requires the representations to be RDF, so
we are redirecting the affected PURLs to the
corresponding RDF representation manually.
candleindark pushed a commit to dandi/dandi-cli that referenced this pull request Dec 16, 2025
…DF representation on Ontobee

obolibrary changed the redirection target of a PURLs
identifying an entity on NCBITaxon from an RDF
representation on Ontobee to an HTML representation
on the NIH official site as of
OBOFoundry/purl.obolibrary.org#1066.
Our logic requires the representations to be RDF, so
we are redirecting the affected PURLs to the
corresponding RDF representation manually.
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

Successfully merging this pull request may close these issues.

[NCBITaxon] Use custom browser term

5 participants