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
- Enter requestedPurpose, allowedPurposes, permissionKnown, permissionGranted, source. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- 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 field | Meaning and units | Accepted input |
|---|---|---|
| requestedPurpose | Requested Purpose | Required. Text; maximum UTF-16 length 8192. |
| allowedPurposes | Allowed Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| permissionKnown | Permission Known | Required. Boolean. |
| permissionGranted | Permission Granted | Required. Boolean. |
| source | Caller-supplied source label; not independently verified. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| listed | Listed | Required. Boolean. |
| permittedUnderFlags | Permitted Under Flags | Required. Boolean. |
| unresolved | Unresolved | Required. Boolean. |
| source | Caller-supplied source label; not independently verified. | Required. Text; maximum UTF-16 length 8192. |
{
"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
Similar or alternative tools
- Consented Name Search Key Flag
Set includeInSearch only when consented and not withdrawn, returning suppliedKey when included and an empty string otherwise.
- Gynecologic Study Contact Consent Match
Compare them with supplied permitted lists, test expiry under inclusive, and set eligible only when active and all comparisons pass.