UGC Permission Coverage

Audit user-generated-content permission records.

Description

UGC permission records track whether required uses of contributed media have a corresponding recorded grant.

UGC permission records track whether required uses of contributed media have a corresponding recorded grant. Coverage is a label comparison rather than an interpretation of consent.^[1]

Audit user-generated-content permission records.

When to use UGC Permission Coverage

Use this tool to audit user-generated-content permission records.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use UGC Permission Coverage and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter requiredPermissions, documentedPermissions using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredPermissions	Required UGC permissions	list of string	Required
documentedPermissions	Documented permissions	list of string	Required

Supply required uses and granted permission labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

coverage%=100×matchedUnique/requiredUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredPermissions": [
      "alpha",
      "beta",
      "gamma"
    ],
    "documentedPermissions": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No contract, rights holder, license scope, expiration or legal sufficiency is verified.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Video Provenance Check: Compare caller-supplied expected and observed records for video provenance check. For a complementary task, use Screengrab Attribution Audit: Audit screengrab attribution coverage.

References

UGC Permission Coverage — tool.io

Similar or alternative tools

Video Provenance Check
Compare caller-supplied expected and observed records for video provenance check.
Screengrab Attribution Audit
Audit screengrab attribution coverage.