Description
Split a shaped container identifier into owner, equipment category, serial, and check-digit fields.
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.
Split a shaped container identifier into owner, equipment category, serial, and check-digit fields.
When to use this tool
Use ISO 6346 Owner Prefix Token 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 code. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read owner, category, serial, checkDigit. Use the output convention below.
Require three uppercase letters, a U/J/Z category character, and seven digits. Split code into owner, category, six-digit serial, and checkDigit.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| code | Code | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| owner | Owner | Required. Text; maximum UTF-16 length 8192. |
| category | Category | Required. Text; maximum UTF-16 length 8192. |
| serial | Serial | Required. Text; maximum UTF-16 length 8192. |
| checkDigit | Check Digit | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"code": "CSQU3054383"
},
"output": {
"owner": "CSQ",
"category": "U",
"serial": "305438",
"checkDigit": "3"
}
}Limitations and assumptions
- This is lexical field extraction only. Owner allocation, check-digit correctness, equipment existence, and container 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.