Fiund / Quality & provenance

Keep the source, signal, and review connected.

A useful video training data collection needs traceable context as well as usable files. Define what will be checked, how findings will be recorded, and which questions remain open.

A podcast guest and microphone filmed in a real studio session — Frame from a real studio recording · Podcast Studio AZSource & media notes ↗

Technical criteria

Category-specific acceptance starts here.

Temporal unit

Clip length, session length, continuity, and whether cuts or transitions are acceptable.

Picture and sound

Resolution, frame rate, codec, aspect ratio, track layout, and synchronization needs.

Content restrictions

Subtitles, overlays, watermarks, music, edits, synthetic material, or excluded subjects.

Labels and splits

Descriptions, temporal annotations, source grouping, and train/evaluation separation.

Review framework

Four separate questions for each collection.

Review layer	What to establish	Evidence to request
Source lineage	Where this exact file or record came from and how it relates to other versions.	Stable identifiers, source references, and derivative relationships.
Technical fit	Whether the recorded fields and signal support the defined model task.	A representative inspection, file-level metadata, and issue records.
Annotation fit	Whether labels have the required meaning, timing, and consistency.	Written conventions, reviewed examples, and known limitations.
Permission scope	Whether the proposed use has been reviewed for the selected material.	Project-specific source documentation and agreed terms.

Illustrative manifest

A manifest should describe the state of review.

Example structure only. These values do not describe an available collection or a completed permission review.

{
  "record_id": "illustrative-record-001",
  "source_reference": "to-be-established",
  "category": "Video Training Data",
  "specification_fields": [
    "Temporal unit",
    "Picture and sound",
    "Content restrictions",
    "Labels and splits"
  ],
  "permission_review": "requires_project_review",
  "technical_review": "not_yet_reviewed",
  "accepted_exceptions": []
}