Annotation Conf. Call July 9, 2013: Difference between revisions
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
*** May have to look at cases where there is more than one more granular term to map to | *** May have to look at cases where there is more than one more granular term to map to | ||
* Moving protein binding to its own file. Chris came up with the idea of keeping the protein binding terms in the GO, but | * Moving protein binding to its own file. Chris came up with the idea of keeping the protein binding terms in the GO, but pulling all protein binding annotations from various curation streams into one GAF file. This seems like a good solution that will make both parties happy. | ||
Revision as of 11:03, 9 July 2013
Agenda
QC check for Enzyme binding
- We would like to propose that there shouldn't be any direct annotations to 'enzyme binding' term. We will add a 'not for direct annotation' tag to this term.
Protein oligomerization
Continuing our discussion on Protein oligomerization, we want to bring up some options to curtors.
- Protein di/tri/oligomerization terms: In many cases where the functional unit is a hetero or homo dimer or oligmer, the best option would be to use col-16 to indicate the functional unit using a PRO ID (or other type of complex ID).
- In cases where geneproduct A is involved in the oligomerization of another gene product B, then the appropriate term would protein complex assembly and indicate the complex in col-16.
Protein binding annotations
- Mapping protein binding terms to finer terms. This idea was discussed last year - http://gocwiki.geneontology.org/index.php/Improving_protein_binding_annotations_using_InterPro_domains
- We can look into implementing this. We could provide a mapping file for groups to update their annotations.
- May have to look at cases where there is more than one more granular term to map to
- We can look into implementing this. We could provide a mapping file for groups to update their annotations.
- Moving protein binding to its own file. Chris came up with the idea of keeping the protein binding terms in the GO, but pulling all protein binding annotations from various curation streams into one GAF file. This seems like a good solution that will make both parties happy.