[Bio] / FigTutorial / annotation_clearinghouse.html Repository:
ViewVC logotype

View of /FigTutorial/annotation_clearinghouse.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.4 - (download) (as text) (annotate)
Tue Oct 30 20:20:51 2007 UTC (12 years, 2 months ago) by overbeek
Branch: MAIN
CVS Tags: rast_rel_2014_0912, rast_rel_2008_06_18, rast_rel_2008_06_16, rast_rel_2008_07_21, rast_rel_2010_0928, rast_2008_0924, rast_rel_2008_09_30, rast_rel_2010_0526, rast_rel_2014_0729, rast_rel_2009_05_18, rast_rel_2009_0925, rast_rel_2010_1206, rast_rel_2010_0118, rast_rel_2009_02_05, rast_rel_2011_0119, rast_rel_2008_12_18, rast_rel_2008_10_09, rast_release_2008_09_29, rast_rel_2008_04_23, rast_rel_2008_08_07, rast_rel_2009_07_09, rast_rel_2010_0827, myrast_33, rast_rel_2011_0928, rast_rel_2008_09_29, rast_rel_2008_10_29, rast_rel_2009_03_26, rast_rel_2008_11_24, HEAD
Changes since 1.3: +35 -49 lines
update the to ACH writeup

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head></head><body><div align="center">
<h1>The Annotation Clearinghouse</h1> 

The <b>Annotation Clearinghouse</b> is a rather simple service.  It does two things:
<li>If you give it the ID of a protein (e.g., <b>tr|Q40XE9</b>, <b>uni|Q40XE9</b>, <b>fig|266940.1.peg.3572</b>,
<b>gi|69288893</b>, <b>NP_251014</b>, <b>kegg|pae:PA2324</b>, or
<b>sp|Q03224</b>), the server will return IDs of other proteins that it knows about that have the same sequence.
Furthermore, associated with each ID will be the function asserted for that ID by the major annotation teams that use that ID
(at least those for which we can download their annotations).
Thus, at any point where you have an ID, you can quickly get opinions about that protein (or other proteins that have
the same sequence).  To see how this works, just go to <a href="http://clearinghouse.nmpdr.org/aclh.cgi">the 
clearinghouse</a>, type in <b>sp|P0A753</b>, and look at the returned table.  We emphasize that all
of the proteins in this table are character-for-character identical, except for small variations at
the start (due to differing calls of start positions).
</li><li>The second aspect of the server involves allowing experts to express reliable assertions.  That is, we are
gathering assertions of function for proteins where each assertion is being made by an expert, and the expert 
believes the assertion to be reliable (i.e., it is not a speculation or guess). It is understood
that even "reliable" assertions are sometimes wrong or incomplete, and we encourage the experts to update
their assertions in such cases.  
When users of the annotation clearinghouse ask for assertions about the protein with a given ID, the expert
assertions are also provided, and they are colored
so that they stand out.  In the table returned for <b>sp|P0A753</b> you will see some assertions made
by Andrei Osterman who is known for his research in NAD metabolism.
</li></ol>We update the sequences used to provide these current annotations frequently, trying to acquire the latest
opinions from each of the annotation groups.  We solicit help from experts, when it is known that
some annotations are in error.  We invite experts to register and contribute their assertions, and we
believe that the annotation groups will carefully monitor such assertions and that it will lead to
steady improvement of the annotations contributed by the major annotation efforts.
<h3>Why Is This Important?</h3>Both services are important, but for
quite distinct reasons. &nbsp;The first service, the gathering of assertions
of function from annotation teams from around the world, allows a user
to rapidly gather a set of opinions for comparison. &nbsp;In effect, the
user has access to the best efforts from a number of groups
simultaneously. &nbsp;All well-known annotation efforts actively compare
their annotations to all others that are publicly-available. &nbsp;Each of
these annotation efforts must actively gather annotations for
comparison. &nbsp;This represents an unnecessary duplication of effort, and
in many cases the gathering of annotations is not systematic leading to
collections that are often out of date.<br><br>The
second service allows experts to contribute assertions. &nbsp;In almost
all cases, we would expect the annotation efforts to observe these and
adjust their annotations accordingly. &nbsp;The result will be rapid
correction of many errors that at this point in time tend to persist
for years. &nbsp;We all know of cases in which published results
contradict the annotations in the archives, and even remain unnoticed
by some of the most reputable annotation efforts. &nbsp;This service
will offer a mechanism that can be used by experts to draw attention to
errors that persist in the public colections (who has not seen an
obvious error and wondered "<span style="font-style: italic;">How can I get this corrected without consuming much effort).</span><br><br>Making
these services easily accessible to the bioinformatics comunity will
allow tool-builders access to data that has been certified by experts.
&nbsp;Even though the<br>expert assertions will probably never cover a
majority of the protein sets, they will represent a sizable sample of
very reliable assertions. &nbsp; As such, teams building automated
annotation pipelines will have a growing body of data against which
they can calibrate their efforts. <br><h2>The Simple Programatic Interface</h2>

Most annotation efforts use a fairly simple approach: they use blast to find a set of similar sequences,
then they gather annotations from a few sources for these similar proteins, and finally they integrate
these annotations for similar sequences into an assertion for their protein of interest.
The annotation clearinhouse provides a simple way to gather current annotations from all of the major
annotation efforts.
Here is a simple Perl program that takes a set of IDs, goes across the web to attain current
annotations, and then displays the acquired annotations.  We offer it soley to illustrate
how straightforward it is to access this data:

</p><pre>#!/usr/bin/perl<br><br>while (defined($_ = &lt;STDIN&gt;))<br>{<br>    if ($_ =~ /(\S+)/)<br>    {<br>        $set = &amp;get_set($1);<br>        foreach $entry (@$set)<br>        {<br>            print join("\t",@$entry),"\n";<br>        }<br>    }<br>}<br><br>sub get_set {<br>    my($id) = @_;<br><br>    my $tmpF = "/tmp/download.$$";<br>    my $url  = "http://clearinghouse.nmpdr.org/aclh.cgi?page=SearchResults&amp;raw_dump=1&amp;query=$id";<br>    system "wget -O $tmpF '$url' &gt; /dev/null 2&gt; /dev/null";<br><br>    open(TMP,"&lt;$tmpF") || die "could not open $tmpF";<br>    while (defined($_ = &lt;TMP&gt;) &amp;&amp; ($_ !~ /^Identifier/)) {}<br>    chomp;<br>    my $set = [];<br>    push(@$set,[split(/\t/,$_)]);<br>    while (defined($_ = &lt;TMP&gt;) &amp;&amp; ($_ =~ /\S/))<br>    {<br>        chomp;<br>        push(@$set,[split(/\t/,$_)]);<br>    }<br>    close(TMP);<br>    unlink $tmpF;<br>    return $set;<br>}<br></pre>The routine <i>get_set($id)</i> can easily be used by any Perl programmer
to download any desired protein sets. &nbsp;Note that the command&nbsp;<span style="font-style: italic;">wget</span> must be accessible via your path.<br><br><h2></h2>

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3