Description
Invert a supplied publication-permission flag and preserve a restriction code.
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.
Invert a supplied publication-permission flag and preserve a restriction code.
When to use this tool
Use Community Term Restricted Publication Flag when you already have termId, permissionToPublish, suppliedRestrictionCode and need to invert a supplied publication-permission flag and preserve a restriction code.
How to use the tool and how it works
- Enter termId, permissionToPublish, suppliedRestrictionCode. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read publicationRestricted, restrictionRecord. Inspect publicationRestricted before interpreting the associated values.
Require termId/restrictionCode nonempty; publicationRestricted=!permissionToPublish, restrictionRecord=JSON.stringify([termId,restrictionCode]).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| termId | Term Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| permissionToPublish | Permission To Publish | Required. Boolean. |
| suppliedRestrictionCode | Supplied Restriction Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| publicationRestricted | Logical inverse of the supplied permissionToPublish flag; not an authorization decision. | Required. Boolean. |
| restrictionRecord | Restriction Record | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"termId": "T17",
"permissionToPublish": false,
"suppliedRestrictionCode": "community request"
},
"output": {
"publicationRestricted": true,
"restrictionRecord": "[\"T17\",\"community request\"]"
}
}Limitations and assumptions
- The restriction code is required even when permission is true. No consent, community authority, rights, actual policy or access control is established.
- 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
- Field Note Public Private Access Tag
Label a field note's supplied access category.
- Corpus Rights Statement Label
Label a corpus with supplied rights wording and source reference.