Description
Format a compact ISNI/ORCID-shaped identifier with four-character groups under a supplied separator style.
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.
Format a compact ISNI/ORCID-shaped identifier with four-character groups under a supplied separator style.
When to use this tool
Use ISNI ORCID Hyphenation Style 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, style. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read formatted. Use the output convention below.
Require a compact 16-character identifier with 15 digits and final digit or uppercase X. Divide into four-character groups and join with spaces, hyphens, or no separator according to style.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| style | Style | Required. Text; one of "spaces", "hyphens", "compact"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| formatted | Formatted | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"identifier": "0000000218250097",
"style": "hyphens"
},
"output": {
"formatted": "0000-0002-1825-0097"
}
}Limitations and assumptions
- The transformation preserves leading zeros and check-character text. It does not distinguish an ISNI from an ORCID, validate the checksum, verify assignment, or determine an identifier's required display 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
- ISBN Hyphenation Supplied Boundaries
Apply caller-supplied ISBN separator positions; assignment ranges and checksum are not inferred.
- ISNI Check Character Position
Split a compact ISNI-shaped identifier into its 15-character body and final check character.