Skip to content

Main content

Oral History Remembered Versus Documented Date

Pair explicitly remembered and documented date wording without treating memory as a verified date.

Loading tool…

Description

Pair explicitly remembered and documented date wording.

Historical records separate source readings, remembered dates, documentary dates, place identifiers and editorial conventions. Supplied certainty or witness labels are annotations rather than authenticated evidence. Original spellings, calendar styles and accession-year conventions need their documentary context before chronological interpretation.

Pair explicitly remembered and documented date wording.

When to use this tool

Use Oral History Remembered Versus Documented Date when you already have interviewId, rememberedDateText, documentedDateText and need to pair explicitly remembered and documented date wording.

How to use the tool and how it works

  1. Enter interviewId, rememberedDateText, documentedDateText. 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 interviewId, rememberedDateText, documentedDateText 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
interviewIdInterview IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
rememberedDateTextRemembered Date TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
documentedDateTextDocumented Date TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "interviewId": "INT17",
    "rememberedDateText": "around 1950",
    "documentedDateText": "1951-02"
  },
  "output": {
    "token": "[\"INT17\",\"around 1950\",\"1951-02\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without treating memory as a verified date. 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

Consult the original source, edition and provenance for a historical claim. Apply an appropriate calendar or documentary analysis when actual conversion, identity or interpretation is needed; a transcription key or uncertainty marker does not establish those results.

References

  1. Calculation and input contract: history/oral-history-remembered-versus-documented-date — tool.io

Similar or alternative tools