9 FEB 2010 RefGen Phone Conference (Archived): Difference between revisions
Jump to navigation
Jump to search
Line 79: | Line 79: | ||
# Overview: The annotation camp will take place over 3 days, from June 16-18 (Wednesday-Friday). | # Overview: The annotation camp will take place over 3 days, from June 16-18 (Wednesday-Friday). | ||
# Goals: 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. We hope members of each MOD will be represented. | # Goals: 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. We hope members of each MOD will be represented. | ||
# Structure: 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]] | # Structure: There will be '''three (3) ‘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]] | ||
##There will be a special emphasis on the reference genome project. Deliverable: annotation propagation rules for the reference genome project. | ##There will be a special emphasis on the reference genome project. Deliverable: annotation propagation rules for the reference genome project. | ||
#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]] | #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]] |
Revision as of 12:29, 4 February 2010
Present
- GOA:
- BHF-UCL:
- MGI:
- RGD:
- Flybase:
- dictyBase:
- TAIR:
- AgBase:
- SGD:
- pombe
- Ecoli:
- Wormbase:
- ZFIN:
- PPOD:
- Berkeley:
Lung curation targets
- Discuss the priorities (Dec, Jan, and fgf10 from November) and goal (March 1st)
- Please answer prior to the call: Can everyone have the curation targets annotated by then? If not, can you write down which families are problematic?
- 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:
- Panther family ID
- Date selected for concurrent annotation
- Date Panther family last annotated (tree annotations)
- Number of members
- Number of RefG members
- Number of members with EXP
- 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 the 'date comprehensively annotated' 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 7 (protein annotations by MODs) is more recent than the date in Column 3 (tree annotation).
- 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
- Overview: The annotation camp will take place over 3 days, from June 16-18 (Wednesday-Friday).
- Goals: 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. We hope members of each MOD will be represented.
- Structure: There will be three (3) ‘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
- There will be a special emphasis on the reference genome project. Deliverable: annotation propagation rules for the reference genome project.
- 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