14.06.2013 Views

Databases and Systems

Databases and Systems

Databases and Systems

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

223<br />

other databanks, <strong>and</strong> define specific views on application results. For example: the<br />

default view for a BLAST search links all BLAST hits to the databank searched (e.g.<br />

SWISS-PROT), <strong>and</strong> displays the description field from there. Since application<br />

results from further application launches are accumulated, one can answer questions<br />

such as “Which hits were reported by the last search but not by the previous search?”,<br />

or “In the last three searches, which hits had a bit-score above 30?” The comparison<br />

is done using a link operation. This method can also be used to collate different<br />

algorithms’ performance on a particular problem (e.g., a specific search by both<br />

BLAST <strong>and</strong> FASTA, or the effects of different parameters settings on an algorithm’s<br />

performance).<br />

As soon as the application program has finished running, its results are thus ‘just<br />

another databank’, which are consequently parsed <strong>and</strong> indexed. Each application<br />

therefore has an associated SRS databank parser, database structure description <strong>and</strong><br />

documentation. This documentation is augmented by the help text for application<br />

parameters.<br />

SRS Views<br />

In the past within SRS, the retrieved information was always a set of entries each<br />

from a single databank. The specification of views was added so that the user can<br />

define virtual entries that may include information from many sources. Views can be<br />

used to treat the sum of all installed databanks as a single structure where user<br />

defined entities can freely span databank boundaries.<br />

SRS regards an entry as a list of data-fields. The simplest form of a view acts as a<br />

filter <strong>and</strong> allows only selected fields to be displayed. For instance, a view could be<br />

defined to display only the ID, the description <strong>and</strong> the line containing the sequence<br />

length for SWISS-PROT entries as shown in figure 4. This type of view, the ‘list-<br />

view’, displays the selected data-fields in the order they occur within the entry <strong>and</strong> in<br />

their original format which includes line codes or field labels. It is mostly useful for<br />

‘turning off undesired information during browsing large sets of entries.<br />

ID ACHA_HUMAN STANDARD; PRT; 402 AA.<br />

DE ACETYLCHOLINE RECEPTOR PROTEIN, ALPHA CHAIN PRECURSOR.<br />

SQ SEQUENCE 482 AA; 54545 MW; E050B513 CRC32;<br />

Figure 4. A SWISS-PROT entry displayed by a list-view.<br />

The table-view provides more sophistication <strong>and</strong> possibilities. The entry in the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!