Skip to content

Main content

Authorized Item Access Scope Tool

Inspect caller-supplied access-purpose/permission metadata without granting access or disclosing restricted content.

Loading tool…

Description

Check requestedPurpose against allowedPurposes.

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.

Check requestedPurpose against allowedPurposes.

When to use this tool

Use Authorized Item Access Scope 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 requestedPurpose, allowedPurposes, permissionKnown, permissionGranted, source. 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 listed, permittedUnderFlags, unresolved, source. Inspect listed, permittedUnderFlags, unresolved before interpreting the associated values.

Check requestedPurpose against allowedPurposes. Set permittedUnderFlags only for a listed purpose with known and granted permission; set unresolved when permissionKnown is false and return source unchanged.1

Input fieldMeaning and unitsAccepted input
requestedPurposeRequested PurposeRequired. Text; maximum UTF-16 length 8192.
allowedPurposesAllowed PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
permissionKnownPermission KnownRequired. Boolean.
permissionGrantedPermission GrantedRequired. Boolean.
sourceCaller-supplied source label; not independently verified.Required. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
listedListedRequired. Boolean.
permittedUnderFlagsPermitted Under FlagsRequired. Boolean.
unresolvedUnresolvedRequired. Boolean.
sourceCaller-supplied source label; not independently verified.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "requestedPurpose": "study",
    "allowedPurposes": [
      "study"
    ],
    "permissionKnown": true,
    "permissionGranted": true,
    "source": "policy-A"
  },
  "output": {
    "listed": true,
    "permittedUnderFlags": true,
    "unresolved": false,
    "source": "policy-A"
  }
}

Limitations and assumptions

  • A listed purpose alone is not permission; source identity, consent validity, access controls, and community protocols 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/authorized-item-access-scope — tool.io

Similar or alternative tools