2011 USC Meeting Action Items

From GO Wiki
Jump to navigation Jump to search

Action items from the 2011 USC meeting


  • Annotation: Report on taxon constraints needs to be implemented ASAP!
  • Annotation: Contact Rama and Emily if you can help organizing and editing the annotation pages on the GO website
  • Annotation: Continue to work on the guidelines. Ask the go-discuss email list for suggestions; ideas: (i) improve IMP/downstream events; (ii) cellular versus multicellular level annotation


  • GO Help: create an aggregator for GO-related stuff on other sites - BioStar, Twitter, Facebook, Myspace, Boing Boing, etc.
  • GO Help: designate a point person for software group queries (Seth seems to have volunteered)
  • GO Help: if you're interested in joining GO help--and it's very rewarding, great fun, and a superb way to enhance your day--please contact Rama and Emily.


  • Evidence Codes: convene a working group to discuss ECO in more depth and propose a plan for implementation in the GOC.


  • Annotation deliverables: What are the annotation items that we are going to present to the world? Formulate guidelines and deliverables.


  • Ontology development: comments on annotation should go into GONUTS (e.g. how to annotate transcription factors), not the GO wiki.
  • Ontology development: notification of GO changes to GO friends
  • Ontology development: weekly emails to GO list containing new terms
  • Ontology development: daily email to GO list containing def differences
  • Ontology development: make available differences in some kind of parseable format
  • Ontology development: get GOing on the integral to qualifier now that everyone is crystal clear on how has part works.
  • Ontology development: to request from everyone to provide a short description of their expertise, so that they can ask appropriate curators when needing input for SF requests


  • PRO: feel free to use PRO IDs in col 17 and ask the PRO team for new IDs. No formal shift to PRO for the time being.


  • Col 16: work out what relations are needed and document them fully. David has volunteered to (and is in the process of) looking through all MGI structured notes since 2002 to work out which relations are required.


  • Software: discuss modularization strategy in OBO-Edit--e.g. having taxon constraints in the OBO file--as well as other information requested by specific groups


  • Ref Genome: devise a method for handling the individual references for families; they have to be loaded into every member DB, which causes all manner of problems


  • Website: write some top notch documentation on the integral to qualifier


  • Common Annotation Tool: get a requirements working group to work everything out
  • Common Annotation Tool: consider using Val's "Tool With No Name" for the community annotation tool NOW (instead of waiting until the next grant period)


  • GPI and GPAD: work out specs, scripts, advantages, disadvantages and a time scale. Another working group to the rescue!




Back to the 2011 USC Meeting Agenda