These notes are for the EDITORS of the Plant Trait Ontology
The release files are:
These are made using the Makefile (see below)
For more details on ontology management, please see the OBO tutorial:
Do you have an ID range in the idranges file (to-idranges.owl), in this directory). If not, get one from the head curator.
The editors version is plant-trait-ontology.obo
** DO NOT EDIT to.obo OR to.owl **
to.obo is the release version
TODO - these are not set up
These are stored in the file
** ONLY USE IDs WITHIN YOUR RANGE!! **
Please see the guide on obofoundry.org
TODO add instructions here
You should only attempt to make a release AFTER the edit version is committed and pushed, and the travis build passes.
to release, change into this directory, and type
make all
This generates derived files such as to.owl and to.obo. The versionIRI will be added.
Commit and push these files to the repository
IMMEDIATELY AFTERWARDS (do not make further modifications) go here:
- https://github.com/Planteome/plant-trait-ontology/releases/
- https://github.com/Planteome/plant-trait-ontology/releases/new
The value of the "Tag version" field MUST be
vYYYY-MM-DD
The initial lowercase "v" is REQUIRED. The YYYY-MM-DD must match what is in the versionIRI of the derived to.owl (data-version in to.obo).
Release title should be YYYY-MM-DD, optionally followed by a title (e.g. "january release")
Then click "publish release"
IMPORTANT: NO MORE THAN ONE RELEASE PER DAY.
The PURLs are already configured to pull from github. This means that BOTH ontology purls and versioned ontology purls will resolve to the correct ontologies. Try it!
- http://purl.obolibrary.org/obo/to.owl <-- current ontology PURL
- http://purl.obolibrary.org/obo/to/releases/YYYY-MM-DD.owl <-- change to the release you just made
For questions on this contact Chris Mungall or email obo-admin AT obofoundry.org
Check the build status here:
This replaces Jenkins for this ontology
See: http://wiki.geneontology.org/index.php/Curator_Guide:_General_Conventions