| Literature DB >> 20974635 |
Cristina Aurrecoechea1, Ana Barreto, John Brestelli, Brian P Brunk, Elisabet V Caler, Steve Fischer, Bindu Gajria, Xin Gao, Alan Gingle, Greg Grant, Omar S Harb, Mark Heiges, John Iodice, Jessica C Kissinger, Eileen T Kraemer, Wei Li, Vishal Nayak, Cary Pennington, Deborah F Pinney, Brian Pitts, David S Roos, Ganesh Srinivasamoorthy, Christian J Stoeckert, Charles Treatman, Haiming Wang.
Abstract
AmoebaDB (http://AmoebaDB.org) and MicrosporidiaDB (http://MicrosporidiaDB.org) are new functional genomic databases serving the amoebozoa and microsporidia research communities, respectively. AmoebaDB contains the genomes of three Entamoeba species (E. dispar, E. invadens and E. histolityca) and microarray expression data for E. histolytica. MicrosporidiaDB contains the genomes of Encephalitozoon cuniculi, E. intestinalis and E. bieneusi. The databases belong to the National Institute of Allergy and Infectious Diseases (NIAID) funded EuPathDB (http://EuPathDB.org) Bioinformatics Resource Center family of integrated databases and assume the same architectural and graphical design as other EuPathDB resources such as PlasmoDB and TriTrypDB. Importantly they utilize the graphical strategy builder that affords a database user the ability to ask complex multi-data-type questions with relative ease and versatility. Genomic scale data can be queried based on BLAST searches, annotation keywords and gene ID searches, GO terms, sequence motifs, protein characteristics, phylogenetic relationships and functional data such as transcript (microarray and EST evidence) and protein expression data. Search strategies can be saved within a user's profile for future retrieval and may also be shared with other researchers using a unique strategy web address.Entities:
Mesh:
Year: 2010 PMID: 20974635 PMCID: PMC3013638 DOI: 10.1093/nar/gkq1006
Source DB: PubMed Journal: Nucleic Acids Res ISSN: 0305-1048 Impact factor: 16.971
Searches available in AmoebaDB and MicrosporidiaDB
| Search type | Description |
|---|---|
| Text | Genes may be identified based on the presence of a particular word anywhere in the gene record. A user may search all gene record fields or select specific categories such as product name or user comments. |
| Gene IDs | Genes can be identified based on their IDs. This includes current and old IDs. |
| Species | Genes may be identified based on the species they are present in. |
| Genomic location | Genes may be identified based on their exact scaffold, contig or chromosome coordinates. |
| Gene type | Genes may be identified based on whether they are coding or non-coding. |
| Exon count | Genes may be identified based on number of exons. |
| Molecular weight | Genes may be identified based on their calculated molecular weight from the predicted proteins. |
| Isoelectric point | Genes may be identified based on their calculated isoelectric point from the predicted proteins. |
| Predicted signal peptide | Genes may be identified based on whether their predicted protein contains a SignalP predicted signal zpeptide. |
| Transmembrane domain count | Genes may be identified based on the number of predicted transmembrane domains present in their predicted proteins. |
| Protein motif pattern | Genes may be identified based on the presence of a specific amino acid motif. |
| InterPro domain | Genes may be identified based on the presence of InterPro domains in their predicted proteins. |
| BLAST | Genes may be identified using BLAST. |
| EST evidence | Genes may be identified based on whether they also have EST evidence of expression. |
| Microarray evidence | Genes may be identified based on their expression profile determined from available microarray experiments. |
| GO term | Genes may be identified based on genome ontology terms. |
| EC number | Genes may be identified based on enzyme commission numbers. |
| Orthologs and paralogs | For the identification of orthologs and paralogs of a genes of interest in available species. |
| Orthology phylogenetic profile | Genes may be identified based on whether they have orthologs or paralogs in other organisms. |
aCurrently only available for AmoebaDB.
Figure 1.Screen shot of the AmoebaDB homepage. The layout of the MicrosporidiaDB homepage is exactly the same. (A) The banner section is a constant fixture on all AmoebaDB and MicrosporidiaDB web pages. It contains links to register and login, all searches, tools and information pages, the basket and favorites and ID and text search windows for rapid access from anywhere on the sites. (B) The side panel on the homepage provides expandable tabs that reveal links to a EuPathDB data summary table, community news items, links to community resources, web tutorials and additional information and help links. The central portion of the home page includes all available searches and tools—gene specific searches in (C), searches against other data types such as genomic sequence, open reading frames and ESTs in (D) and tools, such as BLAST, sequence retrieval and the genome browser in (E).
Figure 2.AmoebaDB or MicrosporidiaDB results page. Once a user runs a search they are taken to the result summary page that includes a search strategy builder in (A), a filter table showing the distribution of results among related species in (B) and an interactive and configurable table of results in (C). Clicking on the IDs in the results reveals the record page—a gene record page is shown in (D) where a user can view gene-specific information such as synteny and available data, and can add user comments (E) or link to the genome browser to view additional data displayed in the genomic context (F).
Figure 3.A search strategy. (A) The search strategy cycle begins with adding a step to the first search (1), which reveals a popup window with all search options. Once a search type is selected (2), search parameters can be modified and a user chooses how to combine these results with the previous step (3). Clicking on the run step button completes the cycle and expands the strategy horizontally (4). This cycle can be repeated to develop complex search strategies (B). Individual steps in a strategy can be revised, renamed, deleted or transformed into orthologs. Also, the strategy itself can be renamed, copied, saved, deleted and shared with a unique URL (red insert).