Skip to content

Main content

Gender Term Source Date Range

Qualify supplied gender-term wording by source and explicit date range without asserting current terminology or identity.

Loading tool…

Description

Attach an ordered source-date interval to a gender-related term.

Gender-related research records preserve self-described wording, source context, grammatical forms and observation bases. Identity and preferences cannot be inferred from a label or grammatical slot. A pay-per-hour figure or care-time union is a local summary, not a legal or causal assessment of inequality.

Attach an ordered source-date interval to a gender-related term.

When to use this tool

Use Gender Term Source Date Range when checking the stated self-described record, source, pay or care-time convention.

How to use the tool and how it works

  1. Enter termText, sourceId, validFromDate, validToDate. 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, intervalDays. Use the output convention below.

Require nonempty term/source labels and real YYYY-MM-DD dates with end>=start. Return [term,source,start,end] as JSON text and end-start in UTC calendar days.1

Input fieldMeaning and unitsAccepted input
termTextTerm TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceIdLiteral source identifier, not a retrieved or verified document.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
validFromDateValid From DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
validToDateValid To DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
intervalDaysUTC end-minus-start calendar days; no inclusive endpoint count or universal term-validity claim.Required. Safe integer.
json
{
  "input": {
    "termText": "Term A",
    "sourceId": "SRC2",
    "validFromDate": "2026-10-28",
    "validToDate": "2026-11-01"
  },
  "output": {
    "token": "[\"Term A\",\"SRC2\",\"2026-10-28\",\"2026-11-01\"]",
    "intervalDays": 4
  }
}

Limitations and assumptions

  • The dates describe a supplied source interval, not universal validity of a term; endpoint inclusion and present-day wording preference are not inferred.
  • 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

Preserve participants’ own wording and verified source definitions; use suitable complete social/statistical analysis and appropriate permission/legal review for actual interpretation or disclosure.

References

  1. Calculation and input contract: gender-studies/gender-term-source-date-range — tool.io

Similar or alternative tools