GO 18th Consortium Meeting Action Items

From GO Wiki
Revision as of 09:10, 25 September 2007 by Maria (talk | contribs)
Jump to navigation Jump to search

Summary of action Items from Day 1

  1. Tutorial on wiki discipline (assigned to Jim Hu).
  2. (ALL) Look at and comment on outstanding items Outstanding Action Items from 17th GOC Meeting, Cambridge UK
  3. (David Hill) Check whether there should be a relationship between pigment metabolic process and pigmentation
  4. Jen: A reference to these pages should go in next newsletter.
  5. Jen Add a link from outreach to something (SOP?)
  6. investigate why terms requests aren’t coming in, do we need things we need to do to make it easier, SF tracker list/annotation list/ who are on these lists/ do other people need to be on those lists?
  7. NML Michael sent ISSN URL to Eurie – Action Eurie!
  8. (Newsletter group) RSS feed for Newsletter
  9. (Esther, Jen and Ruth) Reactome annotations should be available from GO by the next GO Consortium meeting. Add new evidence code EXP for 1:1 Reactome to literature, add all other Reactome with TAS to Reactome source.
  10. Convert Reactome complex terms to GO terms
  11. (Jen) Carry out pilot project with a minimal set of terms, as an experiment and bring back results for next GO meeting
  12. (David Hill) Make difficult sensu terms organism specific (biologist intuitive) (i.e plant vacuole, fungal vacuole). However GO definitions will still be designed to be formal, not depending on species to define the term.

Summary of Action points from Day 2

  1. (David Midori Seth) Deploy the part that created SF items based on a friendly webform, and would like to see an OBO format in the SF item.
  2. Seth, ORB: Make link to how to make a perfect GO term from the term request tool (this information should be available from both the SourceForge page and the wrapper)
  3. Amelia link GOOSE from front page
  4. (Chris Mungall) Cross products: need to have Webex meeting for GO editors so all understand what to do.
  5. DONE: OBO file renaming. JB: add a link to Wiki: http://gocwiki.geneontology.org/index.php/Versionning_Proposal On the best practises page: http://gocwiki.geneontology.org/index.php/Best_Practises
  6. (Midori Harrid) to work on the specification for OBO stanza for term requests (this is already documented).
  7. Gene Association files: to work on a more advanced interface to download custom files (Chris)
  8. Gene Association files: to filter files as they come in. (Chris)
  9. Judy: Predictive Activities. Collaborations with external groups. Reports into next GOC meeting as to these kinds of activities.
  10. Jim: Suggested Making a repository for predictions POSSIBLE ACTION ITEM?
  11. Finalizing proposed evidence code documentation – abbreviated version on web pages and more detailed on GOC Wiki (Rama)
  12. Eurie: querying communities on awareness of evidence codes – do you know what it is, what do you use it for? Also proposal of expanding, then get a feel for what would benefit them? So that we have a large audience.
  13. Sue, Michelle, Rama put evidence code proposal in the context of what we discussed today
  14. Evidence code committee. Documentation for users and curators.
  15. Evidence code Revise evidence code documentation so that a mutation in only one gene can only be IMP (protein localization IGI example)
  16. (Curators) Check whether you have used IGI in this way and update annotations
  17. (Curators) 'with' column optional for NAS - document
  18. Update evidence code decision tree in response to today's discussion on evidence code usage (Jen and EV Code WG)
  19. (Curators) only ND allowed to root nodes - clarify this in the documentation (Rama)