Manager 9March11

From GO Wiki
Jump to: navigation, search

Canceled - not enough attendees


Agenda

Minutes: R

Attending:


  • Can everyone check if there are items from the last meeting we need to carry over? Manager_23Feb11

Old Business

  • MGI Curator's report on changes made to term definitions for annotators to refine their annotations if they think it is warranted. Amelia has written the report; http://www.geneontology.org/scratch/def_diffs.html. his data could be updated once a week.

ACTION: format check, then send out to the GO list. This data could be updated once a week. Location in the scratch directory correct, or should be in a directory for reports?Need to talk with Chris.

New Discussion Topics

Items from the Annotation and Reference genome Groups:

* Encouraging correct GO annotation display by external websites


  • Could Mike C's script be used to remove annotations that apply obsolete GO Database Abbreviations? e.g. It appears that NCBI_NM:123456 should be displayed as RefSeq:NM_123456
  • GOA is looking at MOD identifiers in column 8 (with) of GAFs - Tony would be happy to regularly email groups to identify those ids that fall outside of the accepted id RegExps. However would this QC be best done by Mike's script?
  • How to encourage all GO Consortium providers of GAFs to supply a gp2protein (PAMGO, GeneDB, aspgd, jcvi, peseudocap, sgn)


  • Would it be desirable to generate a reference page for prioritizing non-curation work that we require of annotation groups (e.g. development of annotation file formats, incorporating PAINT and m2p inferences, adding column 16 data etc.)that often involves software engineer time. At GOC meetings many ideas are presented, some are actioned but are not followed up by MODs. Its understandable that some groups are reluctant to use valuable programmer time until they have been convinced that the GOC is determined to go in a certain direction. The page could summarize the top jobs, with links to final specifications of any file formats.


Reminder: this was an item brought up at the GO Consortium meeting in Stanford March 2010. Here are the minutes from the discussion - One of the action items was:

  • Action item: We will roll out new split GAF for all groups


  • Proposal for definition of Comprehensively annotated:(Emily)

- this tag is attached at the level of the gene product and must be accompanied by a timestamp. Definition:

Indicates that a gene product has been the focus of a manual annotation effort whereby a curator has reviewed the current literature and has annotated to the principal functions, process and component GO terms. It is not required for a curator should have annotated every single paper published on a gene product if additional annotations would only duplicate information currently provided.

The timestamp is an essential component of this label, as it indicates the date at which the curator last reviewed the gene product's annotation set and literature available.

It is possible that a gene product may have papers that were published after the 'comprehensively annotated' timestamp that would be suitable for GO annotation but that have not yet been added added.

Similarly, GO annotations to a comprehensively annotated gene product with a later timestamp may exist which have been created during routine annotation update procedures, or as a by-product from a annotation efforts focusing on a different gene product.

Each time a curator re-reviews the entire annotation set for a previously 'comprehensively annotated'-tagged gene product, the associated timestamp should be updated.