Video Provenance Check

Compare caller-supplied expected and observed records for video provenance check.

Description

Video provenance records document where a clip came from and what evidence supports its history.

Video provenance records document where a clip came from and what evidence supports its history. Comparing labels helps identify gaps in a supplied verification checklist.^[1]

Compare caller-supplied expected and observed records for video provenance check.

When to use Video Provenance Check

Use this tool to compare caller-supplied expected and observed records for video provenance check.

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 Video Provenance Check 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 requiredSteps, completedSteps 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
requiredSteps	Required provenance steps	list of string	Required
completedSteps	Completed provenance steps	list of string	Required

Supply required and observed evidence 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": {
    "requiredSteps": [
      "original file",
      "uploader contact",
      "timestamp check",
      "location check"
    ],
    "completedSteps": [
      "original file",
      "timestamp check",
      "location check"
    ]
  },
  "output": {
    "coveragePercent": 75,
    "matched": [
      "original file",
      "timestamp check",
      "location check"
    ],
    "missing": [
      "uploader contact"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No video, metadata, source identity or chain of custody is inspected; matching labels does not authenticate footage.

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 Photo Metadata Coverage: Compare caller-supplied requirements and observations for photo metadata coverage. For a complementary task, use C2PA Provenance Audit: Audit required C2PA provenance assertions.

References

Video Provenance Check — tool.io

Similar or alternative tools

Photo Metadata Coverage
Compare caller-supplied requirements and observations for photo metadata coverage.
C2PA Provenance Audit
Audit required C2PA provenance assertions.