Description
Encode an exact public case-number and year transcription with a supplied court namespace.
Justice records separate consent status, case identifiers, interpreter appointments, document versions and event clocks. A supplied time-string match does not establish a scheduling conflict, and a precision label does not anonymize a record. Local reimbursement and hearing-date arithmetic do not determine legal eligibility, compliance or appropriate action.
Encode an exact public case-number and year transcription with a supplied court namespace.
When to use this tool
Use Public Case Number Year Token when you already have courtCode, caseNumberText, yearText and need to encode an exact public case-number and year transcription with a supplied court namespace.
How to use the tool and how it works
- Enter courtCode, caseNumberText, yearText. 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 courtCode, caseNumberText, yearText 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 |
|---|---|---|
| courtCode | Court Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| caseNumberText | Case Number Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| yearText | Year Text | 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": {
"courtCode": "C17",
"caseNumberText": "00124",
"yearText": "2026"
},
"output": {
"token": "[\"C17\",\"00124\",\"2026\"]"
}
}Limitations and assumptions
- The record preserves supplied identifiers, wording and provenance; it does not authenticate the source, resolve an identifier, retrieve evidence or verify the asserted relationship.
- 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
Check authoritative case, service, consent and scheduling records with the applicable rules for an actual justice matter. Verify timestamps, permissions and interpretation context; local labels and signed intervals do not establish legal effect, identity or a valid proceeding.
References
Similar or alternative tools
- Restorative Session Attendance Consent Token
Preserve explicitly supplied restorative-session attendance consent metadata.
- Justice Referral Document Version Pair
Record explicit justice-referral document and version identifiers.