Protein Sequence Database
A protein sequence database is a curated collection of amino acid sequences representing proteins from all domains of life. These databases store sequence data, functional annotations, and cross references to other biological resources. This guide is for life sciences researchers, bioinformatics beginners, and anyone who needs to retrieve, analyze, or interpret protein sequences for their projects. The information here draws from authoritative training resources such as NCBI Bookshelf and EMBL-EBI Training.
Protein sequence databases allow you to identify a protein of interest, compare it to known sequences, infer function, and design experiments. Understanding their structure, coverage, and limitations is essential for rigorous bioinformatics practice. This article provides a practical framework to navigate these databases effectively.
At a Glance
| Database | Type | Coverage | Curated | Key Use Case |
|---|---|---|---|---|
| UniProtKB/Swiss-Prot | Primary, curated | Reviewed entries from all species | Yes (manual) | High confidence functional annotation |
| UniProtKB/TrEMBL | Primary, automated | All sequences from translations of EMBL | Automated | Large scale searches, novel sequences |
| NCBI Protein (RefSeq) | Primary, curated | Non redundant reference sequences from major organisms | Yes (manual) | Genome based protein sets |
| Protein Data Bank (PDB) | Structure derived | Experimentally determined 3D structures | Yes | Structural biology, sequence structure links |
| Ensembl/Genome Browsers | Genome derived | Predicted proteins from genomes | Mixed | Gene level protein queries |
Core Concepts
A protein sequence database stores sequences as strings of amino acids using the standard 20 letter code. NCBI Bookshelf explains that these databases fall into two categories: primary databases that contain original sequence data derived from experiments or genome translations, and secondary databases that add curated annotations. UniProt, for instance, provides both Swiss-Prot (manually reviewed) and TrEMBL (computationally annotated) entries.
Accession numbers are the stable identifiers used to retrieve a specific sequence version. For example, a UniProt accession like P68871 identifies human beta globin. The same protein may appear in multiple databases under different accessions but cross references are provided. Understanding the difference between a sequence version and an entry version is critical when citing data in publications.
Decision Points for Choosing a Database
Different tasks require different databases. For homology searching with BLAST, both UniProt and NCBI Protein work well, but UniProt offers better functional annotation. When you need high quality annotation for a specific human protein, use Swiss-Prot. For novel sequences from a genome project, TrEMBL or RefSeq are more appropriate. The EMBL-EBI Training resource provides decision trees for choosing between UniProt, RefSeq, and Ensembl based on your organism and data type.
Structure derived databases such as PDB are essential when you need the actual three dimensional fold. PDB entries also contain sequence information, but coverage is limited to proteins with solved structures. For most sequence only querying, UniProt is the first stop.
Practical Workflow or Implementation Sequence
Follow this workflow to retrieve and validate a protein sequence for your research.
- Define your target. If you have a known protein name or gene symbol (e.g., BRCA1 in human), start at UniProt. If you have a nucleotide sequence, translate it using a tool like EMBOSS Transeq, then search with BLASTP against UniProt.
- Perform the search. On the UniProt website, type the name or identifier. Use filters to restrict to reviewed (Swiss-Prot) entries if possible. For Galaxy Training Network workflows, you can automate batch retrieval using the UniProt API or the NCBI Entrez programming utilities.
- Examine the entry. Look for the sequence section, the function annotation, subcellular location, and post translational modifications. Check the evidence tags that support each annotation. If the annotation is tagged as "inferred from electronic annotation" (IEA), treat it as provisional.
- Download the sequence in FASTA format. Include the header line as it contains the accession and description.
- Verify the sequence. Run a quick BLAST against the non redundant database to ensure your sequence matches the expected hits. This step catches truncated or incorrectly retrieved sequences.
- Record the accession number and date of retrieval. For reproducibility, save the exact version (e.g., UniProt P04637 2).
- If you need multiple sequences (e.g., orthologs), use the UniProt batch download or the NCBI database cross reference table.
Quality Checks
Always check the evidence code for each annotation line. Swiss-Prot curator reviewed entries have higher trust. Verify that the sequence length matches experimental expectations. If your protein of interest has known isoforms, check that you have the correct one. Bioconductor packages like AnnotationHub and biomaRt allow programmatic validation by comparing against alternative database versions.
For high throughput sequencing projects, NCBI Sequence Read Archive holds raw reads that can be assembled into de novo protein sequences. However, quality scores and assembly parameters need to be evaluated before using those sequences in downstream analyses.
Common Mistakes
Relying solely on a single database without cross checking. For example, using an ancient GenPept record without checking UniProt leads to missing updated annotations. Another frequent error is ignoring isoform numbering. Many proteins have multiple isoforms that differ in critical regions. Using the wrong isoform can invalidate functional predictions.
Downloading a sequence without noting the version. If you use accession P04637 without a version number, the database may have updated the entry since you last used it. Always record the version (e.g., P04637 3). Also, treat computationally predicted sequences from large genome projects with caution. They may lack functional evidence.
Not considering evolutionary context. Homology based functional inference requires sequences with meaningful similarity (e.g., BLAST e value < 1e 5). Simply matching a name does not guarantee identical function across species.
Limits of Interpretation
Protein sequence databases are incomplete. Many proteins from rare or poorly studied organisms are absent or only predicted. Even well studied organisms like humans have gaps in functional annotation. Bioconductor documentation notes that database updates can change entries, so analyses must be repeated after new releases.
Databases also contain errors. Misannotated start sites, missed splice variants, and wrong domain boundaries are known problems. The trustworthiness of an annotation depends on the evidence level. Swiss Prot entries are manually reviewed but still may have mistakes. TrEMBL entries rely on automated pipelines, increasing error rates.
Interpretation of results must account for database bias. Datasets are skewed toward model organisms and medically relevant proteins. Negative results (no match) do not prove absence of a protein, only that no similar sequence is in the database. Similarly, a predicted domain does not guarantee in vivo function.
Frequently Asked Questions
What is the difference between UniProtKB/Swiss Prot and UniProtKB/TrEMBL?
Swiss Prot entries are manually curated by biologists who review the literature and experimental evidence. TrEMBL entries are automatically annotated and are not reviewed. For highest confidence, use Swiss Prot. For broader coverage, include TrEMBL but treat annotations with caution.
How can I find the canonical isoform of a human protein?
UniProt marks the canonical isoform as the default sequence for each entry. On the UniProt page, the "Sequence" section shows the canonical isoform first, along with a list of alternative isoforms. The canonical isoform is usually the longest or most frequently observed form based on literature.
Can I download protein sequences in bulk?
Yes. UniProt allows batch downloads of up to thousands of sequences using the "Retrieve ID mapping" tool. You can also use the REST API or the biomaRt package in Bioconductor. For NCBI, you can use the efetch utility from the Entrez Programming Utilities.
What is the best database for searching a novel protein sequence with unknown function?
Start with BLASTP against UniProt (Swiss Prot and TrEMBL). That search will identify homologous sequences with known functions. If no significant hits appear, try the NCBI non redundant database, which contains sequences from multiple sources. For structural homology, use HHPred against PDB.
References and Further Reading
- NCBI Bookshelf: Bioinformatics Resources
- EMBL-EBI Training: Protein Sequence Databases
- Galaxy Training Network: Protein Sequence Analysis
- Bioconductor: Annotation Resources
- NCBI Sequence Read Archive
- A Comprehensive Overview of Physical and Adjuvant Therapies for Recurrent Respiratory Papillomatosis - J Voice
- DEHP and Stress Urinary Incontinence - Front Cell Dev Biol
- Identification and Validation of Tolerogenic Dendritic Cells Related Biomarkers - Diabetol Int
- Differences in Axial Psoriatic Arthritis and Axial Spondyloarthritis - Front Med (Lausanne)
- Five Gene Ferroptosis Model for Pancreatic Cancer - Discov Oncol