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

Migrate remaining obo format ontologies from dependency on central OBO build #1446

Open
1 of 4 tasks
cmungall opened this issue Feb 23, 2021 · 9 comments
Open
1 of 4 tasks
Assignees
Labels
attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools pipeline Issues related to development or revision of global Foundry pipelines

Comments

@cmungall
Copy link
Contributor

cmungall commented Feb 23, 2021

Original ticket #290

Documentation: http://obofoundry.org/faq/what-is-the-build-field.html

Also: http://www.obofoundry.org/principles/fp-002-format.html Note: some groups publish an .obo version, and the OBO Foundry pipeline takes care of making the valid .owl file. See the FAQ for details. You may also submit the ontology for review as OBO, see ‘criteria for review’ below.

This central job is no longer running. This means that the OWL for some ontologies is lagging behind what the provider intends with their provided obo format version.

We could restart the build, but we think it may be better to get groups set up with providing the OWL themselves. Now with github actions and ODK it should be easier to do this. There is still the concern that many of these groups (e.g model organism communities) may have no technical resources, but we would potentially do this just with PRs in their ontologies

  • update http://obofoundry.org/faq/what-is-the-build-field.html to say this no longer runs
  • find list of ontologies that rely on this
  • work with each such that they are providing owl themselves
  • clarify fp-002- such that it is clear each group is responsible for providing their own OWL
@cmungall cmungall added the attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools label Feb 23, 2021
@cmungall cmungall self-assigned this Feb 23, 2021
@matentzn
Copy link
Contributor

matentzn commented Feb 23, 2021

UPDATED 8 July 2023:

Quick analysis of the main purl (owl) redirects, if this helps:

Out of 186 active ontologies

  • 137 raw.github to master/main
  • 13 raw.github branch/tag (not master) - see below
  • 6 github raw - alternative syntax
  • 13 Old Berkley Server - see below <- THESE NEED FIXING!
  • 18 Github releases (latest)
  • 9 other

Purls to raw.github branch/tag:

https://raw.githubusercontent.com/BFO-ontology/BFO/v2019-08-26/bfo_classes_only.owl -- bfo
https://raw.githubusercontent.com/biobanking/biobanking/v2023-04-05/obib.owl -- obib
https://raw.githubusercontent.com/infectious-disease-ontology/infectious-disease-ontology/2017-11-03/ido.owl -- ido
https://raw.githubusercontent.com/information-artifact-ontology/IAO/v2022-11-07/iao.owl -- iao
https://raw.githubusercontent.com/ISA-tools/stato/dev/releases/latest_release/stato.owl -- stato
https://raw.githubusercontent.com/monarch-initiative/GENO-ontology/develop/geno.owl -- geno
https://raw.githubusercontent.com/obi-ontology/obi/v2023-03-10/obi.owl -- obi
https://raw.githubusercontent.com/OHMI-ontology/OHMI/v2019-09-17/ohmi.owl -- ohmi
https://raw.githubusercontent.com/OmniSearch/ncro/release-2015-12-10/build/ncro-all-in-one.owl -- ncro
https://raw.githubusercontent.com/OPL-ontology/OPL/v2023-06-23/opl.owl -- opl
https://raw.githubusercontent.com/safisher/ornaseq/2019-07-08/ornaseq.owl -- ornaseq
https://raw.githubusercontent.com/SED-ML/KiSAO/deploy/kisao.owl -- kisao
https://raw.githubusercontent.com/VEuPathDB-ontology/VEuPathDB-ontology/2023-05-30/eupath.owl -- eupath

Alternative github raw notation

https://github.com/allysonlister/swo/raw/master/swo.owl -- swo
https://github.com/AnimalGenome/vertebrate-trait-ontology/raw/master/current_release/vt.owl -- vt
https://github.com/CTDbase/exposure-ontology/raw/master/exo.owl -- exo
https://github.com/flora-phenotype-ontology/flopoontology/raw/master/ontology/flopo.owl -- flopo
https://github.com/obophenotype/ascomycete-phenotype-ontology/raw/master/apo.owl -- apo
https://github.com/terms4fairskills/FAIRterminology/raw/master/t4fs.owl -- t4fs

berkeleybop.org server:

Remaining

Migrated (August 2023):

Rest

