Skip to content
master
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 

README.md

DOI

Build for NCBITaxon Ontology

The NCBITaxon ontology is an automatic translation of the NCBI taxonomy database into obo/owl.

Details

For details on using the ontology, see the OBO page:

http://obofoundry.org/ontology/ncbitaxon.html

This README details with technical aspects of the build

Releases

Outdated, see end of README for updated instructions

Releases of the obo/owl happen when the Continuous Integration Job is manually triggered. Currently this must be done by an OBO administrator. There is currently no fixed cycle, and this is generally done on demand. The team that informally handles this are:

  • James Overton, IEBD/OBO
  • Heiko Dietze, LBNL/GO
  • Frederic Bastian, BgeeDb/Uberon
  • Chris Mungall, LBNL/GO/Monarch/Uberon/OBO
  • Peter Midford, Phenoscape
  • Bill Duncan (LBNL)
  • Nicolas Matentzoglu (EMBL-EBI)

Subsets

Currently there is one subset, ncbitaxon/subsets/taxslim - for details, see subsets/README.md

Licensing

The license for this software is BSD3. See the LICENSE file.

Note that the content of the ontology is not covered by this software license. The content comes from NCBI.

Citing the NCBITaxon ontology

before citing, ask yourself what the artefact you wish to cite is:

  • The NCBI taxonomy database
  • The OBO/OWL rendering of the NCBI taxonomy database

The latter is a fairly trivial translation of the former. If you are in any way citing the contents then you should cite the database. Currently the most up to date reference is:

If you specifically wish to cite the OBO/OWL translation, use the URL for this page

Editors guide for running releases

  1. Trigger the Jenkins Job on ci.monarchinitiative.org
  2. Download all generated files from the Jenkins job (except for env.txt), including the files in the subset directory.
  3. On GitHub, go to Code, and click on releases.
  4. Click "Draft a new release". The tag is something like v2020-02-28. Provide a title and a meaningful description, and upload all the files downloaded from the Jenkins job above. Hit Publish release.
  5. Click "Draft a new release". The tag is should be currentx (note the x). Provide a title and a meaningful description, and upload all the files downloaded from the Jenkins job above. Hit Publish release.
  6. Find the release labeled current: https://github.com/obophenotype/ncbitaxon/releases/tag/current, and delete it.
  7. Click on the release labeled currentx and change the name of the the label from current.

Note: Do not simply delete current and recreate it because this will cause ncbitaxon to be unavailable for as long as you are uploading it. Due to its size, this can be more than an hour!

You can’t perform that action at this time.