2011 USC Meeting Action Items: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:


* '''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.
* '''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.


* '''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
* '''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

Revision as of 16:39, 20 May 2011

  • 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


  • 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.


  • 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: def diffs to the list
  • 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.


  • 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.


  • 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