Annotation Conf. Call 2017-10-24: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 37: Line 37:
** Review use of contributes_to and colocalizes_with  
** Review use of contributes_to and colocalizes_with  
** Noctua into full production mode
** Noctua into full production mode
** Representation of protein complexes, and their constituent members, in GO
** Representation of protein complexes, and their constituent members, in GO and GO-CAM models
*** [https://github.com/geneontology/go-annotation/issues/1662 inferring MFs from annotations to complex portal IDs to individual complex participants]
***[https://github.com/geneontology/go-annotation/issues/1661 Protein complex representation in Noctua]


= Minutes =  
= Minutes =  

Revision as of 14:08, 23 October 2017

Meeting URL

Agenda

Annotation QC

  • Manual annotation to uninformative high-level terms is strongly discouraged
    • See: improving specificity by banning high level terms #1648
    • For example: direct annotation to 'transport' (GO:0006810) is one case where a more specific annotation can likely be made
    • In AmiGO, there are 53 experimentally supported annotations to 'transport'.
    • Can groups check these annotations to see if a more granular term is appropriate?
    • Annotations according to group:
 (8) EcoCyc
 (7) EcoliWiki
 (7) MGI
 (7) PseudoCAP
 (6) SGD
 (5) UniProt
 (4) BHF-UCL
 (3) RGD
 (3) TAIR
 (2) GR
 (1) SynGO
  • PomBase has a list of >1300 high-level terms that have a 'do not manually annotate' flag
  • The proposal is to work through this list so annotations are consistent amongst all GOC members

Ontology Updates

GOC Meetings Cambridge

Minutes

  • On call: