Resource guide
Reviewing camera motion in egocentric recordings
Assess motion against action visibility rather than polished appearance.
Fiund / Quality & provenance
A useful data egocentric collection needs traceable context as well as usable files. Define what will be checked, how findings will be recorded, and which questions remain open.
Technical criteria
Head-mounted, chest-mounted, or another participant-centered view; describe acceptable camera movement.
Action list, sequence length, successful and unsuccessful attempts, and variation between participants.
Resolution, frame rate, field of view, audio policy, and any requirements for time alignment.
Action boundaries, object references, task descriptions, and the level of detail needed for evaluation.
Review framework
| 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
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": "Data Egocentric",
"specification_fields": [
"Viewpoint",
"Task coverage",
"Capture details",
"Annotation"
],
"permission_review": "requires_project_review",
"technical_review": "not_yet_reviewed",
"accepted_exceptions": []
}Further reading
Resource guide
Assess motion against action visibility rather than polished appearance.
Resource guide
Describe transitions and local visibility within the working scene.
Resource guide
Focus variation on observable behavior and deployment requirements.
Your project, in focus
Speak directly with Jaeden Schafer at Fiund about the source material, specifications, and review your project needs.
jaeden@fiund.comSource fit, permissions, samples, pricing, and delivery are reviewed for the individual project.
Start with these details