Identifiers match
A recording ID should point to the same example in the file name, manifest and any annotation records.
Dataset delivery
A useful handoff connects each recording to its task, relevant capture information and agreed labels. Define the package with the people who will use it.
THE PACKAGE / A SHARED STRUCTURE
The file structure should make a recording understandable without a separate conversation for every clip. Stable identifiers connect footage, labels and review notes.
Agree the format during the pilot. Your existing ingestion tools, annotation schema and evaluation workflow should guide the handoff. A folder of video files and a robot-action dataset contain different information; the specification should say exactly what is included.
DOWNLOAD / ILLUSTRATIVE PACKAGE
The example contains a readme, fictional manifest and sample annotation JSON. It contains no footage, client records or personal data. Actual formats are agreed for each collection.
Download example packageillustrative-delivery-package/ ├── README.txt ├── manifest.csv └── annotations.json # Example only # No video files are included # Not a published Labeno dataset
BEFORE HANDOFF
Completeness is more than a file count. Review the package against the approved brief and schema.
A recording ID should point to the same example in the file name, manifest and any annotation records.
Names, units, time conventions and missing-value rules should be understandable to the receiving team.
Capture channels, label depth, exclusions and review criteria should be described alongside the delivery.
Tell us what you want recorded. We can discuss the skill, environment, camera setup, annotation and budget in a scoping meeting.