Over all goals for the meeting are available here

From GO Wiki
Jump to: navigation, search

Preparation needed in advance of GO Consortium meeting

  1. Preparation for each GO annotation group
    • How does GO annotation fit into your overall curation process? Ideally as a high-level flowchart
    • What is your process for GO annotation? Ideally as a detailed flowchart
      • What software tools do you use for GO annotation?
      • 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?
      • 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?
  2. Develop proposal for annotation process (Suzi, Harold, Rama, Emily, Kimberly, Paul)
    • Literature-based annotation process using examples from transcription overhaul (Karen & Varsha) and apoptosis (Paola & Emily)
      • Ontology development support of annotation (David, Chris, Paola)
      • Prioritization, e.g. biological domain focus (Suzi, Emily, Rama)
      • Measure of success of these overhauls and how can the process and result be improved (Rama & Mike)
    • Phylogenetic annotation (Pascale and/or PaulT)

Overview of goals of meeting

At this meeting we will be discussing specific proposals with the prime objective being to reach agreement on an implementation path going forward to efficiently and accurately create functional annotations capturing molecular information about gene products that are of high quality. Ideally we will achieve the following:

  1. We will agree on specific annotation goals relative to the experimental literature. These #s will be reassessed at subsequent GOC meetings and used as a means of tracking progress.
    1. Each annotation group will track completeness
      1. Globally: Out of the potential GO annotations that could be made, what fraction are completed? What fraction of all relevant papers (or genes, or however the group prioritizes GO annotation) have been curated?
      2. By gene: Which genes are currently “comprehensive” wrt the available experimental literature?
    2. The dedicated annotation staff will track adherence to annotation guidelines
    3. The dedicated annotation staff will track the number of non-redundant, accepted annotations each period
    4. The dedicated annotation staff will track the information content (specificity) of the accepted annotations
  2. We will extend our quality control methods and strategies by creating a working group dedicated to this role.
    1. Agreement that all contributed annotations will undergo secondary QA steps before being accepted
    2. Agreement that dedicated QA curators have the authority to reject contributed annotations
    3. Contributing curators agree to follow annotation guidelines and remove or revise annotations that do not meet these guidelines
    4. The dedicated QA curators will agree to use and maintain the documented methodologies for inferred annotation
    5. The dedicated QA curators will agree to use the prioritization scheme that is available on GO site.
  3. We will define concrete steps for implementation of required infrastructure for meeting these annotation goals.
    1. Contributing groups will sign off on the new annotation flow proposal and their ability and plans for implementation.
    2. Sign off on the initial proposed requirements for the common annotation tool.