9 FEB 2010 RefGen Phone Conference (Archived)

From GO Wiki
Jump to navigation Jump to search

Present

  • GOA:
  • BHF-UCL:
  • MGI:
  • RGD:
  • Flybase:
  • dictyBase:
  • TAIR:
  • AgBase:
  • SGD:
  • pombe
  • Ecoli:
  • Wormbase:
  • ZFIN:
  • PPOD:
  • Berkeley:

Lung curation targets

  1. Discuss the priorities (Dec, Jan, and fgf10 from November) and goal (March 1st)
  2. Please answer prior to the callCan everyone have the curation targets annotated by then?
  • GOA:
  • BHF-UCL:
  • MGI:
  • RGD:
  • Flybase:
  • dictyBase:
  • TAIR:
  • AgBase:
  • SGD:
  • pombe
  • Ecoli:
  • Wormbase:
  • ZFIN:

PAINT demo

Ed Lee, Berkeley

Plan for annotation status reporting tool

Kara and her group have started to work on a tool that would display the annotation status of the Panther families. There will be a regularly updated web page that will show the following information:

  1. Panther family ID
  2. Date selected for concurrent annotation
  3. Date Panther family last annotated
  4. Number of members
  5. Number of RefG members
  6. Number of members with EXP
  7. Date more recent member last annotated

We could add 'date comprehensively annotated' for groups that can provide this information:

Please answer prior to the call: who currently captures that and could generate a file with such information:

  • GOA: Yes
  • BHF-UCL:
  • MGI:
  • RGD:
  • Flybase:
  • dictyBase: Yes (we capture curation status for the entire 'gene' curation, but could use that for now)
  • TAIR:
  • AgBase:
  • SGD:
  • pombe
  • Ecoli:
  • Wormbase:
  • ZFIN:


  • Alerts:
    • Tree curators should be alerted when the Date in Column 6 is more recent than the date in Column 2.
    • When the Panther families are modified (once-twice per year), there should be a check to verify that the members are still the same. If there are additions or deletions: there should be an alert for curators annotations. We may be able to automate part of the required modifications to annotations.
  • Annotations to nodes: All the previous part of the script is just a report based on the trees and the GAF files. However in some cases we annotate to nodes rather to entire trees. There needs to be a way to request a report for a specific tree node. This will be done as a second step.


Branding Ref.genome annotation data in GOC and within each group

Rama started a wiki page to collect ideas. http://gocwiki.geneontology.org/index.php/Ideas_for_publicizing_Ref.Genome_Annotation_Data Use this page to provide suggestions


GO annotation camp

  1. Overview: The annotation camp will take place over 3 days, from June 16-18 (Wednesday-Friday).
  2. Goals and deliverables:
    1. This annotation camp will be focused on updating and refining skills of existing GO biocurators including new GO biocurators in existing annotation groups and including the Swiss-Prot curation team.
    2. There will be three ‘focused annotation sessions’ where specific annotation issues will be discussed. Deliverable: final annotation documentation for each of the three topics.

Suggestion for discussion topics should be added to the GO camp agenda: 2010_GO_camp_Meeting_Logistics#Suggestions_for_annotation_issues_to_be_discussed

    1. There will be a special emphasis on the reference genome project. Deliverable: annotation propagation rules for the reference genome project.
  1. Registration: If you already know whether you'll be able to attend or not, please fill the wiki meeting logistics page: 2010_GO_camp_Meeting_Logistics

Back to Reference Genome Conference_Calls Page