Description
Check only the canonical HTTPS ORCID URL host and identifier shape; checksum validation is separate.
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 HTTPS ORCID URL host and identifier shape; checksum validation is separate.
When to use this tool
Use ORCID Https Prefix Host 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 url. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, identifier. Inspect valid before interpreting the associated values.
Match the exact lowercase https://orcid.org/ prefix followed by four hyphenated groups, with the final character a digit or uppercase X. Return valid and the identifier, or empty identifier when the shape fails.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| url | Url | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"url": "https://orcid.org/0000-0002-1825-0097"
},
"output": {
"valid": true,
"identifier": "0000-0002-1825-0097"
}
}Limitations and assumptions
- This verifies one canonical-looking URL spelling without checksum or registry checks. It does not establish researcher identity, ownership, record existence, or a general URL normalization policy.
- 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.
- Validation: ORCID Display Hyphen Group Check
Check only the canonical ORCID display grouping and final X position, explicitly not the MOD11-2 checksum or registry existence.