These notes are for the EDITORS of duo
This project was created using the ontology starter kit. See the site for details.
For more details on ontology management, please see the OBO tutorial or the Protege Planteome Tutorial
Make sure you have an ID range in the idranges file
If you do not have one, get one from the head curator.
The editors version is duo-edit.owl
** DO NOT EDIT duo.obo OR duo.owl in the top level directory **
[../../duo.owl] is the release version
To edit, open the file in Protege. First make sure you have the repository cloned, see the GitHub project for details.
These are stored in the file
** ONLY USE IDs WITHIN YOUR RANGE!! **
If you have only just set up this repository, modify the idranges file and add yourself or other editors. Note Protege does not read the file
- it is up to you to ensure correct Protege configuration.
We aim to put this up on the technical docs for OBO on http://obofoundry.org/
For now, consult the Protege Planteome Tutorial and look for the section "new entities"
You should only attempt to make a release AFTER the edit version is committed and pushed, and the travis build passes.
to release:
cd src/ontology
make
If this looks good type:
make prepare_release
This generates derived files such as duo.owl and duo.csv and places them in the top level (../..). The versionIRI will be added.
Commit and push these files.
git commit -a
And type a brief description of the release in the editor window
Finally type
git push origin master
IMMEDIATELY AFTERWARDS (do not make further modifications) go here:
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 duo.owl (data-version in duo.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/duo.owl <-- current ontology PURL
- http://purl.obolibrary.org/obo/duo/releases/YYYY-MM-DD.owl <-- change to the release you just made
For questions on this email obo-admin AT obofoundry.org
Check the build status here:
