Description
Check only the canonical ORCID display grouping and final X position, explicitly not the MOD11-2 checksum or registry existence.
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.
Check only the canonical ORCID display grouping and final X position, explicitly not the MOD11-2 checksum or registry existence.
When to use this tool
Use Validation: ORCID Display Hyphen Group Check 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 result. Expand result to inspect the returned fields.
Check identifier for the four hyphenated ORCID display groups with uppercase X permitted only as the final character. Return groupedShape and checksumChecked false inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"identifier": "0000-0002-1825-0097"
},
"output": {
"result": {
"groupedShape": true,
"checksumChecked": false
}
}
} Limitations and assumptions
- This is display shape only, not checksum validity, registry assignment, or authentication. Compact identifiers and lowercase x are not normalized by this tool.
- Outputs are nested inside result. 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 Checksum Canonical Grouping
Accept 16 compact characters or exact four-character hyphen groups with 15 digits and a final digit or uppercase X.
- ORCID Https Prefix Host Check
Check only the canonical HTTPS ORCID URL host and identifier shape; checksum validation is separate.