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.

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.

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.

Gene Product Information (GPI) Format

Gene Product Information (GPI) format is used to submit gene and gene product information to the GO Consortium. Please note that the GPI companion file for annotation information uses the GPAD file format.

GPI format version

All annotation files must start with a single line denoting the file format. For GPI it is as follows:

!gpi-version: 1.2

GO Qualifiers


Annotation is the process of assigning GO terms to gene products. The annotation data in the GO database is contributed by members of the GO Consortium, and the Consortium is actively encouraging new groups to start contributing annotation. Annotations can be made from published literature where a curator reads and interprets the experiments and results presented in a paper or can be inferred automatically using sequence information or by key word mapping. Details on how to make automatic inferences can be found on the Electronic Annotation page.