Description
Record an explicit language-audio publication purpose and permission flag.
Community-supplied names, credits, permissions and source versions carry their own authority and context. A recorded access or precision label does not itself grant permission or hide a location. Preserving requested wording and attribution order is distinct from authenticating rights, community approval or adequate protection.
Record an explicit language-audio publication purpose and permission flag.
When to use this tool
Use Language Audio Publication Permission Field when you already have recordingId, publicationPurpose, permissionRecorded and need to record an explicit language-audio publication purpose and permission flag.
How to use the tool and how it works
- Enter recordingId, publicationPurpose, permissionRecorded. 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 recordingId, publicationPurpose, permissionRecorded 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. Boolean permission or verification fields are recorded assertions, not authorizations.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordingId | Recording Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| publicationPurpose | Publication Purpose | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| permissionRecorded | Permission Recorded | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordingId": "REC17",
"publicationPurpose": "public archive",
"permissionRecorded": true
},
"output": {
"token": "[\"REC17\",\"public archive\",true]"
}
}Limitations and assumptions
- The result records supplied values without establishing valid authorization. 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 community-provided permissions, attribution instructions and controlled records for actual use. Apply access and location protection to the underlying material, rather than treating a display mask or status label as the complete safeguard.
References
Similar or alternative tools
- Community Supplied Metadata Namespace Code
Qualify an explicit community-supplied metadata field code by namespace and version.
- Community Resource Explicit Access Date
Preserve explicit community-resource access-date and permission-reference metadata.