Description
Qualify an explicit community-supplied metadata field code by namespace and version.
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.
Qualify an explicit community-supplied metadata field code by namespace and version.
When to use this tool
Use Community Supplied Metadata Namespace Code when you already have communityNamespace, suppliedFieldCode, sourceVersion and need to qualify an explicit community-supplied metadata field code by namespace and version.
How to use the tool and how it works
- Enter communityNamespace, suppliedFieldCode, sourceVersion. 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 communityNamespace, suppliedFieldCode, sourceVersion 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 |
|---|---|---|
| communityNamespace | Community Namespace | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedFieldCode | Supplied Field Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceVersion | Source Version | 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": {
"communityNamespace": "COMM17",
"suppliedFieldCode": "FIELD2",
"sourceVersion": "v2"
},
"output": {
"token": "[\"COMM17\",\"FIELD2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without imposing a vocabulary. 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 Resource Explicit Access Date
Preserve explicit community-resource access-date and permission-reference metadata.
- Community Preferred Name Period Label
Preserve an explicitly supplied community preferred-name and period label.