guide

SourceForge Links

The GO project pages at the SourceForge site hold information about all of the work currently in progress in the Gene Ontology Consortium.

To submit a request to the Gene Ontology Consortium on any of the subjects shown below, please follow the link corresponding to that subject, and then use the 'Submit New' option.

Trackers for Requests, Suggestions and Comments

GO CVS Repository

Anonymous Access to the GO CVS Repository

Issue the following commands on your machine to create a directory for the GO CVS repository, check out the contents, and update your copy.

user% cd myDirectory

where myDirectory is the directory where you would like to store the GO repository and user% is your command line prompt.

user% mkdir go

Evidence Code Decision Tree

The following flow chart illustrates the steps that a curator typically takes when deciding what evidence code should be applied to an annotation. Please see the evidence code guide for more information on each of the codes.

Annotation Quality Control

The GO Consortium implements a number of automated checks to check the quality of the annotations submitted to the GO database. These checks are detailed on the annotation quality control checks page.

Other File Downloads

References and Evidence Codes

File / Format Download Updated
Database cross-reference list
A list of the abbreviations used by GO in database cross-references.
See also the dbxref Documentation (plain text).
As required

Preparing GO Annotations for Submission

This page documents the steps required to take when supplying Gene Ontology annotations to the GO Consortium (GOC). For general information on how to conduct GO annotations, please see the GO Annotation Policies Guide.

CVS Help

Issue the following commands on your machine to create a directory for the GO CVS repository, check out the contents, and update your copy.

user% cd myDirectory

where myDirectory is the directory where you would like to store the GO repository and user% is your command line prompt.

user% mkdir go

Maintaining complete 'is_a' and 'part_of' trees in cellular component

The cellular component ontology is is_a complete, meaning that every term has a path to the root node which passes solely through is_a relationships. This should be preserved; the following guidelines should help maintain this structure.