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

From GO Wiki
Jump to: navigation, search
m
m
Line 1: Line 1:
 
 
==Why do you want GO annotations?==
 
==Why do you want GO annotations?==
  
Line 9: Line 8:
 
you can manually annotate them. <br>
 
you can manually annotate them. <br>
  
===I have a set of ESTs and I would like to attach annotations.===<br>
+
===I have a set of ESTs and I would like to attach annotations.===
 
You can cluster and apply ids.<br>  
 
You can cluster and apply ids.<br>  
 
then run blastX or run gene predictions programme then blastP<br>
 
then run blastX or run gene predictions programme then blastP<br>
Line 15: Line 14:
 
You can also do manual annotations to the predicted proteins. <br>
 
You can also do manual annotations to the predicted proteins. <br>
  
===I have a genome sequence===<br>
+
===I have a genome sequence===
 
you assemble the genome sequence and do gene calls. <br>
 
you assemble the genome sequence and do gene calls. <br>
 
you get a cds seqence or a protein sequence or both. <br>
 
you get a cds seqence or a protein sequence or both. <br>
Line 21: Line 20:
 
Or take protein predictions and interproscan or blastP and then manual annotations.<br>
 
Or take protein predictions and interproscan or blastP and then manual annotations.<br>
  
===I have a microarray data set===<br>
+
===I have a microarray data set===
 
cdna or oligos?<br>
 
cdna or oligos?<br>
 
do they have ids?<br>
 
do they have ids?<br>
Line 30: Line 29:
 
Can you get more upto date annotations than those provided with your tool?<br>
 
Can you get more upto date annotations than those provided with your tool?<br>
  
===A have a peptide sequence. ===<br>
+
===A have a peptide sequence. ===
 
what gene is it?<br>
 
what gene is it?<br>
 
Can you map to known genes with ids?<br>
 
Can you map to known genes with ids?<br>

Revision as of 07:52, 22 August 2007

Why do you want GO annotations?

I represent a small lab working on biological area

If you have protein sequence in a text file, maybe from a load of papers you read.
you can blastP and get e-annotation.
you can run through interproscan and get the domains interpro2go annotations.
you can manually annotate them.

I have a set of ESTs and I would like to attach annotations.

You can cluster and apply ids.
then run blastX or run gene predictions programme then blastP
you can run interpro and it will try to find the longest orf.
You can also do manual annotations to the predicted proteins.

I have a genome sequence

you assemble the genome sequence and do gene calls.
you get a cds seqence or a protein sequence or both.
then you can take the cds and do blastX or interproscan.
Or take protein predictions and interproscan or blastP and then manual annotations.

I have a microarray data set

cdna or oligos?
do they have ids?
How do they relate to the genes?
Do the genes have GO annotations?
Is there a mod for your species that does GO?
Have you talked to them?
Can you get more upto date annotations than those provided with your tool?

A have a peptide sequence.

what gene is it?
Can you map to known genes with ids?
can you retrieve the annotations or make annotations.



Electronic annotation

IEAoverview.jpg

This diagram illustrates some of the main ways of making electronic annotation. It should be read from the top down. The diagram shows sequences from UniProt having electronic GO annotation assigned by several computational methods. All of these methods involve use of mapping files. For more information on mappings see http://www.geneontology.org/GO.indices.shtml.

InterPro Mapping

In the case of the Interpro mapping it is possible to assign electronic GO annotation to your sequences based on InterPro domains and a number of other criteria. For example if your sequence has a DNA binding domain then it makes sense to electronically annotate it to the DNA binding function term. For more information on InterPro mapping please see http://gocwiki.geneontology.org/index.php/InterProScan.

Keyword Mapping

This part of the diagram illustrates how sequences already categorised using the SwissProt keyword mapping can have GO annotation automatically applied by transferring via the keyword mapping file.

HAMAP

HAMAP is a system that categories sequences based on family or subfamily characteristics and is applied to bacterial, archaeal and plastid-encoded proteins. GO annotation can be automatically applied to such sequences using the mapping file between HAMAP and GO.

Enzyme Commission

The Enzyme Commission database categories enzymes by the reactions they catalyse. If your sequences are already categories by EC then you can transfer GO annotations using the mapping file of EC to GO categories.

Other mappings

These are just a few examples of mapping files that can be used to transfer annotations to your sequence objects. Many other mappings are available, and if there is not a mapping file between GO and your current annotation system then we can assist you in making one.

Blast

You can also make electronic annotations by blasting your sequence against manually annotated sequences and transferring the GO annotations across to your sequence. The threshold of similarity in this process is up to you, and depends on your requirements.



Literature Annotation


Below is a schematic diagram giving an introduction to the steps involved in literature-based GO annotation. If you are interested in carrying out literature-based annotation you can receive full tuition in the process by attending a GO annotation camp or by working with an individual GO Consortium annotation mentor.

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?
  • Your database must have an internal rule that object identifiers are never reused.