https://gitlab.com/fortunalab/ontoavida/-/raw/master/ontoavida.owl -- ontoavida
https://gitub.u-bordeaux.fr/erias/fideo/-/raw/master/fideo.owl -- fideo
https://proconsortium.org/download/current/pro_reasoned.owl -- pr
http://www.informatics.jax.org/downloads/reports/mp.owl -- mp
https://bitbucket.org/hegroup/ogg/raw/master/ogg-merged.owl -- ogg
https://download.rgd.mcw.edu/ontology/clinical_measurement/clinical_measurement.owl -- cmo
http://current.geneontology.org/ontology/go.owl -- go
http://ftp.ebi.ac.uk/pub/databases/chebi/ontology/chebi.owl -- chebi
http://vertebrate-taxonomy-ontology.s3-website-us-west-2.amazonaws.com/releases/vto.owl -- vto

@matentzn
Copy link
Contributor

matentzn commented Feb 23, 2021

Code snippet to get the redirects:

import requests
import yaml
import urllib.request
with urllib.request.urlopen("http://obofoundry.org/registry/ontologies.yml") as data:
    obo_data = yaml.safe_load(data)
    
for o in obo_data['ontologies']:
    oid = o['id']
    if o['activity_status']=="active":
            purl = f"http://purl.obolibrary.org/obo/{oid}.owl"
            r = requests.get(purl, allow_redirects=False)
            url = r.headers['Location']
            print(f"{url}||{oid}")

matentzn added a commit to OBOFoundry/purl.obolibrary.org that referenced this issue Feb 23, 2021
matentzn added a commit to OBOFoundry/purl.obolibrary.org that referenced this issue Feb 23, 2021
Unifying raw.github redirect see OBOFoundry/OBOFoundry.github.io#1446
matentzn added a commit to OBOFoundry/purl.obolibrary.org that referenced this issue Feb 23, 2021
Unifying git release links, see OBOFoundry/OBOFoundry.github.io#1446
matentzn added a commit to OBOFoundry/purl.obolibrary.org that referenced this issue Feb 23, 2021
matentzn added a commit to OBOFoundry/purl.obolibrary.org that referenced this issue Feb 23, 2021
@nlharris nlharris added the pipeline Issues related to development or revision of global Foundry pipelines label Apr 20, 2021
@nlharris
Copy link
Contributor

This came up during today's OFOC call. Looks like it's mostly done?

@matentzn
Copy link
Contributor

Not by a longshot, but @balhoff s idea with #1577 will help speed this up.

@matentzn
Copy link
Contributor

matentzn commented Jul 8, 2023

Update 2 years later: 13 ontologies left to redirect. Action item for the next person coming across this issue:

  • Contact all 13 ontologies to update their PURL config (tell them how)

@matentzn
Copy link
Contributor

matentzn commented Aug 18, 2023

@fbastian considers deprecating olatdv and pdumdv

EDIT: these were set to inactive.

@matentzn
Copy link
Contributor

Today, I contacted

Petra Fey <pfey northwestern.edu>,
bgee@sib.swiss,
Terry Hayamizu <Terry.Hayamizu jax.org>,
"Smith, Jennifer" <jrsmith mcw.edu>,
gthayman mcw.edu,
sjwang mcw.edu,
ramirez macn.gov.ar,
Yvonne Bradford <ybradford zfin.org>

Via email:

Dear ontology maintainers (ddanat, hom, ma, mmo, pw, rs, spd, xco, zfs)!

We have a long-standing issue of ontologies with stale OWL products: 

https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1446

This means that for quite a few years, your ontologies have been stale (never updated) in OBOs primary dependency system, which relies on this PURL: http://purl.obolibrary.org/obo/ID.owl, e.g. http://purl.obolibrary.org/obo/ddant.owl. 

Would you be able to either email me the location of your correct OWL files, or update the purl config yourself, e.g. https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/zfa.yml?

Feel free to reach out to me if you have problems or questions, we can provide people to support you.

All best,
Nico (OBO Operations Committee)

@nlharris
Copy link
Contributor

nlharris commented Mar 1, 2024

Is this still in progress?

@matentzn
Copy link
Contributor

matentzn commented Mar 1, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools pipeline Issues related to development or revision of global Foundry pipelines
Projects
None yet
Development

No branches or pull requests

3 participants