Ontology publishing pipeline 2009 (Archived): Difference between revisions

From GO Wiki
Jump to navigation Jump to search
(New page: The current publishing pipeline essentially copies the gene_ontology_write.obo file to the public area, and then runs obo2obo in order to generate the legacy obof1.0 and go files. See...)
 
Line 1: Line 1:
The current publishing pipeline essentially copies the [[gene_ontology_write.obo]] file to the public area, and then runs obo2obo in order to generate the legacy obof1.0 and go files. See [[Ontology CVS Directory Layout Overhaul 2007]]
The current publishing pipeline essentially copies the [[gene_ontology_write.obo]] file to the public area, and then runs obo2obo in order to generate the legacy obof1.0 and go files. See [[Ontology CVS Directory Layout Overhaul 2007]]


Line 22: Line 21:


The following steps should be identical to the existing pipeline. See [[Ontology CVS Directory Layout Overhaul 2007]]
The following steps should be identical to the existing pipeline. See [[Ontology CVS Directory Layout Overhaul 2007]]
== Step 3 : publish legacy GO files ==
1_0.obo and .ontology files

Revision as of 15:35, 27 January 2009

The current publishing pipeline essentially copies the gene_ontology_write.obo file to the public area, and then runs obo2obo in order to generate the legacy obof1.0 and go files. See Ontology CVS Directory Layout Overhaul 2007

With the addition of new inter-ontology relations in the core GO, we decided we needed to introduce a buffer to insulate ontology file consumers from these kinds of new changes.

Step 1 : publish editors version as GO-ext (extended GO)

This step is a simple cp of gene_ontology_write.obo to ontology/obo_format_1_2/gene_ontology_ext.obo

(alternatively we could use obo2obo)

Step 2 : filter GO-ext and publish in usual place

This involves a new script that will filter out inter-ontology links and also intra-MF regulates links.

The script currently lives at scratch/regulates_xp_live/obol-remove-inter-ontology-link.pl (its location could be changed)

we will need a cron that executes:

 obol-remove-inter-ontology-link.pl ontology/obo_format_1_2/gene_ontology_ext.obo > ontology/obo_format_1_2/gene_ontology.1_2.obo.tmp &&\
 mv ontology/obo_format_1_2/gene_ontology.1_2.obo.tmp ontology/obo_format_1_2/gene_ontology.1_2.obo

The following steps should be identical to the existing pipeline. See Ontology CVS Directory Layout Overhaul 2007

Step 3 : publish legacy GO files

1_0.obo and .ontology files