Skip to content

Main content

Ottoman Archive Envelope Item Token

Build an unambiguous explicit archive envelope-item reference without accessing records.

Loading tool…

Description

Build an unambiguous explicit archive envelope-item reference.

Historical sources may use edition-specific locators, parallel date systems, name variants and uncertain readings. A supplied presence flag differs from an observed document feature, and display order does not convert calendars. Preserve the original transcription, convention and authority before comparing records or drawing historical conclusions.

Build an unambiguous explicit archive envelope-item reference.

When to use this tool

Use Ottoman Archive Envelope Item Token when you already have archiveId, envelopeText, itemText and need to build an unambiguous explicit archive envelope-item reference.

How to use the tool and how it works

  1. Enter archiveId, envelopeText, itemText. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Enter archiveId, envelopeText, itemText 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 fieldMeaning and unitsAccepted input
archiveIdArchive IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
envelopeTextEnvelope TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
itemTextItem TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "archiveId": "AR17",
    "envelopeText": "ENV2",
    "itemText": "ITEM3"
  },
  "output": {
    "token": "[\"AR17\",\"ENV2\",\"ITEM3\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without accessing records. 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

Inspect the original document or edition and its cataloguing conventions for identity and interpretation. Use an appropriate calendar or paleographic method when actual conversion or reading is required; supplied locators and uncertainty markers organize rather than establish that evidence.

References

  1. Calculation and input contract: middle-eastern-studies/ottoman-archive-envelope-item-token — tool.io

Similar or alternative tools