Annotation Conf. Call 2017-10-24: Difference between revisions
Jump to navigation
Jump to search
Line 30: | Line 30: | ||
== GOC Meetings Cambridge == | == GOC Meetings Cambridge == | ||
*Review key action items from signaling workshop and GOC meeting | *Review key action items from signaling workshop and GOC meeting | ||
** Focus on annotation to signaling pathways | |||
** Adoption of expanded set of BP relations | |||
** Review use of contributes_to and colocalizes_with | |||
** Noctua into full production mode | |||
= Minutes = | = Minutes = |
Revision as of 13:43, 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
- Molecular Function terms describing 'transcription factors' - Pascale
- See: Make parent term for transcription factor activity
GOC Meetings Cambridge
- Review key action items from signaling workshop and GOC meeting
- Focus on annotation to signaling pathways
- Adoption of expanded set of BP relations
- Review use of contributes_to and colocalizes_with
- Noctua into full production mode
Minutes
- On call: