The G protein-coupled receptor database (GPCRDB) collects, large amounts of heterogeneous data on GPCRs. It contains experimental data on sequences, ligand-binding constants, mutations and oligomers, and derived data such as multiple sequence alignments and homology models.

Prefix

gpcrdb

Keywords

life science molecular biology protein small molecule

Links

Homepage

Contact

David Gloriam   0000-0002-4299-7561

Pattern for Local Unique Identifiers

Local identifiers in G protein-coupled receptor database should match this regular expression:
^\w+$

Example Local Unique Identifier

RL3R1_HUMAN   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from G protein-coupled receptor database should match this regular expression:
^gpcrdb:\w+$

Example CURIE

gpcrdb:RL3R1_HUMAN

Publications

• 1998 GPCRDB: an information system for G protein-coupled receptors
• 2021 GPCRdb in 2021: integrating GPCR sequence, structure and function
• 2018 GPCRdb in 2018: adding GPCR structure models and ligands
• 2016 GPCRdb: the G protein-coupled receptor database - an introduction
• 2015 GPCRdb: an information system for G protein-coupled receptors
• 2013 GPCRDB: an information system for G protein-coupled receptors
• 2010 GPCRDB: information system for G protein-coupled receptors
• 2003 GPCRDB information system for G protein-coupled receptors
• 2001 Collecting and harvesting biological data: the GPCRDB and NucleaRDB information systems

The metaregistry provides mappings between the Bioregistry and other registries. There are 7 mappings to external registries for this resource with 4 unique external prefixes.

A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).

The local unique identifier RL3R1_HUMAN is used to demonstrate the providers available for G protein-coupled receptor database. A guide for curating additional providers can be found here.

Additional providers curated in the Bioregistry are listed here. These are typically inherited from Identifiers.org or Prefix Commons, and need extra curation.