Skip to content

Main content

Historical Gazetteer As Of Key

Encode explicit gazetteer authority, place ID and as-of date fields without resolving historical place membership.

Loading tool…

Description

Qualify a historical place identifier by authority and a supplied as-of date.

Digital editions separate source readings, editorial uncertainty, witness locators, image requests, identifiers and rights statements. XML character/attribute rules differ from display labels, while URI fragments and TEI pointers need their target-document context. An identifier key or formatted token does not authenticate a witness, validate an edition or authorize reuse.

Qualify a historical place identifier by authority and a supplied as-of date.

When to use this tool

Use Historical Gazetteer As Of Key when you already have authorityCode, placeId, asOfDate and need to qualify a historical place identifier by authority and a supplied as-of date.

How to use the tool and how it works

  1. Enter authorityCode, placeId, asOfDate. 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 key. Use the output convention below.

Require authorityCode/placeId nonempty and a real UTC YYYY-MM-DD date; encode [authorityCode,placeId,asOfDate] as JSON-array text.1

Input fieldMeaning and unitsAccepted input
authorityCodeAuthority CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
placeIdPlace IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
asOfDateAs Of DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
keyKeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "authorityCode": "G-A",
    "placeId": "P17",
    "asOfDate": "1920-01-01"
  },
  "output": {
    "key": "[\"G-A\",\"P17\",\"1920-01-01\"]"
  }
}

Limitations and assumptions

  • No historical gazetteer lookup, boundary reconstruction, authority match or validity of a place at that date is established.
  • 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

Validate the complete XML/TEI document or IIIF request when technical conformance matters, and inspect the original witness and rights record for editorial use. Preserve uncertain readings, source order and attribution rather than treating local tokens as verified scholarly interpretations.

References

  1. Calculation and input contract: digital-humanities/historical-gazetteer-as-of-key — tool.io

Similar or alternative tools