Difference between revisions of "Mock-ups for GO website"

From GO Wiki
Jump to: navigation, search
m
m
Line 17: Line 17:
 
===General principles for sequence ids===
 
===General principles for sequence ids===
  
  You must have stable ids for your objects. <br>
+
  You must have stable identifiers for your objects. <br>
  You must provide information on what the object is. Protein, nucleotide or whatever.
+
  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  
+
  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. (Although the gene_association
+
  know whether it is nucleotide sequence or a protein. <br>
file column says you can say 'gene', you must say if the sequence id is protein or DNA.)<br>
+
  If a sequence identifier has become obsolete then you should be able to track down what has  
  If a sequence id has become obsolete then you should be able to track down what has  
 
 
  replaced it. What is the mechanism for that?<br>
 
  replaced it. What is the mechanism for that?<br>
  If people are submitting annotations to the GO consortium then they must have an  
+
  If people are submitting annotations to the GO Consortium then they must have an  
  internal rule that their object ids are never reused. <br>
+
  internal rule that their object identifiers are never reused. <br>

Revision as of 02:31, 22 August 2007

IEAoverview.jpg


Literature original-4thMay.png


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?
If people are submitting annotations to the GO Consortium then they must have an internal rule that their object identifiers are never reused.