GO 18th Consortium Meeting Minutes Day 2: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Monday 24th September 2007, Princeton University, NJ | Monday 24th September 2007, Princeton University, NJ | ||
== Board Agenda == | |||
1. Plans for immediate future (SL) | 1. Plans for immediate future (SL) | ||
| Line 17: | Line 19: | ||
5. Evidence codes (ma) | 5. Evidence codes (ma) | ||
Overview of cross products by CJM | == Overview of cross products by CJM == | ||
… | … | ||
CP results in scratch directory. | |||
… | … | ||
| Line 44: | Line 45: | ||
DB: not straightforward to find when people took data | DB: not straightforward to find when people took data | ||
SO and Chromosonal Location – CJM and KE discuss offline. | |||
== John Day-Richter - Term Lifecycle == | |||
GET SLIDES FROM JDR | |||
Give users a temporary ID to work with when they need a new term. | |||
However many terms rejected | |||
Need to feedback to them outcome of term request. | |||
How do this? | |||
Everyone has some way of dealing with term obsoletion – therefore we can use these mechanisms to feedback to user. | |||
When request closed, use ‘consider’ or ‘replace_by’ tags to get correct term. | |||
Create mini ontology file they can update all their annotations with the new term id. | |||
'''Discussion follows….''' | |||
Revision as of 09:35, 24 September 2007
Monday 24th September 2007, Princeton University, NJ
Board Agenda
1. Plans for immediate future (SL) a. regulation b. cross products
2. Database report a. schema changes b. production
3. GA files (mike)
4. OBO-Edit (john)
5. Evidence codes (ma)
Overview of cross products by CJM
…
CP results in scratch directory.
…
Discussion gene_ontology_edit.obo file vs original file confused.
JDR – add obo version number to the filename. Then use original name as release version of file.
MA/Mike – change ‘edit’ in curators version to ‘pre_release’ to better describe it’s use. Orig file updated nightly by Stanford.
CJM: need to take versioning a little more seriously – impossible to replicate analyses. How do we cite what version of the GO we use?
Michelle – do we hide pre release file?
Cjm: no, culture of using the latest file.
Michelle: However, orig file updated daily anyway.
DB: not straightforward to find when people took data
SO and Chromosonal Location – CJM and KE discuss offline.
John Day-Richter - Term Lifecycle
GET SLIDES FROM JDR
Give users a temporary ID to work with when they need a new term.
However many terms rejected
Need to feedback to them outcome of term request.
How do this?
Everyone has some way of dealing with term obsoletion – therefore we can use these mechanisms to feedback to user.
When request closed, use ‘consider’ or ‘replace_by’ tags to get correct term.
Create mini ontology file they can update all their annotations with the new term id.
Discussion follows….