2012 Annotation Meeting Stanford: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
 
(108 intermediate revisions by 12 users not shown)
Line 1: Line 1:
=Agenda=
=Agenda=
==Goals==
==Preparation/Goals for the meeting ==
GO annotations are the primary product of the GO and curator time is our most valuable resource: we need a defined process for how they will be produced efficiently and at high quality.
[[Over all goals for the meeting are available here ]]
* Overall objective: to briefly review the existing GO annotation streams, and delve into how we can make GO annotations better, faster.
* We will define new processes to identify and set annotation goals by production numbers and by domain coverage.
** rate of production by annotation:  # of annotations/quarter (ACTION ITEM: pick a realistic GOAL for increasing this # over the next 5 years)
** rate of production by domain:  # of domain evaluations / quarter (ACTION ITEM: pick a goal for first quarter and evaluate for future goals)
** rate of refinement:  increase in information content/year (ACTION ITEM: pick a realistic GOAL for increasing this # over the next 5 years)
** quality standards and metrics:  minimal requirements for community contributions (ACTION ITEM: publishing these requirements)
** what additional information shall we aim to collect to enrich the annotations coming from GO funded efforts (ACTION ITEM: List of new data types in relation to existing annotation)
* We will review and evaluate the current components of a process
** what are the current bottlenecks (ACTION ITEM: list of areas we need to address)
** what changes will we make in our process to eliminate bottlenecks and improve quality (ACTION ITEM: a prioritized list of these steps to work on over the next 3 months)
** what changes will we make to our data flow (ACTION ITEM: data flow diagram)


==Proposed Agenda==
==Group Photo==
[[Image: GOC-Stanford-2012.jpg|800px]]


==='''''Sunday afternoon: 1pm until 4:30pm'''''===
==Remote Attendees==
====GOC Vision - From experimental data to structured knowledge for biologist ====
We will use the GO phone conference line and webex. An email will be sent to the GO consortium mailing list about how to join the Webex. <br>
* The hourglass model: gathering in of data, munging data, broad spectrum of output for consumption by biologists
Toll-free USA number 1-866-953-9688 (US Toll number 1-212-548-2460 in case of problems with 866 number)<br>
* Overview - Experimental Data In - Where does it come from? How can we as a community be more efficient?
Toll-free UK 0808 238 6001 (toll number: 646 834-9311)<br>
** Most experimental data currently comes from biomedical literature
Toll-free Switzerland 0800 562 830 (toll number: 646 834-9311)<br>
** Priorities can be either gene set or domain based
** Data could also come from data centers - pros and cons
** GO curators should be able to annotate for genes from all organisms (different than MOD curators)and need support to do this.
*PRIMARY MEETING ACTION ITEM: What can we collectively do to make annotation of experimental data more efficient?
** not expected to answer now, but at the end of the meeting....needs to be held in mind throughout this meeting.
** Tracking experimental annotations, QC. metrics (further discussions later)
* Building on Experimental Annotations
** Defining data flow after deposit of experimental annotations
** How often can/should we update phylogenetic analysis? 
** How can we stream PAINT annotations effectively to consumers
** How can we measure completeness of annotation stream both by gene and by domain??
* Focus of Meeting
** Finding efficiencies in generating experimental annotations
** Exploring GO SWAT option where GOC staff oversee domain effort with distributed curation supported
** how can curators focused on experimental literature contribute to PAINT-like annotation stream
*PRIMARY MEETING ACTION ITEM: What is the measure of completeness by gene or by domain that we want to employ?
** in contrast to others, vertebrates have tens of members of the thousands of small gene families.
** in contract to others, vertebrates have hundreds of publications for primarily-studied set of ~10,000 genes.
**
*PRMIARY MEETING ACTION ITEM: What do different sets of GO users want?  How do we provide this?
**


====General Discussion of Integrated Annotation Pipeline (Mike Cherry 20-23 minutes)====
Participant Pin: (801-561)<br>
* Can we define data flow from publication to PAINT annotation?
* Will, in general, each curator work from gene or from domain perspective?
* Will in general, each curator complete chain from experimental data through phlyo-inference; or how will these processes flow from one to the other.
* GO SWAT teams (PaulT and Judy)


====Current Status of Annotation Production (20-30 minutes) i.e. Where are we now with basic EXP annotation? ====
==Feb 26, 2012, Day 1 (half day) - Overview==
* What is our current rate of new annotation production
<font size = "+1">Arrive at: 11:00AM<br>
* What is our current rate of annotation loss (due to sunset clause, average % of annotations that can't be loaded, etc.)
Meeting: 12:00PM</font>
* Annotation Information Content assessment (how detailed are the existing annotations and what has been the trend over time)
===Current GO annotation status===
* Completeness and adherence to standards of "gp2protein" files
Minutes: Emily, Yasmin [[File:GOConsortiummeetingminutesFeb26_am.pdf‎]]
=====Goal for this Session=====


====Outline of the current EXP-based annotation process. (20-30 minutes)====
* Overview of current pipeline experimental information submitted by annotation groups (Paul T & Mike) [[File: GOC_SurveyQ2.pdf]], [[File:GOCquestionnaire3.pdf‎]], [[File:GOCquestionnaire4.pdf‎]]
# Knowledge extraction (both into the ontology and new annotations)(David, Val)
** Paul's summary slides [[File: survey_summary_3E_thru_4.pdf]]
#* Curators working directly from the literature
* Overview of rates of GO annotation production (break out metrics separately by group and by ontology aspect; for BP also report metrics separately for cellular process, multicellular organismal process; for CC also report metrics separately for macromolecular complex)
#* Curators working with experts in the field (who summarize and provide links to the primary literature)
* Current annotation status and the trend over time will be presented here along with the proposed report page. E.g. What is our current rate of new annotation production, annotation information content assessment, current rate of annotation loss (due to sunset clause, average % of annotations that can't be loaded, etc.), annotation “completeness” (how many genes with annotations in all three aspects considering: EXP only; EXP+ISS; EXP+ISS+IEA; ND only)  (Amelia, Chris and Suzi)
# Knowledge capture
* Completeness and adherence to standards of [http://wiki.geneontology.org/index.php/Gp2protein_file "gp2protein" files] (Paul T). <br>
#* Ontology requests for change
GPI format: (http://wiki.geneontology.org/index.php/Gene_Product_Association_Data_%28GPAD%29_Format#Proposed_Gene_Product_Information_.28GPI.29_file_format)
#* MODs
#* others
# Quality Assurance
# Data flow
#* Current
#* Straw-man proposal
=====Goal for this Session=====


====Lessons learned from recent EXP-based curation efforts ( >2 hours)====
===Vision for GO annotation process===
Focus is on how the processes might be generalized, with specific details only as supporting examples.
Minutes: Rama, Karen
* '''Domain-specific curation and ontology development (Knowledge extraction)'''
* Annotation submission (Suzi, Paul T., Chris and Emily) [[File:min_ideal_GO_annotation_requirements.pdf]]
** apoptosis annotation (Paola Roncaglia and Emily Dimmer)
** minimum annotation
** transcription overhaul (Karen Christie & Varsha Khodiyar)
** enhanced expressivity for GO annotations (Paul T.) [[File:enhanced_expressivity.pdf]]
* '''Approaches for recording annotations (Knowledge capture)'''
** Wiki-based annotation in CACAO: proposed improvements and potential generalizations (Jim Hu and Brenley)
** Integrating annotations coming from multiple sources for a single organism (Experiences at Swiss-Prot and GOA)
** CANTO experiences (Val Wood)
This is a PomBase tool that is being developed by Kim Rutherford to include GOC requirements to make it become available to community experts, who would like to submit small sets of GO annotations to the GO Consortium, which would then need to be reviewed by GOC groups. (Kim and PomBase will be keeping Kimberly and the CAF working group in the loop as to developments)
* '''Discussion of annotation strategy'''
** What are the bottlenecks
=====Goal for this Session=====


==='''''Monday: 9am to 5pm'''''===
Minutes: [[File:GOC2012MinutesSession2.pdf]]


====Towards a common annotation framework (Kimberly and Chris)====
==Feb 27, 2012, Day 2 (full day)==
* '''Kimberly to report on user requirements for CAF.'''
<font size = "+1">Breakfast: 8:00AM<br>
Kimberly is currently talking to all curation groups about individual GO annotation tools, what features they have and what features curators would like. Therefore, by the GO Consortium meeting, Kimberly will be able to present the features that GOC curators feel are most important.
Meeting: 9:00AM</font>
* '''Discussion'''
===Case studies of state-of-the-art annotation approaches===
** any other aspects curators would require in an annotation tool.
[[minutes_annotation_approaches_stanford_2012 | Minutes]]: Jane, Paola<br>
** What additional data should be supplied by annotation groups
** How best to use text-mining in the CAF for prioritizing curation work (e.g. Textpresso)
* '''Project plan, development goals for next 3-6 months (Chris Mungall)'''


====Phylogenetic inference process (Paul Thomas and Pascale/Suzi)====
Each of these presentations will consider the experiences they have had and what the bottlenecks and issues that have been encountered. We will use these lessons to determine the best path forward to streamline and enrich the process.
* '''PAINT as used for Quality Assurance'''
**Dual perspectives (biological topic focus)
**cross-checking annotations
**Phylogenetic inference: Synthesis, QA and inference across organisms using PAINT
* '''PAINT: How MODs can achieve full breadth of genome coverage'''
** Focused annotation session for ~10 GO annotators per group
** Led by Pascale and/or PaulT with Mike L., Rama, Li Ni, Donghui, Huaiyu handling groups individually
** small groups to make each session manageable and productive
** Mixed groups
*** those with previous training in PAINT annotation
*** no training, however strong possibility in using PAINT later on to create GO annotations (e.g. GO NIH funded curators)
** Annotations to transfer would be selected on the basis of recent annotation work by GO Consortium groups that are now in the GO database, to terms from the ontology which have been reviewed and likely to remain stable (e.g. from the recent transcription annotation effort)
** Time required: minimum: 5 hours.
=====Goal for this Session=====


==='''''Tuesday: 8:30am to 4pm'''''===
* Community approaches for recording annotations
** [[Media:GO_201202_CACAO.pdf|Wiki-based annotation in CACAO: proposed improvements and potential generalizations]] (Jim Hu and Brenley McIntosh)
** CANTO experiences (Val Wood). CANTO is a PomBase tool that is being developed by Kim Rutherford to include GOC requirements to make it become available to community experts, who would like to submit small sets of GO annotations to the GO Consortium, which would then need to be reviewed by GOC groups. (Kim and PomBase will be keeping Kimberly and the CAF working group in the loop as to developments)
* What additional gene function information is used to supplement GO annotation?
** at UniProt (Claire)
** at MGI, e.g. cell types; temporal -spatial (David & Harold)[[File:MGI_GO_EI_2.pdf‎]]
* GOC Domain-specific curation and ontology development
** apoptosis annotation (Paola and Emily )
** transcription overhaul (Rama & Karen) [[Media:TxnOH-OntDev-Report.pdf]], [[Media:TxnOH-AnnotReport.pdf]]
** summary of recommendations (Mike)


====Minimal requirement for GO annotations (Emily Dimmer and Harold Drabkin) i.e. What does an annotation consist of, both minimally and ideally ====
===Proposal for GOC use of common annotation framework to support literature annotation and subsequent phylogenetic annotation process===
* Minimal requirements for submitting GO annotations (for projects and MODs *not* funded via the GOC)
Minutes: Chris, Seth
* What would an ideal annotation consist of and what are the responsibilities for GO curators (for projects and MODs *funded* via the GOC)
* Overview of the common annotation framework (Chris and <b>Paul T.</b>)
* LEGO annotation framework
** Data flow proposal. [[File: current_and_proposed_annotation_flow.pdf]]
* Details of the common annotation framework  (<b>Paul S</b>, Paul T, Judy, Mike, Suzi)
* Common annotation Software prototype demos (Kimberly et al.).
** Kimberly is currently talking to all curation groups about individual GO annotation tools, what features they have and what features curators would like. By the GO Consortium meeting, Kimberly will present the features that GOC curators feel are most important.
*** Any other aspects curators would require in an annotation tool.
*** What additional data should be supplied by annotation groups.
*** How best to use text-mining in the CAF for prioritizing curation work (e.g. Textpresso).
*** CAT Project development goals for next 3-6 months. (Kimberly & Chris Mungall)
*** PAINT as used for Quality Assurance: Dual perspectives (biological topic focus); cross-checking annotations; Phylogenetic inference: Synthesis, QA and inference across organisms using PAINT.
*** Integration and prioritization of phylogenetic annotations within the framework of experimental annotations.


====Towards a biological topic-focused approach====
==Feb 28, 2012, Day 3 (full day)==
* '''How and who should select targeted gene sets'''
<font size = "+1">Breakfast: 8:00AM<br>
** Is 9 genes a reasonable # to tackle per annotation milestone
Meeting: 9:00AM</font>
** What criteria should be used to declare a milestone has been reached. (comprehensively annotated gene products, final paint approval, other QC checks)
* '''What skills are needed among the members of the annotation focus group and what tools do they need'''
** Ontology expert, biological expertise, GO curator
** Efficient ways of leveraging the community
** What tools and other infrastructure would assist.
* '''Next steps towards integral quality control'''
** Define our specific tactical approach to new annotation strategy


====Responsibilities and review of milestones for next meeting====
===Concurrent sessions (4 hr)===
* Software group will go off for a concurrent meeting (Chris, Seth, Ben, Mary, Heiko, Hans-Michael)
* '''Instructions to download and launch PAINT, and general user guide:''' http://wiki.geneontology.org/index.php/PAINT_User_Guide
* PAINT training (Suzi and/or Huaiyu)
** PAINT background and intro to function evolution in gene families (Paul T.) [[File:basic_PAINT_annotation_background.pdf]]
How MODs can achieve full breadth of genome coverage: Focused annotation session for ~5-7 GO annotators per group: Led by Pascale, Paul, & Huaiyu handling groups individually: small groups to make each session manageable and productive. Annotations to transfer would be selected on the basis of recent annotation work by GO Consortium groups that are now in the GO database, to terms from the ontology which have been reviewed and likely to remain stable (e.g. from the recent transcription annotation effort)


==Preparation needed in advance of GO Consortium meeting (incomplete, see agenda)==
 
#Develop proposal for annotation process (Harold, Rama, Emily, Kimberly)
:* Mixed groups
#*using examples from transcription overhaul (Karen & Varsha)
:** those with previous training in PAINT annotation
#*apoptosis (Paola & Emily)
:** no training, however strong possibility in using PAINT later on to create GO annotations (e.g. GO NIH funded curators)
#*CACAO (Jim Hu)
:** Group 1: Pascale, Rama, Kimberly, - Prudence, Petra, Stacia, Dianna, Doug, Susan, Varsha, Aurore, Steven, Martha,
#*Integrating multiple sources for annotations on a single species (Rolf or Claire)
:** Group 2: Paul, Li, David, Tanya, - Julie, Karen, Cindy, Peter, Brenley, Paola, Ruth, Rex N, Lucas, Rajni
#*Phylogenetic annotation (Pascale and/or PaulT)
:** Group 3: Huaiyu, Donghui, Harold, Emily - Yasmin, Rob, Selina, Kalpana, Jim, Val, Jane, Carson, Diane
#Preparation for each GO annotation group
 
#*How does GO annotation fit into your overall curation process? Ideally as a high-level flowchart
===Decisions made, reorganization of manager groups and their coordinators.===
#*What is your process for GO annotation?  Ideally as a detailed flowchart
 
#**What software tools do you use for GO annotation?
Minutes: David, Kimberly, Harold
#**Do you regularly make both literature and inferred (e.g. ISS) annotations?
 
#**How do you prioritize which papers, genes, etc. are targeted for GO annotation?
'''Minutes:'''[[File:Tuesday_02_28_Minutes.pdf]]
#**How do you create a GAF file for submission to the GOC?
 
#*What information do you want to capture in a controlled vocabulary that you currently CANNOT capture with GO terms?
* Defined tasks that will occur over the next six months.
 
* The PIs will affirm that the Managers are responsible for communicating the tasks required to reach the projects agreed to goals.
** The Directors empower the Managers to activity monitor the working groups progress and report any problems that inhibit reaching our goals.
** There are commitments that need to be met by all members for the GOC to be a success.
 
* To conclude the meeting we will finalize goals and what we’ve agreed to do going forward. (GO Directors)
** Annotation and Ontology productivity working group
*** Pick a realistic goal for increasing the # of annotations/quarter over the next 5 years
*** Pick a realistic goal for increasing the information content (specificity) of the annotations over the next 5 years
*** Define and publish what is minimally required for community contributions and mechanisms to ensure quality standards are met. That is, minimal requirements for submitting GO annotations (for projects and MODs *not* funded via the GOC)
*** Efficient ways of leveraging the community
*** What tools and other infrastructure would assist.
*** Respond in a timely manner to community & sourceforge term requests
** Annotation Integration & ontology review working group
*** Quality Control: Independent secondary checks of annotations
**** Automated checks
**** Semi-manual checks
**** Manual checking through random sampling
**** What criteria should be used: comprehensively annotated gene products via final paint approval, other QC checks
*** How to select targeted gene sets
*** Define what additional information we ideally would aim to collect to enrich the annotations coming from GO funded efforts. That is, What would an ideal annotation consist of and what are the responsibilities for GO curators (for projects and MODs *funded* via the GOC)
*** Ontology modeling, consistency and review
** Framework working groups
*** Database infrastructure:
**** Define concrete steps for implementation of required infrastructure for meeting these annotation goals.
**** LEGO annotation framework
**** Sign off on the new annotation flow proposal.
**** Mechanism for sending GO annotations to the MODs. GO annotations will be generated by dedicated GO curators using the central CAT tool, and resultant
*** GO annotation tools working group
*** User and community interactions
** Ad hoc groups
*** Fixed timeframe
*** Fixed deliverable(s)  
** GO Directors (Paul T, Paul S, Suzi, Mike, & Judy
*** Decision making
*** Set priorities for each working groups
*** Attend working group calls
[[Category:Workshops]]

Latest revision as of 10:08, 15 April 2019

Agenda

Preparation/Goals for the meeting

Over all goals for the meeting are available here

Group Photo

Remote Attendees

We will use the GO phone conference line and webex. An email will be sent to the GO consortium mailing list about how to join the Webex.
Toll-free USA number 1-866-953-9688 (US Toll number 1-212-548-2460 in case of problems with 866 number)
Toll-free UK 0808 238 6001 (toll number: 646 834-9311)
Toll-free Switzerland 0800 562 830 (toll number: 646 834-9311)

Participant Pin: (801-561)

Feb 26, 2012, Day 1 (half day) - Overview

Arrive at: 11:00AM
Meeting: 12:00PM

Current GO annotation status

Minutes: Emily, Yasmin File:GOConsortiummeetingminutesFeb26 am.pdf

  • Overview of current pipeline experimental information submitted by annotation groups (Paul T & Mike) File:GOC SurveyQ2.pdf, File:GOCquestionnaire3.pdf, File:GOCquestionnaire4.pdf
  • Overview of rates of GO annotation production (break out metrics separately by group and by ontology aspect; for BP also report metrics separately for cellular process, multicellular organismal process; for CC also report metrics separately for macromolecular complex)
  • Current annotation status and the trend over time will be presented here along with the proposed report page. E.g. What is our current rate of new annotation production, annotation information content assessment, current rate of annotation loss (due to sunset clause, average % of annotations that can't be loaded, etc.), annotation “completeness” (how many genes with annotations in all three aspects considering: EXP only; EXP+ISS; EXP+ISS+IEA; ND only) (Amelia, Chris and Suzi)
  • Completeness and adherence to standards of "gp2protein" files (Paul T).

GPI format: (http://wiki.geneontology.org/index.php/Gene_Product_Association_Data_%28GPAD%29_Format#Proposed_Gene_Product_Information_.28GPI.29_file_format)

Vision for GO annotation process

Minutes: Rama, Karen

Minutes: File:GOC2012MinutesSession2.pdf

Feb 27, 2012, Day 2 (full day)

Breakfast: 8:00AM
Meeting: 9:00AM

Case studies of state-of-the-art annotation approaches

Minutes: Jane, Paola

Each of these presentations will consider the experiences they have had and what the bottlenecks and issues that have been encountered. We will use these lessons to determine the best path forward to streamline and enrich the process.

  • Community approaches for recording annotations
    • Wiki-based annotation in CACAO: proposed improvements and potential generalizations (Jim Hu and Brenley McIntosh)
    • CANTO experiences (Val Wood). CANTO is a PomBase tool that is being developed by Kim Rutherford to include GOC requirements to make it become available to community experts, who would like to submit small sets of GO annotations to the GO Consortium, which would then need to be reviewed by GOC groups. (Kim and PomBase will be keeping Kimberly and the CAF working group in the loop as to developments)
  • What additional gene function information is used to supplement GO annotation?
  • GOC Domain-specific curation and ontology development

Proposal for GOC use of common annotation framework to support literature annotation and subsequent phylogenetic annotation process

Minutes: Chris, Seth

  • Overview of the common annotation framework (Chris and Paul T.)
  • Details of the common annotation framework (Paul S, Paul T, Judy, Mike, Suzi)
  • Common annotation Software prototype demos (Kimberly et al.).
    • Kimberly is currently talking to all curation groups about individual GO annotation tools, what features they have and what features curators would like. By the GO Consortium meeting, Kimberly will present the features that GOC curators feel are most important.
      • Any other aspects curators would require in an annotation tool.
      • What additional data should be supplied by annotation groups.
      • How best to use text-mining in the CAF for prioritizing curation work (e.g. Textpresso).
      • CAT Project development goals for next 3-6 months. (Kimberly & Chris Mungall)
      • PAINT as used for Quality Assurance: Dual perspectives (biological topic focus); cross-checking annotations; Phylogenetic inference: Synthesis, QA and inference across organisms using PAINT.
      • Integration and prioritization of phylogenetic annotations within the framework of experimental annotations.

Feb 28, 2012, Day 3 (full day)

Breakfast: 8:00AM
Meeting: 9:00AM

Concurrent sessions (4 hr)

How MODs can achieve full breadth of genome coverage: Focused annotation session for ~5-7 GO annotators per group: Led by Pascale, Paul, & Huaiyu handling groups individually: small groups to make each session manageable and productive. Annotations to transfer would be selected on the basis of recent annotation work by GO Consortium groups that are now in the GO database, to terms from the ontology which have been reviewed and likely to remain stable (e.g. from the recent transcription annotation effort)


  • Mixed groups
    • those with previous training in PAINT annotation
    • no training, however strong possibility in using PAINT later on to create GO annotations (e.g. GO NIH funded curators)
    • Group 1: Pascale, Rama, Kimberly, - Prudence, Petra, Stacia, Dianna, Doug, Susan, Varsha, Aurore, Steven, Martha,
    • Group 2: Paul, Li, David, Tanya, - Julie, Karen, Cindy, Peter, Brenley, Paola, Ruth, Rex N, Lucas, Rajni
    • Group 3: Huaiyu, Donghui, Harold, Emily - Yasmin, Rob, Selina, Kalpana, Jim, Val, Jane, Carson, Diane

Decisions made, reorganization of manager groups and their coordinators.

Minutes: David, Kimberly, Harold

Minutes:File:Tuesday 02 28 Minutes.pdf

  • Defined tasks that will occur over the next six months.
  • The PIs will affirm that the Managers are responsible for communicating the tasks required to reach the projects agreed to goals.
    • The Directors empower the Managers to activity monitor the working groups progress and report any problems that inhibit reaching our goals.
    • There are commitments that need to be met by all members for the GOC to be a success.
  • To conclude the meeting we will finalize goals and what we’ve agreed to do going forward. (GO Directors)
    • Annotation and Ontology productivity working group
      • Pick a realistic goal for increasing the # of annotations/quarter over the next 5 years
      • Pick a realistic goal for increasing the information content (specificity) of the annotations over the next 5 years
      • Define and publish what is minimally required for community contributions and mechanisms to ensure quality standards are met. That is, minimal requirements for submitting GO annotations (for projects and MODs *not* funded via the GOC)
      • Efficient ways of leveraging the community
      • What tools and other infrastructure would assist.
      • Respond in a timely manner to community & sourceforge term requests
    • Annotation Integration & ontology review working group
      • Quality Control: Independent secondary checks of annotations
        • Automated checks
        • Semi-manual checks
        • Manual checking through random sampling
        • What criteria should be used: comprehensively annotated gene products via final paint approval, other QC checks
      • How to select targeted gene sets
      • Define what additional information we ideally would aim to collect to enrich the annotations coming from GO funded efforts. That is, What would an ideal annotation consist of and what are the responsibilities for GO curators (for projects and MODs *funded* via the GOC)
      • Ontology modeling, consistency and review
    • Framework working groups
      • Database infrastructure:
        • Define concrete steps for implementation of required infrastructure for meeting these annotation goals.
        • LEGO annotation framework
        • Sign off on the new annotation flow proposal.
        • Mechanism for sending GO annotations to the MODs. GO annotations will be generated by dedicated GO curators using the central CAT tool, and resultant
      • GO annotation tools working group
      • User and community interactions
    • Ad hoc groups
      • Fixed timeframe
      • Fixed deliverable(s)
    • GO Directors (Paul T, Paul S, Suzi, Mike, & Judy
      • Decision making
      • Set priorities for each working groups
      • Attend working group calls