PIVOT: protein interacions visualizatiOn tool.

Nir Orlev; Ron Shamir; Yosef Shiloh

doi:10.1093/bioinformatics/btg426

Home/Archive/PubMed

PubMed · 14960471

PIVOT: protein interacions visualizatiOn tool.

Nir Orlev·Ron Shamir·Yosef Shiloh

View original source ↗Export metadata ↓

Abstract

Protein Interaction VisualizatiOn Tool (PIVOT) is a visualization tool for protein-protein interactions. It allows the user to create personal data sets of interactions by combining information from private and public data sources. The user can gradually access the interactions' data using a clear interactive map that is focused on the researcher's protein of interest, and is reshaped and expanded in response to his/her queries. It also offers several visual enhancements and intelligent queries that help the user efficiently study it. PIVOT allows the user to search the interactions data set for paths connecting proteins that are expected to co-operate. The user can also employ PIVOT to predict unknown interactions among proteins, based on interactions among their homologous proteins in other species.

Explore related subjects

Database Management Systems Databases, Protein Information Storage and Retrieval Protein Binding Protein Interaction Mapping Proteins Sequence Alignment Sequence Analysis, Protein Sequence Homology, Amino Acid Software User-Computer Interface Journal Article

Keep this discovery

Explore connections, maps & timelines

BibTeX RIS

Nir Orlev, Ron Shamir, Yosef Shiloh. 2004-01-22. PIVOT: protein interacions visualizatiOn tool.. https://doi.org/10.1093/bioinformatics%2Fbtg426

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related citations

PubMed2004

PDZBase: a protein-protein interaction database for PDZ-domains.

SUMMARY: PDZBase is a database that aims to contain all known PDZ-domain-mediated protein-protein interactions. Currently, PDZBase contains approximately 300 such interactions, which have been manually extracted from > 200 articles. The database can be queried through both sequence motif and keyword-based searches, and the sequences of interacting proteins can be visually inspected through alignments (for the comparison of several interactions), or as residue-based diagrams including schematic secondary structure information (for individual complexes).

Database Management Systems↗

PubMed2004

GOChase: correcting errors from Gene Ontology-based annotations for gene products.

SUMMARY: The Gene Ontology (GO) is a controlled biological vocabulary that provides three structured networks of terms to describe biological processes, cellular components and molecular functions. Many databases of gene products are annotated using the GO vocabularies. We found that some GO-updating operations are not easily traceable by the current biological databases and GO browsers. Consequently, numerous annotation errors arise and are propagated throughout biological databases and GO-based high-level analyses. GOChase is a set of web-based utilities to detect and correct the errors in GO-based annotations.

Database Management Systems↗

PubMed2004

Tools for loading MEDLINE into a local relational database.

BACKGROUND: Researchers who use MEDLINE for text mining, information extraction, or natural language processing may benefit from having a copy of MEDLINE that they can manage locally. The National Library of Medicine (NLM) distributes MEDLINE in eXtensible Markup Language (XML)-formatted text files, but it is difficult to query MEDLINE in that format. We have developed software tools to parse the MEDLINE data files and load their contents into a relational database. Although the task is conceptually straightforward, the size and scope of MEDLINE make the task nontrivial. Given the increasing importance of text analysis in biology and medicine, we believe a local installation of MEDLINE will provide helpful computing infrastructure for researchers. RESULTS: We developed three software packages that parse and load MEDLINE, and ran each package to install separate instances of the MEDLINE database. For each installation, we collected data on loading time and disk-space utilization to provide examples of the process in different settings. Settings differed in terms of commercial database-management system (IBM DB2 or Oracle 9i), processor (Intel or Sun), programming language of installation software (Java or Perl), and methods employed in different versions of the software. The loading times for the three installations were 76 hours, 196 hours, and 132 hours, and disk-space utilization was 46.3 GB, 37.7 GB, and 31.6 GB, respectively. Loading times varied due to a variety of differences among the systems. Loading time also depended on whether data were written to intermediate files or not, and on whether input files were processed in sequence or in parallel. Disk-space utilization depended on the number of MEDLINE files processed, amount of indexing, and whether abstracts were stored as character large objects or truncated. CONCLUSIONS: Relational database (RDBMS) technology supports indexing and querying of very large datasets, and can accommodate a locally stored version of MEDLINE. RDBMS systems support a wide range of queries and facilitate certain tasks that are not directly supported by the application programming interface to PubMed. Because there is variation in hardware, software, and network infrastructures across sites, we cannot predict the exact time required for a user to load MEDLINE, but our results suggest that performance of the software is reasonable. Our database schemas and conversion software are publicly available at http://biotext.berkeley.edu.

Database Management Systems↗