The MEROPS database is an information resource for peptidases (also termed proteases, proteinases and proteolytic enzymes) and the proteins that inhibit them. This collections references inhibitors.

Prefix

merops.entry

Alternative Prefixes

merops.inhibitor

Keywords

biomedical science enzyme life science protein structure

Links

Homepage

Contact

Neil D Rawlings   0000-0001-5557-7665

Pattern for Local Unique Identifiers

Local identifiers in MEROPS Entry should match this regular expression:
^[SCTAGMNUIX]{1,2}\d{2}\.([AB]\d{2}|\d{3})$

Example Local Unique Identifiers

I31.952   Resolve
S01.001   Resolve
XM02.001   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from MEROPS Entry should match this regular expression:
^merops\.entry:[SCTAGMNUIX]{1,2}\d{2}\.([AB]\d{2}|\d{3})$

Example CURIEs

merops.entry:I31.952
merops.entry:S01.001
merops.entry:XM02.001

Publications

• 1999 MEROPS: the peptidase database
• 1993 Evolutionary families of peptidases
• 2018 The MEROPS database of proteolytic enzymes, their substrates and inhibitors in 2017 and a comparison with peptidases in the PANTHER database
• 2015 Twenty years of the MEROPS database of proteolytic enzymes, their substrates and inhibitors
• 2015 Peptidase specificity from the substrate cleavage collection in the MEROPS database and a tool to measure cleavage site conservation
• 2011 MEROPS: the database of proteolytic enzymes, their substrates and inhibitors
• 2007 MEROPS: the peptidase database

References

GitHub Issue https://github.com/biopragmatics/bioregistry/issues/439

The metaregistry provides mappings between the Semantic Farm 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 I31.952 is used to demonstrate the providers available for MEROPS Entry. Some providers may use a different example, which is displayed in the table below. A guide for curating additional providers can be found here.

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