Skip to content

Main content

Interview Pseudonym Collision Pair

Flag two distinct supplied interview identifiers sharing the exact same nonempty pseudonym without identifying speakers.

Loading tool…

Description

Flag one pseudonym shared by distinct supplied interview IDs.

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.

Flag one pseudonym shared by distinct supplied interview IDs.

When to use this tool

Use Interview Pseudonym Collision Pair when you already have firstInterviewId, firstPseudonym, secondInterviewId, secondPseudonym and need to flag one pseudonym shared by distinct supplied interview IDs.

How to use the tool and how it works

  1. Enter firstInterviewId, firstPseudonym, secondInterviewId, secondPseudonym. 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 collision. Inspect collision before interpreting the associated values.

Require all four identifiers nonempty; collision=firstInterviewId!=secondInterviewId && firstPseudonym===secondPseudonym.1

Input fieldMeaning and unitsAccepted input
firstInterviewIdFirst Interview IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
firstPseudonymFirst PseudonymRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
secondInterviewIdSecond Interview IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
secondPseudonymSecond PseudonymRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
collisionDistinct interview IDs and identical pseudonyms; no participant identity or anonymity is established.Required. Boolean.
json
{
  "input": {
    "firstInterviewId": "I17",
    "firstPseudonym": "Speaker A",
    "secondInterviewId": "I18",
    "secondPseudonym": "Speaker A"
  },
  "output": {
    "collision": true
  }
}

Limitations and assumptions

  • Identical interview IDs never flag collision. Exact-string equality does not establish participant identity, anonymity or appropriate pseudonym assignment.
  • 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/interview-pseudonym-collision-pair — tool.io

Similar or alternative tools