Contributing GO annotations
While most GO annotations are produced by members of the GO Consortium, we welcome feedback as well as annotations from the research community.
Suggesting revisions for existing annotations
Researchers who notice either missing or inaccurate annotations for a gene or a GO term can send this information to the GO Consortium.
1. Gather all necessary information
- Literature citation (PMID if available)
- Description of the issue: the gene product and the term combination that you suggest be reviewed and why you believe this is incorrect
- A suggestion for a solution, if possible
2. Communicate with the GO annotation team
- The preferred way is to create tickets in the GO-annotation tracking system. This allows you to monitor the progress on work on the issue and participate in the discussion with GO annotation team members. Instructions about how to create an account and use the GitHub repository can be found here.
- Alternatively, contact the GO helpdesk with your request.
Contributing new GO annotations
Our recommendation for annotating novel genomes is to submit transcripts to NCBI. These submissions will reach UniProt, where InterPro2GO will automatically create high-quality (IEA) GO annotations. These annotations will be made available in a future GO release. GO does not recommend that groups create their own IEAs with internal tools due to reproducibility and accuracy concerns.
Research groups who wish to generate manual GO annotations from experimental data- for instance, new annotations for genes of a species that is not currently annotated in GO, or annotating specific genes for a given biological research domain- can contribute these annotations to the GO knowledgebase. Please contact us early in your project to establish the data exchange process between your group and GO. GO will make sure you have access to the proper documentation and training materials to ensure your annotations meet the GO guidelines.
GO annotation files must be in GAF 2.2 and contain:
- UniProt IDs, or IDs that can be mapped to UniProt, for each annotated entity
- precise & informative valid GO terms for each entity, taking in to account taxon constraints and term restrictions
- PMID of the published literature describing the methods and findings
- a precise evidence code
- other mandatory elements are listed in the GAF 2.2 documentation
Other information, such as mapping files, may be required in addition to the GAF.
Contributing your expertise
The Gene Ontology Consortium welcomes contributions from experts in any area of biology to help us improve the annotations. Contact us to start contributing or improving GO annotations.