Skip to content

Main content

Historical Event Date Precision Token Tool

Attach an explicit historical date-precision annotation without interpreting a calendar or inferring missing fields.

Loading tool…

Description

Quote date text and append its declared precision.

Archival records often contain bounded dates, editions, and source identifiers. Arithmetic on supplied coordinates can check consistency while leaving historical interpretation and authenticity unresolved.

Quote date text and append its declared precision.

When to use this tool

Use Historical Event Date Precision Token when you need a precise date-span or source-record bookkeeping step.

How to use the tool and how it works

  1. Enter eventId, dateText, precision. 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.

Require nonempty eventId and dateText and a listed precision token. Quote date text and append its declared precision.1

Input fieldMeaning and unitsAccepted input
eventIdEvent IdRequired. Text; maximum UTF-16 length 8192.
dateTextSupplied date text under the accepted precision and grammar above.Required. Text; maximum UTF-16 length 8192.
precisionRecorded precision category; not a measurement-uncertainty estimate.Required. Text; one of "exact-day", "month", "year", "circa", "range", "unknown"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenToken in the supported spelling; inspect the accepted grammar above.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "eventId": "E7",
    "dateText": "1750",
    "precision": "circa"
  },
  "output": {
    "token": "E7; date=\"1750\"; precision=circa"
  }
}

Limitations and assumptions

  • This records uncertainty metadata without parsing the date, estimating an interval, normalizing a calendar, or verifying an event.
  • 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

Consult the original catalog and documented calendar or dating convention when historical interpretation matters.

References

  1. Calculation and input contract: history/historical-event-date-precision-token — tool.io

Similar or alternative tools