The transporter classification database.
Saier MH, Reddy VS, Tamang DG, Västermark A. · 2014
Read The transporter classification database. by Saier MH, Reddy VS, Tamang DG, Västermark A. (2014) in the Tower of Babel, a free online library of public-domain works preserved in clean, searchable text. No sign-up. The full text is served as a plain-text file at a predictable URL, where text is present: https://antarctic-labs.com/tower-of-babel/europmc-pmc3964967.txt.
Introduction
Milton H. Saier and three colleagues describe the Transporter Classification Database in 2014. Their paper appeared in Nucleic Acids Research. The database is the reference point for transport proteins. Those proteins move molecules across cell membranes. It holds more than 10,000 proteins, with no duplicates. Every known family of membrane transport systems is covered. The proteins come from all kinds of living things.
Entries sit in a five-level filing system. Broad class sits at the top. The single transport system sits at the bottom. Superfamilies are cross-linked between levels. Each family carries hand-written notes. The notes cover shape, function, mechanism, and evolution. The database links out to many other resources. It is the only scheme of its kind backed by the world biochemistry union. The paper reports the update and its software.
Catalog record
| CREATOR | Saier MH, Reddy VS, Tamang DG, Västermark A. |
|---|---|
| YEAR | 2014 |
| COLLECTION | PAPERS |
| FORMAT | TXT |
| FILE SIZE | 37 KB |
| LICENSE | CC BY 4.0 |
| RIGHTS | CC BY |
| SOURCE | Europe PMC |
Browse the full library · About the Tower of Babel
Full text
The opening of the work, from the library's hosted text:
The Transporter Classification Database By Milton H. Saier, Vamsee S. Reddy, Dorjee G. Tamang, Åke Västermark Published in: Nucleic Acids Research DOI: 10.1093/nar/gkt1097 ABSTRACT The Transporter Classification Database (TCDB; http://www.tcdb.org) serves as a common reference point for transport protein research. The database contains more than 10 000 non-redundant proteins that represent all currently recognized families of transmembrane molecular transport systems. Proteins in TCDB are organized in a five level hierarchical system, where the first two levels are the class and subclass, the second two are the family and subfamily, and the last one is the transport system. Superfamilies that contain multiple families are included as hyperlinks to the five tier TC hierarchy. TCDB includes proteins from all types of living organisms and is the only transporter classification system that is both universal and recognized by the International Union of Biochemistry and Molecular Biology. It has been expanded by manual curation, contains extensive text descriptions providing structural, functional, mechanistic and evolutionary information, is supported by unique software and is interconnected to many other relevant databases. TCDB is of increasing usefulness to the international scientific community and can serve as a model for the expansion of database technologies. This manuscript describes an update of the database descriptions previously featured in NAR database issues. INTRODUCTION: THE TC SYSTEM: DESIGN AND RATIONALIZATION In 1995, Fleischmann et al. (1) published the full genome sequence of a living organism, Haemophilus influenzae, the first time such a feat had been accomplished. This revolutionary event marked the beginning of the genomics era. Because of our long-standing interest in molecular transmembrane transport, members of the Saier laboratory recognized the need for a classification system for transport systems equivalent to the Enzyme Commission (EC) system already in existence for enzymes (2). The EC system classified enzymes strictly on the basis of function, as it was designed before sequence and phylogenetic data were available. Even before the advent of the genomics revolution, it became clear that the EC system was tremendously deficient because it could not accommodate phylogenetic data without restructuring the entire system. Although considered desirable by many, such a restructuring of the EC system has never been achieved. Even before 1995, our laboratory was conducting phylogenetic analyses of transport proteins [for review, see (3)]. We realized that phylogeny reflects protein structure, function and mechanism, and therefore, is an essential component of any molecular classification system. With a desire to conduct whole genome analyses of transporters, we recognized a need for a universal system of transport protein classification that took cognizance of both function and phylogeny. With this conviction in mind, we designed what is now known as the Transporter Classification (TC) system. Transporters in the TC Database (TCDB) are classified using a functional/phylogenetic five-tier system (4,5) as follows: N1.L1.N2.N3.N4, where N is a number and L is a letter: N1 is the class; L1 is the subclass; N2 is the family (sometimes actually a superfamily); N3 is the subfamily; (or family in the case of a superfamily) and N4 is the actual transport system. Classes 1–5 are well defined (channels, secondary carriers, primary active transporters, group translocators and transmembrane electron carriers, respectively); classes 6–7 are presently empty, being reserved for yet to be discovered classes, and classes 8 and 9 represent accessory proteins and incompletely characterized proteins, respectively. This system, describing transport systems from all types of living organisms, was formally adopted by the International Union of Biochemistry and Molecular Biology (IUBMB) in June 2001 and has served the international scientific community effectively ever since (6–9). DATABASE CONTENT AND ACCESS Encoded within the relational database schema is the functional/phylogenetic TC taxonomy (Figure 1). Users can access the information through our intuitive interface, where information can be viewed at different levels of granularity by returning populated HTML data to the web browser client (the superficial tier). Users can enter at the top levels for information about classes and families and descend to the deepest level about individual proteins. Figure 1.Current MySQL schema, displayed using Workbench 6.0 CE and showing the tables currently in TCDB’s database architecture. Each line in a table represents a column and displays which datatype (such as int, varchar, text, etc.) can be stored. Ten tables, which are not being used directly by TCDB but that have been used for maintenance tasks are not shown in the diagram: test, lang error, proteinold, tc2acc broke, tc2acc 1, flags, cflags, temp_tms, temp_preds and misc. A table that has a trifork (entity relationships) pointing toward it contains a column with explicit IDs from another table. The tables having no entity relationships are grouped on the left. The diagram contains four layers (left to right, and from top to bottom): the protein layer (green), the family layer (yellow), the ontology layer (blue) and the compounds layer (red). Since its last publication in the NAR database issue in 2009 (5), there has been significant change in the database design (schema above). Some basic issues pertaining to data integrity, redundancy and management have led to conversion of the MySQL Table Engine from MyISAM to InnoDB. Perhaps the most important justification for this conversion is the fact that different levels of TC classification have a type of parent–child relationship. A foreign key constraint should allow cascading action when a row (tuple) is inserted/updated/deleted. Thus, all related tables are affected, leaving no orphaned records. Roughly one half of the schema follows the standard relationships between class, subclass, superfamily, family, cluster or subfamily and system, and the other half shows tables of information pertaining to unique UniProt protein accession numbers. The steps involved and basic ideas behind the TCDB Admin interface for curation are the same as above and follow the DB design schema. However, the look and feel of the interface has changed since its update in 2010, along with some new options such as ‘View Task Queue’ and ‘View Staff Logs’. We share our mapping file with different databases, and these files are automatically updated every time a new protein is added to the database. The entire web interface has been revamped. The new look and feel should be consistent across all major browsers, easier to navigate, URL friendly, and overall, a huge improvement from the previous HTML frame-based web pages. For example, the browse tab for viewing the TC System (http://www.tcdb.org/browse.php) has been entirely redesigned using jQuery. For a more detailed description of the capabilities available to the user, see Wakabayashi et al. (10). In addition to the search option under the search tab, one can search TCDB from a search box on the main page using single or multiple terms including TC ID#, key word, protein name or abbreviation, organismal source, author name, UniProt accession number, PDB ID number, associated disease, reference, etc. The following details are returned with a protein search, or can be easily accessed following such a search: (i) TC ID#, (ii) reference, (iii) accession number, (iv) protein name, (v) length, (vi) molecular weight, (vii) species, (viii) predicted number of TMSs, (ix) location/topology/orientation and (x) database of interacting proteins (DIPs) and Pfam reference. The user is also given an option of either BLASTING/PSI-BLASTING the protein against the non-redundant National Center for Biotechnology Information (NCBI) or TCDB (accessed from the