Description
Recognize an optional case-insensitive https://doi.org/ or https://dx.doi.org/ resolver prefix.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Recognize an optional case-insensitive https://doi.org/ or https://dx.doi.org/ resolver prefix.
When to use this tool
Use DOI URL Prefix Versus Identifier Tag when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter value. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read kind, identifier. Use the output convention below.
Recognize an optional case-insensitive https://doi.org/ or https://dx.doi.org/ resolver prefix. Strip it when present, require the remaining implemented 10. plus four-to-nine digits and nonempty non-whitespace suffix shape, and return kind and identifier.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| kind | Kind | Required. Text; maximum UTF-16 length 8192. |
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"value": "https://doi.org/10.1000/182"
},
"output": {
"kind": "resolver-url",
"identifier": "10.1000/182"
}
}Limitations and assumptions
- The suffix is preserved without URI decoding, and extra slash characters can remain. Shape does not prove DOI registration, resolvability, publisher identity, or correctness of citation metadata.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- Validation: DOI Prefix Single Field Check
Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.
- Ror URL Host Identifier Split
Split the identifier from an optional exact ROR resolver prefix under a lexical shape gate.