Description
Split token at its first slash.
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 token at its first slash.
When to use this tool
Use DOI Suffix Nonempty Boundary 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 prefixValid, suffixPresent, suffix. Inspect prefixValid, suffixPresent before interpreting the associated values.
Split token at its first slash. Return prefixValid for the implemented 10. plus four-to-nine digit prefix and suffixPresent for any nonempty remainder, along with suffix.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| prefixValid | Prefix Valid | Required. Boolean. |
| suffixPresent | Suffix Present | Required. Boolean. |
| suffix | Suffix | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "10.1000/xyz"
},
"output": {
"prefixValid": true,
"suffixPresent": true,
"suffix": "xyz"
}
}Limitations and assumptions
- The flags are independent and suffix content is not validated or trimmed. Whitespace-only suffixes can count as present; no DOI registration, resolution, or complete syntax check is performed.
- 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
- BCP 47 Extlang Subtag Boundary
Split a language-tag-shaped string into language, up to three extlang-shaped parts, and a remainder.
- Validation: DOI Prefix Single Field Check
Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.