This page summarizes how the Phenotype2GO-based GO annotations will be handled for the WormBase builds and GO uploads.

Source of Annotations

Phenotype2GO-based annotations are generated as part of the WB build based upon the presence of a phenotype associated with a perturbation of gene activity.
The perturbation may be an RNAi experiment (or a variation).
If the perturbation is an RNAi experiment, we will only associate the GO annotations with phenotypes resulting from disruption of the primary target. Secondary targets will not be used for Phenotype2GO annotations.
All papers will be included in the pipeline (see below for some details on this).
It will be up to Caltech to integrate the annotations into their curation database and perform any necessary QC there.
Phenotype2GO annotations displayed in WB will come from the Caltech .ace file uploaded with each build.

Source of Phenotype2GO Mappings

All mappings between WB Phenotype Ontology and Gene Ontology terms are submitted during the build in a separate .ace file submitted by Ranjana.
No mappings are present in the ?Phenotype objects submitted separately during the build, as this would have the potential to overwrite mappings coming from the GO curators.