Skip to content

Main content

Instrument Name Community Source Key

Qualify caller-provided instrument wording by a named source without assigning a community-preferred name.

Loading tool…

Description

Pair an instrument name with its stated community source.

Musical field records distinguish performer/community attribution, transcription and naming sources, cyclic beat coordinates and recorded permission. A public-access label is different from a reuse license, and a numerical timing residual is different from performance interpretation. Cultural context and actual consent remain tied to original sources.

Pair an instrument name with its stated community source.

When to use this tool

Use Instrument Name Community Source Key when checking the stated public-record, timing, attribution or permission convention.

How to use the tool and how it works

  1. Enter instrumentWording, communitySource, sourceVersion. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Require nonempty instrument wording, community source and source version. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
instrumentWordingInstrument WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
communitySourceCommunity SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceVersionSource VersionRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "instrumentWording": "Instrument A",
    "communitySource": "Public glossary A",
    "sourceVersion": "v2"
  },
  "output": {
    "token": "[\"Instrument A\",\"Public glossary A\",\"v2\"]"
  }
}

Limitations and assumptions

  • Community attribution is supplied rather than authenticated; no universal instrument classification, naming authority or reuse permission is inferred.
  • 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

Use original recordings and community/source conventions, with appropriate verified consent and rights review for actual interpretation, reproduction or sharing.

References

  1. Calculation and input contract: ethnomusicology/instrument-name-community-source-key — tool.io

Similar or alternative tools