Skip to content

Main content

Kinship Diagram Deceased Marker Label Tool

Append an explicitly supplied deceased marker to a kinship label only when its recorded flag is true.

Loading tool…

Description

Append a supplied deceased marker under a recorded status flag.

Anthropological records preserve source language, translation status, community terms, household reference dates, kinship labels and permission context. A reciprocal-term display is not a verified kinship rule, while a pseudonym collision differs from identity verification. Display masks and public-access labels do not establish adequate protection or valid consent.

Append a supplied deceased marker under a recorded status flag.

When to use this tool

Use Kinship Diagram Deceased Marker Label when you already have personLabel, recordedDeceased, suppliedMarker and need to append a supplied deceased marker under a recorded status flag.

How to use the tool and how it works

  1. Enter personLabel, recordedDeceased, suppliedMarker. 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 diagramLabel. Use the output convention below.

Require personLabel and suppliedMarker nonempty; append the marker only when recordedDeceased=true.1

Input fieldMeaning and unitsAccepted input
personLabelPerson LabelRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
recordedDeceasedRecorded DeceasedRequired. Boolean.
suppliedMarkerRequired nonempty text even when recordedDeceased=false and the marker is not appended.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
diagramLabelDiagram LabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "personLabel": "Person A",
    "recordedDeceased": true,
    "suppliedMarker": "†"
  },
  "output": {
    "diagramLabel": "Person A†"
  }
}

Limitations and assumptions

  • The marker is required even when unused. No person, vital status, kinship, chronology or culturally appropriate notation is verified.
  • 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 field records, community-provided terms, translation sources and permission instructions for actual interpretation or reuse. Apply protection to underlying records and evaluate the full research context; local keys and status labels do not perform those tasks.

References

  1. Calculation and input contract: cultural-anthropology/kinship-diagram-deceased-marker-label — tool.io

Similar or alternative tools