Reference Genome Database Requirements Discussion 2007 (Retired): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This is the place to discuss features and requirements for the Reference Genome Database being designed to replace the Google Spreadsheet system currently in use. | This is the place to discuss features and requirements for the Reference Genome Database being designed to replace the Google Spreadsheet system currently in use. | ||
(here's one to get us started --chris): | |||
== Ensures consistent use of identifiers == | |||
Identifiers must ''unambiguously'' identify a single entry in a database. | |||
Identifiers should conform to the following syntax: | |||
DBAuthority : LocalID | |||
DBAuthority should be in the GO xrefs metadata list: | |||
* http://www.geneontology.org/cgi-bin/xrefs.cgi | |||
E.g. | |||
FB:FBgn0000001 | |||
Curators should not be expected to memorise identifiers, so a data entry system should allow them to enter symbols etc and have this resolved as an ID eg using some automatic lookup mechanism |
Revision as of 18:33, 5 April 2007
This is the place to discuss features and requirements for the Reference Genome Database being designed to replace the Google Spreadsheet system currently in use.
(here's one to get us started --chris):
Ensures consistent use of identifiers
Identifiers must unambiguously identify a single entry in a database.
Identifiers should conform to the following syntax:
DBAuthority : LocalID
DBAuthority should be in the GO xrefs metadata list:
E.g.
FB:FBgn0000001
Curators should not be expected to memorise identifiers, so a data entry system should allow them to enter symbols etc and have this resolved as an ID eg using some automatic lookup mechanism