Biocurator

Reviewing GO annotations for a gene or protein

To start, check if there are existing annotations to the gene or protein of interest: open a Gene Ontology browser (e.g. AmiGO, QuickGO) and search for the gene or gene protein record of interest by entering it in the 'Search' field, then browse associated annotations and follow links to see the full list of annotations:

Reviewing GO annotations associated with a scientific article

To start, check if there are existing annotations to the paper:  Open a Gene Ontology browser, (e.g. AmiGO, QuickGO) and enter a PubMed identifier (PMID) for the paper of interest in the 'Search' field.

GO Annotation File (GAF) Format 2.1

Annotation data is submitted to the GO Consortium in the form of gene association files, or GAFs. This guide lays out the format specifications for GAF 2.1; for the previous GAF 2.0 file syntax, please see the GAF 2.0 file format guide.

For the first GAF 1.0 file syntax, please see the GAF 1.0 file format guide.

Please see the information on the changes in GAF 2.1.

External Mapping File Format

Mappings of GO have been made to other many other classification systems; a full list is available on the Mappings to GO page. This page describes the format of these files.

Format Specification

The source of the external file is given in the line beginning !Uses: !Uses:http://www.tigr.org/docs/tigr-scripts/egad_scripts/role_reports.spl, 15 aug 2000.

The line syntax for mappings is:

external database:term identifier (id/name) > GO:GO term name ; GO:id

For example:

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.

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

Gene Product Association Data (GPAD) format

The GPAD file is an alternative means of exchanging annotations from the Gene Association File (GAF). The GPAD format is designed to be more normalized than GAF, and is intended to work in conjunction with a separate format for exchanging gene product information.

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

!gpa-version: 1.1