-
Notifications
You must be signed in to change notification settings - Fork 2
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
VT purl does not point to latest release #3
Comments
@cmungall FYI |
This issue results in an old version VT to be displayed on OLS. |
We experience the same problem with AgroPortal. And I assume BioPortal too. So I would recommend:
|
Sorry for the overlook. Please take a look in the "current_release" folder. Is this something that can work for you as a "stable version"? We will keep files in this location to be up to date. Thank you all! |
Thats perfect! just make sure you keep it updated. Thanks :) |
Good day! I noticed that
https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/vt.yml redirects the VT ontology to the uPheno repo. Your OBO metadata suggests that this repo here is the rightful home of VT, so we should change the above ASAP. One of the consequences is tools like ontobee or OLS which are used to browser are ontologies are not up to date with VT anymore! But basically anyone who is referring to VT by its purl (http://purl.obolibrary.org/obo/vt.owl) is now using an out-of-date version.
https://www.ebi.ac.uk/ols/ontologies/vt
http://www.ontobee.org/ontology/VT
Assuming that this indeed IS the right VT repo, would you want us to redirect the OBO purl here instead? If so, we need you to do one thing (I can take care of the rest): create a file called "vt.owl" somewhere in your repo, for example in a directory called "current release" which you always remember to overwrite when you have a new release. So for example, you want to add VT version 10, you would do as you did so far, and then overwrite the file vt.owl with the VT-10.0.owl file so that we can have a stable url to point to. What do you think? Happy to help.
The text was updated successfully, but these errors were encountered: