Description
Normalize a compact ORCID check character from lowercase x to uppercase X without checking its checksum.
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.
Normalize a compact ORCID check character from lowercase x to uppercase X without checking its checksum.
When to use this tool
Use ORCID Check Character Uppercase Rule 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, changed. Inspect changed before interpreting the associated values.
Require 15 digits followed by a digit, X, or x in compact form. Uppercase the string and return canonical and whether it changed.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| canonical | Canonical spelling under this tool’s formatting rule; inspect validity flags separately. | Required. Text; maximum UTF-16 length 8192. |
| changed | Changed | Required. Boolean. |
{
"input": {
"identifier": "000000012146438x"
},
"output": {
"canonical": "000000012146438X",
"changed": true
}
}Limitations and assumptions
- Only check-character case is normalized. Hyphenated input is rejected and the checksum, registry assignment, and person's identity are not verified.
- 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.