GO annotation fields required for correct display
GO annotations are most completely represented by the gene association file format used by GO Consortium members, detailed here.
However, for a web-based display of annotation data it is understandable when groups to decide to restrict their display to the most essential and useful GO annotation fields required by their users. However, we would ask that such displays do include the mininimal fields which are essential to be able to properly interpret a GO annotation statement.
Column No. | Column Name | Requirement | Further Detail |
---|---|---|---|
1. | DB | Optional | |
2. | DB_Object_ID | Essential | can be mapped to corresponding sequence identifiers |
3. | DB_Object_Symbol | Optional | |
4. | Qualifier | Essential | Notably annotations using the 'NOT' qualifier |
5. | GO term ID and/or name | Essential | |
6. | DB:Reference | Essential? Recommended? | this is an integral part of the annotation format. Without the reference, the annotation becomes untraceable and causes problems for users of the displayed annotation set who would like to verify the statement |
7. | Evidence | Essential | |
8. | With(or)From | Recommended | Provides important supporting information, especially required to add meaning to annotations describing interactions |
9. | Aspect | Optional | |
10. | DB_Object_Name | Optional | |
11. | DB_Object_Synonym | Optional | |
12. | DB_Object_Type | Optional | |
13. | Taxon | Optional | |
14. | Date | Recommended | |
15. | Assigned_by | Essential | |
16. | Annotation Extension | Optional | |
17. | Gene Product Form ID | Optional |
COMMENTS
In addition, should external websites be encouraged to provide a link to the GO Consortium? Rachael
Also suggest that if external websites would like to be notified of any changes to these recommendations, then to send us an email? We would then be able to build up a picture of who displays our annotations, which may be useful for grant reporting purposes. Edimmer 11:12, 2 February 2011 (UTC)