Skip to content

Main content

Brazilian Diary Date Separator Token

Join explicit Brazilian diary date-transcription fields without parsing ambiguous dates or converting calendars.

Loading tool…

Description

Join supplied diary day, month and year transcriptions with a separator.

Archival records use source-specific expediente, foja, tomo, series and imprint-role wording. A recorded copy status or date transcription differs from authentication or calendar interpretation. Preserve original spellings, numbering and permission context before matching records or publishing a passage.

Join supplied diary day, month and year transcriptions with a separator.

When to use this tool

Use Brazilian Diary Date Separator Token when you already have suppliedDayText, suppliedMonthText, suppliedYearText, separator and need to join supplied diary day, month and year transcriptions with a separator.

How to use the tool and how it works

  1. Enter suppliedDayText, suppliedMonthText, suppliedYearText, separator. 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 dateLabel. Use the output convention below.

Require all four strings nonempty; concatenate day, month and year in that order using separator.1

Input fieldMeaning and unitsAccepted input
suppliedDayTextUnparsed date component text; no calendar validity is checked.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedMonthTextSupplied Month TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedYearTextSupplied Year TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
separatorSeparatorRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
dateLabelDate LabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "suppliedDayText": "03",
    "suppliedMonthText": "04",
    "suppliedYearText": "1950",
    "separator": "/"
  },
  "output": {
    "dateLabel": "03/04/1950"
  }
}

Limitations and assumptions

  • No digits, calendar, real date, chronology or locale-specific notation are validated.
  • 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 archive, edition or interview and its local descriptive conventions. Apply appropriate documentary or calendar analysis for substantive interpretation; display redaction and locator keys do not establish provenance or publication rights.

References

  1. Calculation and input contract: latin-american-studies/brazilian-diary-date-separator-token — tool.io

Similar or alternative tools