Description
Encode an explicitly annotated object-use context.
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.
Encode an explicitly annotated object-use context.
When to use this tool
Use Material Object Use Context Tag when you already have objectCode, useCode, contextCode and need to encode an explicitly annotated object-use context.
How to use the tool and how it works
- Enter objectCode, useCode, contextCode. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read tag. Use the output convention below.
Enter objectCode, useCode, contextCode using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in tag. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| objectCode | Object Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| useCode | Use Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| contextCode | Context Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| tag | Tag | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"objectCode": "O17",
"useCode": "U3",
"contextCode": "C2"
},
"output": {
"tag": "[\"O17\",\"U3\",\"C2\"]"
}
}Limitations and assumptions
- The result records supplied values without inferring a cultural practice from an object. 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
- Public Artifact Caption Source Credit
Preserve an explicit public artifact caption and supplied source credit.
- Household Residence Pattern Source Code
Preserve a caller-coded residence-pattern record with its source codebook.