Skip to content

Main content

Community Defined Date Precision Token Tool

Attach explicit community-defined precision wording and provenance to a date transcription without imposing calendar fields.

Loading tool…

Description

Require nonempty dateText, communityPrecisionLabel, and sourceId, then combine them into a source-qualified token.

Calendar coordinates depend on an era, origin, day-start rule, and sometimes an arithmetic rather than observational convention. A supplied coordinate difference does not resolve those choices.

Require nonempty dateText, communityPrecisionLabel, and sourceId, then combine them into a source-qualified token.

When to use this tool

Use Community Defined Date Precision Token when you need a documented calendar convention or source-coordinate comparison.

How to use the tool and how it works

  1. Enter dateText, communityPrecisionLabel, sourceId. 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 dateText, communityPrecisionLabel, and sourceId, then combine them into a source-qualified token.1

Input fieldMeaning and unitsAccepted input
dateTextSupplied date text under the accepted precision and grammar above.Required. Text; maximum UTF-16 length 8192.
communityPrecisionLabelCommunity Precision LabelRequired. Text; maximum UTF-16 length 8192.
sourceIdIdentifier used to retain the supplied source context.Required. Text; 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": {
    "dateText": "season A",
    "communityPrecisionLabel": "season precision",
    "sourceId": "S17"
  },
  "output": {
    "token": "season A [season precision; S17]"
  }
}

Limitations and assumptions

  • Neither date nor precision wording is interpreted; the source convention and community authority are not validated or replaced with a Gregorian assumption.
  • 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 source calendar and authoritative date information for actual observance, conversion, or historical dating.

References

  1. Calculation and input contract: indigenous-studies/community-defined-date-precision-token — tool.io

Similar or alternative tools