Description
Accept 16 compact characters or exact four-character hyphen groups with 15 digits and a final digit or uppercase X.
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.
Accept 16 compact characters or exact four-character hyphen groups with 15 digits and a final digit or uppercase X.
When to use this tool
Use ORCID Checksum Canonical Grouping 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 identifier. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read canonical, valid. Inspect valid before interpreting the associated values.
Accept 16 compact characters or exact four-character hyphen groups with 15 digits and a final digit or uppercase X. Compute the MOD 11-2 check from the first 15 digits, return valid for a matching final symbol, and return canonical grouping for shaped input.1
The ORCID check character uses MOD 11-2 and can be a digit or uppercase X; registry assignment is a separate property.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| canonical | Grouped spelling for shaped input, even if checksum fails; empty for malformed shape. | Required. Text; maximum UTF-16 length 8192. |
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
{
"input": {
"identifier": "0000000218250097"
},
"output": {
"canonical": "0000-0002-1825-0097",
"valid": true
}
}Limitations and assumptions
- A shaped identifier with a wrong checksum still receives canonical grouping and valid false; malformed shape returns empty canonical. Checksum success does not prove registry assignment, ownership, or researcher identity.
- 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
- ORCID Https Prefix Host Check
Check only the canonical HTTPS ORCID URL host and identifier shape; checksum validation is separate.
- ORCID Check Character Uppercase Rule
Normalize a compact ORCID check character from lowercase x to uppercase X without checking its checksum.