RefG Princeton April 12-13 2010

From GO Wiki
Revision as of 13:14, 12 April 2010 by Karadolinski (talk | contribs)

Jump to: navigation, search

Propagation Rules/SOP

  • Very useful to spend a few minutes looking at a review, geneWiki, etc for an overview of the family when PAINT curators are not familiar.
  • Use ortholog mapping to do a reality check on the tree: overall look, see if OrthoMCL makes sense. If it does not, contact Paul and the tree will be edited as appropriate.
  • Generally easiest to start with Mol. Function, then Cell. Component, then Biol. Process
  • Can be useful (leads to improvements to GO structure) downloads terms and views the DAG for all terms (possible future feature request)
  • Every NOT must have an Evidence entry. Add notes below the generic paragraph that pops up.
  • When PAINT curator finds an experimental annotation, the SOP is to contact the MOD curator, but they do not need to wait. They can just add the note to the Evidence entry that the annotation exists and the tree will be revisited.
  • NOT + rapid divergence = the line will not be in the GAF but will be retained in PAINT. This will enable the ability to say "do not propagate" to a particular clade, distinguished from adding an explicit NOT. For a "real" NOT, we will use a different qualifier; these will be exported in the GAF. This SOP was discussed for quite some time--alternative solutions that we did not like as well: 1) "Do Not Propagate" pruning automatically based on branch length. 2) manually examine the Ref Genome proteins, but do not look at every single other proteins for other species.
  • Use common sense and keep the big picture of the tree and knowledge about the family in mind (eg. LON family: propagation of mito., light strand promoter anti-sense binding annotation to base of euks) ie. we should not always limit ourselves to the bare minimal triangulation. Always include an evidence note when doing so.
  • Treat closely related genes with opposite annotations: look at PMIDs and see if they are really contradictory, if so, don't propagate. If not, contact the MODs to correct the annotation.
  • Still do the multiple annotations in cases where we make sourceforge requests for new links in the ontology.
  • Do not propagate GO:0005515 protein binding (will be suppressed from PAINT), GO:0005488 binding, and enzyme binding.
  • We will only propagate children of protein binding when the terms are specific enough to indicate a specific protein family and/or it provides useful biological information to the biologist wanting to learn more about this term ie. that molecular function is related to the biological process(es) that are annotated in this family.
  • We will propagate small molecule binding terms.

Misc Notes/Action items/Still pending questions

  • Missing MOD annotation to 'sequence-specific DNA binding', will request this: LON family
  • ser-dependent (parent) -> atp-dependent peptidase (child), need this link, check up to endopeptidase-> sourceforge item: LON family.
  • Read document of proposal about binding terms
  • write to Emily, remove ADP binding from human annotation in LON family
  • DNA polymerase binding: ask for new term: DNA polymerase gamma binding. And, human changes annotation to new term. LON family

PAINT feature requests/bugs

  • Down the road feature: be able to launch a DAG viewer to see all annotations in context of GO structure
  • Add domain information
  • Radio buttons color coded based on GO aspect
  • Scrolling in MSA view alters the residue number (bug), enable search to go to specific residues
  • Remove GO:0005515 (protein binding) from the list of terms we see in PAINT

Quick tour for new PAINT users (Li and Mary)

Ed gave a quick tour of the latest version of PAINT.

Review protein families, see: While reviewing protein families, we can generate a list of propagation rules. We can pick up lunch in our cafe, and work through lunch.


  • Annotate root to 'ATP-dependent peptidase activity' based on experimental annotation span across species
  • NOT to radA clade, we know that they do not have this activity, use the missing_residues qualifier
  • Scrolled through rest of alignment to identify others that do not have the active site
  • Missing MOD annotation to 'sequence-specific DNA binding', will request this of MOD, and annotate to root
  • Annotate mito., light strand promoter anti-sense binding annotation to base of eukaryotes. Based simply on data, would go to human-mouse base, but when given some thought about where this happened, should go to the base of eukaryotes.
  • see notes in the abstract generated by this family for more details



GO annotation camp discussion

misc. discussion items

  • (Mike): Is the PANTHER to P-POD OrthMCL mapping currently working?
  • (Mike): Should we fix the dates in the new GAF files to reflect when the annotations were actually made?
  • (Mike): Could we re-generate the statistics from the GAF files using a script (rather than manually)?
    • Probably easy enough, once we discuss what stats we're interested in capturing (Ed)
  • (Mike): Pascale noticed a problem with the literature linkouts to Wormbase, and I just had some trouble with ZFIN
    • Fixed (Ed)

Annotation tracker

Sven, CJM, Seth

  • Current issues/roadblocks
  • Subfamily issue: can we deal?
  • Feedback
  • Can we leverage the annotation reporter to generate the monthly lists in an easier way?


  • Title: ???
  • Authors: as on this mailing list, and possibly adding CJM, Seth, and Sven if we add a section on the DB and the other GO-top PIs
  • Affiliations: obviously
  • Abstract: Paul?
  • Author Summary: Suzi will take a crack at this
  • Introduction: Pascale&Paul
  • Results: as below, with possible addition of DB section and web interface, although this could be a different paper. Ed and Suzi can write #1, Paul&Mike for #2?
  • Discussion: #3 (Mike & Kara)
  • Materials and Methods: cut and dry, write at the end
  • Acknowledgments: all the curators at the MODs, the grant...
  • References, Figure Legends, Tables: as they fall out from the above.