Description
Check only overall LEI width and uppercase alphanumeric alphabet; LOU structure and checksum are 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 overall LEI width and uppercase alphanumeric alphabet; LOU structure and checksum are separate.
When to use this tool
Use LEI Entity Prefix Length 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 token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read validLength, validAlphabet. Inspect validLength, validAlphabet before interpreting the associated values.
Return validLength for exactly 20 UTF-16 code units and validAlphabet for a nonempty string consisting only of uppercase ASCII letters and digits.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| validLength | Valid Length | Required. Boolean. |
| validAlphabet | Valid Alphabet | Required. Boolean. |
{
"input": {
"token": "5493001KJTIIGC8Y1R12"
},
"output": {
"validLength": true,
"validAlphabet": true
}
}Limitations and assumptions
- The two flags are independent: a correctly sized token can fail the alphabet check. Reserved positions, final-digit structure, checksum, registry assignment, and legal-entity 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
- Validation: DOI Prefix Single Field Check
Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.
- DOI URL Prefix Versus Identifier Tag
Recognize an optional case-insensitive https://doi.org/ or https://dx.doi.org/ resolver prefix.