Mock-ups for GO website: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 17: | Line 17: | ||
===General principles for sequence ids=== | ===General principles for sequence ids=== | ||
*You must have stable identifiers for your objects. <br> | |||
*You must provide information on what the object is. For example, is it a protein or nucleotide. | |||
It doesn't matter if a nucleotide sequence is a gene, a genome, or an EST as long as you | |||
know whether it is nucleotide sequence or a protein. <br> | |||
*If a sequence identifier has become obsolete then you should be able to track down what has | |||
replaced it. What is the mechanism for that?<br> | |||
*Your database must have an | |||
internal rule that object identifiers are never reused. <br> |
Revision as of 06:32, 22 August 2007
Sending annotations to the consortium
If you are sending annotations to the consortium then please bear these general rules in mind.
Updating the annotations
The gene ontology structure changes over time and so it is essential that annotations should be maintained long term to accommodate these changes. If you are submitting annotations to the Consortium then you should either ensure that your group has funding to maintain the annotations, or that you have made an agreement with another group that they will carry out maintenance.
General principles for sequence ids
- You must have stable identifiers for your objects.
- You must provide information on what the object is. For example, is it a protein or nucleotide.
It doesn't matter if a nucleotide sequence is a gene, a genome, or an EST as long as you
know whether it is nucleotide sequence or a protein.
- If a sequence identifier has become obsolete then you should be able to track down what has
replaced it. What is the mechanism for that?
- Your database must have an
internal rule that object identifiers are never reused.