Description
Record an explicit authority identifier check-digit transcription and algorithm source.
Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.
Record an explicit authority identifier check-digit transcription and algorithm source.
When to use this tool
Use Authority Identifier Check Digit Source Row when you already have identifierText, suppliedCheckDigit, algorithmSource and need to record an explicit authority identifier check-digit transcription and algorithm source.
How to use the tool and how it works
- Enter identifierText, suppliedCheckDigit, algorithmSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter identifierText, suppliedCheckDigit, algorithmSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifierText | Identifier Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedCheckDigit | Supplied Check Digit | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| algorithmSource | Algorithm Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"identifierText": "00124",
"suppliedCheckDigit": "7",
"algorithmSource": "registry rule R4"
},
"output": {
"token": "[\"00124\",\"7\",\"registry rule R4\"]"
}
}Limitations and assumptions
- The result records supplied values without inventing or applying a registry algorithm. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.
References
Similar or alternative tools
- Information Source Edition Tag
Qualify explicit source-edition wording.
- Metadata Controlled Value Source Key
Qualify a literal controlled metadata value by its supplied vocabulary source.