Difference between revisions of "PO Release SOP Page"

From Plant Ontology Wiki
Jump to navigationJump to search
Line 26: Line 26:
  
 
=Preparing ontology files for release:=
 
=Preparing ontology files for release:=
Once the editing and quality checks are completed, four versions of the Plant Ontology file are prepared prior to the release:  
+
Once the editing and quality checks are completed, the following versions of the Plant Ontology file are prepared prior to the release:  
 
* plant_ontology.obo
 
* plant_ontology.obo
 
* plant_ontology_assert.obo
 
* plant_ontology_assert.obo
 
* plant_ontology_assert_basic.obo
 
* plant_ontology_assert_basic.obo
 +
* po_anatomy.obo
 +
* po_temporal.obo
  
 
see: [http://palea.cgrb.oregonstate.edu/viewsvn/Poc/tags/live/Readme.txt?view=markup readme file] for description of each
 
see: [http://palea.cgrb.oregonstate.edu/viewsvn/Poc/tags/live/Readme.txt?view=markup readme file] for description of each
  
 +
Prior to the release, these files will be copied (moved?) over to the "beta" branch of the svn
  
 +
 +
 +
 +
In addition we also create an OWl version:
 
* plant_ontology.owl  
 
* plant_ontology.owl  
  

Revision as of 17:44, 6 October 2011

This page is a place to list all the steps we need to take for the database releases.

Let's not reinvent the wheel every 4 months. Under constr low.gif

Ontology quality control

Checks done by ontology editors

Before each release, ontology editors should run some qc checks. In fact, these should be done one a regular basis in between releases, but it is crucial to do them immediately before a release.

  • Run the reasoner to remove any redundant links.
  • Do a search for extra space and odd characters in terms, definitions, and dbxrefs.

Checks done by the IT team

  • Get any broken dbxrefs working and fixed
  • Check for any lines in the existing association files that reference obsolete or alternate IDs.

Internal and external reviews

Once we have completed the editing, the Ontology should be open for review- could use Dev browser (no annotations) or Beta (with annotations)

Preparing ontology files for release:

Once the editing and quality checks are completed, the following versions of the Plant Ontology file are prepared prior to the release:

  • plant_ontology.obo
  • plant_ontology_assert.obo
  • plant_ontology_assert_basic.obo
  • po_anatomy.obo
  • po_temporal.obo

see: readme file for description of each

Prior to the release, these files will be copied (moved?) over to the "beta" branch of the svn



In addition we also create an OWl version:

  • plant_ontology.owl


Different working versions of these files are kept at http://palea.cgrb.oregonstate.edu/viewsvn/Poc/trunk/ontology/OBO_format/ and http://palea.cgrb.oregonstate.edu/viewsvn/Poc/trunk/ontology/OWL_format/.

When the files are ready for live release, they are transferred to http://palea.cgrb.oregonstate.edu/viewsvn/Poc/tags/live/.

"Summary of Changes" page

  • During the time between the releases, while we are editing the ontology, we will create a page (or pages) to keep track of the changes being made

For example: see October_2011_Release_Page this has links to the "Summary of Changes" page, e.g.: Summary of Changes to PO October 2011

  • Also should list terms that have been merged, changed definitions, or renamed.
  • If possible, it is also good to list new synonyms for existing terms, especially if those synonyms are quite different from the original name. For example, we would want to highlight the cone is a synonym of strobilus, but it is not that important to note that portion of epidermal tissue is a synonym for epidermis.

Announcements

  • Prepare and post announcements for the PO front page, Jaiswal Lab Page
  • Send out announcements to the mailing lists