Skip to content

Main content

Community Defined Term Alias Count Tool

Count explicitly authorized community-defined aliases without generating or publishing restricted vocabulary.

Loading tool…

Description

Count distinct authorized alias labels for selectedTerm, and separately count its unauthorized records including duplicates.

Cultural and community records can carry access, attribution, quotation, and publication permissions. Preserving a supplied label does not create permission or override community protocols, source conditions, or an individual's stated preferences.

Count distinct authorized alias labels for selectedTerm, and separately count its unauthorized records including duplicates.

When to use this tool

Use Community Defined Term Alias Count when you need to record a supplied attribution or access statement without expanding its scope.

How to use the tool and how it works

  1. Enter termIds, aliasLabels, authorized, selectedTerm. Keep parallel arrays aligned. 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 authorizedAliases, unauthorizedRecords. Use the output convention below.

Require aligned termIds, aliasLabels, and authorized arrays. Count distinct authorized alias labels for selectedTerm, and separately count its unauthorized records including duplicates.1

Input fieldMeaning and unitsAccepted input
termIdsTerm IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
aliasLabelsAlias LabelsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
authorizedAuthorizedRequired. Array of boolean; maximum items 256.
selectedTermSelected TermRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
authorizedAliasesAuthorized AliasesRequired. Safe integer.
unauthorizedRecordsUnauthorized RecordsRequired. Safe integer.
json
{
  "input": {
    "termIds": [
      "t",
      "t",
      "t"
    ],
    "aliasLabels": [
      "a",
      "a",
      "b"
    ],
    "authorized": [
      true,
      true,
      false
    ],
    "selectedTerm": "t"
  },
  "output": {
    "authorizedAliases": 1,
    "unauthorizedRecords": 1
  }
}

Limitations and assumptions

  • Matching is literal; authorization flags, term identity, language equivalence, and permission to publish aliases are not verified.
  • 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

Confirm the original permission, community protocol, and intended use with the responsible people before sharing material.

References

  1. Calculation and input contract: indigenous-studies/community-defined-term-alias-count — tool.io

Similar or alternative tools