Description
Link explicit archive interview, return-copy and receipt identifiers.
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.
Link explicit archive interview, return-copy and receipt identifiers.
When to use this tool
Use Archive Interview Return Copy Receipt when you already have interviewId, copyId, receiptReference and need to link explicit archive interview, return-copy and receipt identifiers.
How to use the tool and how it works
- Enter interviewId, copyId, receiptReference. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter interviewId, copyId, receiptReference 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 field | Meaning and units | Accepted input |
|---|---|---|
| interviewId | Interview Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| copyId | Copy Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| receiptReference | Receipt Reference | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"interviewId": "I17",
"copyId": "C4",
"receiptReference": "R2"
},
"output": {
"token": "[\"I17\",\"C4\",\"R2\"]"
}
} Limitations and assumptions
- The result records supplied values without establishing delivery or consent. 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 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
Similar or alternative tools
- Ethnographic Source Consent Scope Token
Preserve explicit ethnographic source consent-scope metadata.
- Field Note Language Switch Span Label
Preserve an explicit field-note language-switch span and supplied language tag.