Inferred from Electronic Annotation (IEA)
IEA: Inferred from Electronic Annotation
Note: Different children of IEA are used in Protein2GO, and GPAD, but not in GAF. Should we document those evidence codes on this page, as well?
Note: Annotations using the IEA code should be reviewed after one year, any older than this date will be deleted.
Annotations based on "matches" in sequence similarity comparisons if they have not been reviewed by a curator Annotations transferred from database records, if not reviewed by a curator Annotations made on the basis of keyword mapping files, if not reviewed by a curator If annotations based on sequence similarity based methods have been reviewed by a curator, use ISS instead and change the reference from the one that describes the computational analysis to one that says that the curator reviewed the sequence similarity and approved it. Used for annotations that depend directly on computation or automated transfer of annotations from a database, particularly when the analysis is performed internally and not published. A key feature that distinguishes this evidence code from others is that it is not made by a curator; use IEA when no curator has checked the specific annotation to verify its accuracy. The actual method used (BLAST search, Swiss-Prot keyword mapping, etc.) doesn't matter.
When the method used to make annotations using the IEA code is performed internally by the annotating group and is not published, a short description of the method should be written and added to the GO Consortium's collection of GO references, where it will be given a GO_REF ID which can be used to cite the reference in gene association files.
Examples where the IEA evidence code should be used:
Annotations based on "matches" in sequence similarity comparisons if they have not been reviewed by a curator. If annotations based on sequence similarity based methods have been reviewed by a curator, use ISS instead. Annotations transferred from database records, if not reviewed by a curator. If such annotations are reviewed by a curator and the database record has no linked publication, consider the NAS code. Annotations made on the basis of keyword mapping files, if not reviewed by a curator Examples where the IEA evidence code should not be used:
Annotations based on "matches" in sequence similarity comparisons and which have been reviewed by a curator should be made with ISS code. Annotations transferred from database records, where the annotation is reviewed by a curator should not receive the IEA code. If the source is not traceable and the annotation is worth making, NAS should be used. Usage of the With/From Column for IEA
At the January 2007 GOC meeting, it was agreed that it will be required to make an entry in the with/from column for all annotations made after May 1, 2007 when using this evidence code to indicate what individual sequences, sequence objects, methods, keyword mapping files, etc. are the basis of the annotation. When multiple entries are placed in the with/from field, they are separated by pipes.
DB Object ID
DB Object Symbol
... ... UniProt:A0A7W6 A0A7W6_9PARI GO:0006118 GOA:interpro|GO_REF:0000002 IEA InterPro:IPR005797 ... ... UniProt:A0A7W4 A0A7W6_9PARI GO:0006118 GOA:spkw|GO_REF:0000004 IEA SP_KW:KW-0496 ... ... UniProt:A0K8M1 A0K8M1_BURCH GO:0004830 GOA:spec|GO_REF:0000003 IEA EC:22.214.171.124 ... ... UniProt:A0KAB8 Y2695_BURCH GO:0008237 GOA:hamap|GO_REF:0000020 IEA HAMAP:MF_00009 ... ... UniProt:O77797 AKAP3_BOVIN GO:0009434 GOA:compara|GO_REF:0000019 IEA Ensembl:ENSMUSP00000093091 ...