-
Notifications
You must be signed in to change notification settings - Fork 206
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
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
added
the
attn: Technical WG
Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools
label
Feb 23, 2021
Code snippet to get the redirects:
|
matentzn
added a commit
to OBOFoundry/purl.obolibrary.org
that referenced
this issue
Feb 23, 2021
unifying raw.github urls see OBOFoundry/OBOFoundry.github.io#1446
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
added
the
pipeline
Issues related to development or revision of global Foundry pipelines
label
Apr 20, 2021
This came up during today's OFOC call. Looks like it's mostly done? |
Update 2 years later: 13 ontologies left to redirect. Action item for the next person coming across this issue:
|
@fbastian considers deprecating olatdv and pdumdv EDIT: these were set to inactive. |
Today, I contacted
Via email:
|
Is this still in progress? |
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
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
The text was updated successfully, but these errors were encountered: