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

[OBA] VT term IRIs redirect to berkeleybop and give 404 error #1018

Closed
krlong68 opened this issue Feb 7, 2025 · 7 comments · Fixed by #1020 or #1023
Closed

[OBA] VT term IRIs redirect to berkeleybop and give 404 error #1018

krlong68 opened this issue Feb 7, 2025 · 7 comments · Fixed by #1020 or #1023

Comments

@krlong68
Copy link

krlong68 commented Feb 7, 2025

The following IRIs give a 404 error:
http://purl.obolibrary.org/obo/OBA_VT0000188
http://purl.obolibrary.org/obo/OBA_VT0001560
http://purl.obolibrary.org/obo/OBA_VT000012

But the following IRIs resolve correctly to Ontobee.
http://purl.obolibrary.org/obo/OBA_2060174
http://purl.obolibrary.org/obo/OBA_2045372

The 404 error page URLs have the following format: http://www.berkeleybop.org/ontologies/OBA_VT4000012

It may also be worth noting that the pages for the VT terms do exist in Ontobee, but the URLs encode the special characters (":", "/") in the IRIs. This is the page for OBA:VT10000188: https://ontobee.org/ontology/OBA?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FOBA_VT0000188

@jamesaoverton
Copy link
Member

Thanks for the report @krlong68.

@cmungall is listed as the contact for OBA here https://obofoundry.org/ontology/oba.html. Chris: I think the problem is that we default to requiring numeric IDs, so to handle "VT" we'll need a custom entry in config/obo.yml. Is that what you want to do?

@matentzn
Copy link
Contributor

matentzn commented Feb 7, 2025

I gave it a shot: #1020

@krlong68
Copy link
Author

Thank you! Just a heads up that I am now noticing a different error with the IRIs for both VT and non-VT terms. They lead to the OLS website successfully, but give a Page Not Found error. I'm again seeing that the special characters in the IRIs within the URLs are encoded, whereas this does not happen in the URLs for terms from some other ontologies. Is this an OLS issue or still related to the IRI redirect?

@jamesaoverton
Copy link
Member

Ok. Please provide some examples, and I’ll look into it.

@jamesaoverton
Copy link
Member

You're right, I made a mistake in PR #1020. Hopefully it's fixed by #1023.

@krlong68
Copy link
Author

Looks good now, thank you!

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