OBOFoundry / purl.obolibrary.org

A system for managing OBO PURLs
BSD 3-Clause "New" or "Revised" License
75 stars 128 forks source link

Update rbo.yml #856

Closed DanBerrios closed 2 years ago

DanBerrios commented 2 years ago

See issue #855. Removes OBO formatted RBO as product. Also updated the URLs for the repo to point to the GH org-hosted URLs instead of my personal GH space URLs (they are redirected already by GH but would rather they show the org).

jamesaoverton commented 2 years ago

The point of PURLs is that they're permanent, so I do not want to just drop the rbo.obo PURL. I suggest keeping it pointed to the older version of the file until the issue is fixed. Is that OK with you?

DanBerrios commented 2 years ago

The problem we are having is that Ontobee will not pick up the latest version of our OWL file from our GH repo and Nico suggested that maybe the yaml entry for the OBO format is the cause, I guess because the version tag in that file does not match the latest version.

jamesaoverton commented 2 years ago

I don't think that having a PURL for rbo.obo can be causing your problem with Ontobee. I merged a version that maintains the old rbo.obo PURL, and I'll follow up with Oliver.

DanBerrios commented 2 years ago

@jamesaoverton Thank you, our database curators rely on the purls working every day, so being without them has caused a lot of inefficiency in their workflows...

jamesaoverton commented 2 years ago

RBO is loaded into OLS: https://www.ebi.ac.uk/ols/ontologies/rbo

If you prefer, you can redirect http://purl.obolibrary.org/obo/RBO_ term IRIs to OLS instead of Ontobee using term_browser: ols. Ontobee is the default, but projects can choose their preferred ontology browser.

matentzn commented 2 years ago

There is no way the OBO purl has anything to do with the update process in ontobee! Something got misunderstood somewhere.