Description
Split the identifier from an optional exact ROR resolver prefix under a lexical shape gate.
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 the identifier from an optional exact ROR resolver prefix under a lexical shape gate.
When to use this tool
Use Ror URL Host Identifier Split 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 value. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read identifier, urlForm. Inspect urlForm before interpreting the associated values.
Require the implemented nine-character lowercase ROR identifier shape, optionally preceded by the exact https://ror.org/ prefix. Return the extracted identifier and urlForm indicating the prefix's presence.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| urlForm | Url Form | Required. Boolean. |
{
"input": {
"value": "https://ror.org/03yrm5c26"
},
"output": {
"identifier": "03yrm5c26",
"urlForm": true
}
}Limitations and assumptions
- This checks shape and host spelling only. It does not verify the checksum, resolve the registry record, establish an organization's existence, or accept extra path, query, or fragment text.
- 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: Ror Base32 Identifier Alphabet Check
Check the nine-character ROR local-id lexical form: leading zero, six restricted base32 characters and two decimal checksum digits; checksum and registry are not evaluated.
- ORCID Checksum Canonical Grouping
Accept 16 compact characters or exact four-character hyphen groups with 15 digits and a final digit or uppercase X.