BRENDA is a collection of enzyme functional data available to the scientific community. Data on enzyme function are extracted directly from the primary literature The database covers information on classification and nomenclature, reaction and specificity, functional parameters, occurrence, enzyme structure and stability, mutants and enzyme engineering, preparation and isolation, the application of enzymes, and ligand-related data.
This resource is a provider. This means that
while it may have its own prefix, it actually reuses the identifiers provided by the
ec
prefix. For all use cases, you should use ec
instead of brenda.
- Prefix
brenda- Keywords
- enzyme sbml
- License
- http://www.brenda-enzymes.org
- Links
- Homepage
- Publications
- 2017 The BRENDA enzyme information system-From a database to an expert system
- 2014 BRENDA in 2015: exciting developments in its 25th year of existence
- 2012 BRENDA in 2013: integrated reactions, kinetic data, enzyme function data, improved disease classification: new options and contents in BRENDA
- 2010 BRENDA, the enzyme information system in 2011
- 2008 BRENDA, AMENDA and FRENDA the enzyme information system: new content and tools in 2009
- 2007 BRENDA, AMENDA and FRENDA: the enzyme information system in 2007
- 2004 BRENDA, the enzyme database: updates and major new developments
- 2003 Review of the BRENDA Database
- 2002 BRENDA: a resource for enzyme data and metabolic information
- 2002 BRENDA, enzyme data and metabolic information
Identifier Standards
- Pattern for Local Unique Identifiers
-
Local identifiers in BRENDA Enzyme should match this regular expression:
^((\d+\.-\.-\.-)|(\d+\.\d+\.-\.-)|(\d+\.\d+\.\d+\.-)|(\d+\.\d+\.\d+\.\d+))$ - Example Local Unique Identifier
- 1.1.1.1 Resolve
- Pattern for CURIES
-
Compact URIs (CURIEs) constructed from BRENDA Enzyme should match this regular expression:
^brenda:((\d+\.-\.-\.-)|(\d+\.\d+\.-\.-)|(\d+\.\d+\.\d+\.-)|(\d+\.\d+\.\d+\.\d+))$ - Example CURIE
- brenda:1.1.1.1
Contacts
- Contact
-
Dietmar Schomburg
0000-0002-3354-822X
Ontology
A summary of the relations in the Bioregistry schema can be found here.
- Provides
- EC
- In Collection (2)
- Global Biodata Coalition - Global Core Biodata Resources Synapse.org external links
Mappings to External Registries
Mappings from records in Bioregistry to external registries comprises the metaregistry. This resource has 7 mappings to external registries with 3 unique external prefixes.
| Registry Name | Registry Metaprefix | External Prefix | Curate |
|---|---|---|---|
| BioContext | biocontext |
BRENDA
|
|
GO
|
go |
BRENDA
|
|
Identifiers.org
|
miriam |
brenda
|
|
N2T
|
n2t |
brenda
|
|
Pathguide
|
pathguide |
51
|
|
Prefix Commons
|
prefixcommons |
brenda
|
|
re3data
|
re3data |
r3d100010616
|
Providers
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 1.1.1.1 is used to demonstrate the providers
available for BRENDA Enzyme. Some providers may use a different example, which is displayed in the table below.
A guide for curating additional providers can be found
here.
| Provider Name | Provider Code | URI |
|---|---|---|
| BRENDA Enzyme | brenda |
https://www.brenda-enzymes.org/php/result_flat.php4?ecno=1.1.1.1 |
| Bioregistry | bioregistry |
https://bioregistry.io/brenda:1.1.1.1 |
| Identifiers.org | miriam |
https://identifiers.org/brenda:1.1.1.1 |
| Name-to-Thing | n2t |
https://n2t.net/brenda:1.1.1.1 |
Extra Providers
Additional providers curated in the Bioregistry are listed here. These are typically inherited from Identifiers.org or Prefix Commons, and need extra curation.
| Provider Name | Provider Code | URL |
|---|---|---|
| Bio2RDF | bio2rdf |
http://bio2rdf.org/brenda:1.1.1.1 |