Skip to content

Main content

Historical Employment Personday Unit Tool

Preserve explicit historical employment person-day quantity and unit convention without assuming hours per day.

Loading tool…

Description

Preserve explicit historical employment person-day quantity and unit convention.

Historical economic records depend on archival wording, accounting signs, local units, assigned values, denominations and date precision. A wage-day ratio is a comparison of supplied amounts rather than actual labor time. Preserving an account-year label or unit factor does not authenticate a historical price, practice or legal obligation.

Preserve explicit historical employment person-day quantity and unit convention.

When to use this tool

Use Historical Employment Personday Unit when you already have recordId, quantityText, personDayConvention and need to preserve explicit historical employment person-day quantity and unit convention.

How to use the tool and how it works

  1. Enter recordId, quantityText, personDayConvention. 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 recordId, quantityText, personDayConvention 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
recordIdRecord IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
quantityTextQuantity TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
personDayConventionPerson Day ConventionRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordId": "R17",
    "quantityText": "12",
    "personDayConvention": "one recorded worker-day"
  },
  "output": {
    "token": "[\"R17\",\"12\",\"one recorded worker-day\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without assuming hours per day. 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 ledger, archive and historical unit or monetary definitions when reconstructing an account. Reconcile period, commodity quality, currency and source corrections before comparing values; local labels and supplied conversions preserve only their declared assumptions.

References

  1. Calculation and input contract: economic-history/historical-employment-personday-unit — tool.io

Similar or alternative tools