← Photo Datasets

Fiund / Resource guide

Version photo datasets without confusing downstream users

Track additions, removals, corrections, and split changes across image dataset releases.

A real two-person podcast interview on the blue-chair studio set
Frame from a real studio recording · Podcast Studio AZSource & media notes ↗

Define the release boundary

A release should identify a particular set of image files, annotations, metadata, and split assignments. Updating one component can change the meaning of the collection even when filenames remain the same. Decide what constitutes a new release and preserve the previous manifest. This gives downstream users a stable reference for experiments, reviews, and subsequent sourcing discussions.

Describe changes by type

Separate new images, removed images, corrected labels, revised taxonomies, and technical re-exports. A resized copy is not the same change as a new photographed subject. Include stable identifiers and reasons where appropriate. Keep a machine-readable change list alongside a concise human explanation so teams can reconcile differences without manually comparing every file in two deliveries.

Protect evaluation continuity

Review whether additions are related to held-out source groups and whether corrections alter evaluation targets. If split assignments change, describe that directly. Results from two releases may no longer be comparable under the original interpretation. Preserve source relationships and duplicate findings so an expanding collection does not gradually undermine the independence assumptions established for its first release.

Plan practical withdrawals and corrections

Establish a project contact and a procedure for communicating required changes to delivered material. The technical manifest should make affected assets identifiable without exposing unnecessary supporting records. Discuss project-specific usage documentation and responsibilities separately. Fiund sourcing can include these delivery expectations in the brief, but no blanket promise about future inventory or every possible permitted use should replace a concrete agreement.

Review checklist

  • Version files, labels, metadata, and splits together.
  • Distinguish additions from re-exports and corrections.
  • Explain changes affecting evaluation comparability.
  • Keep affected assets identifiable for later updates.

Your project, in focus

Describe the images your model needs to see.

Speak directly with Jaeden Schafer at Fiund about the source material, specifications, and review your project needs.

Source fit, permissions, samples, pricing, and delivery are reviewed for the individual project.

Start with these details

  1. Subjects and class taxonomy
  2. Counts and required visual diversity
  3. Image formats and minimum dimensions
  4. Annotation type and review rules
  5. Permitted uses and exclusions
Build your project brief ↗

Original studio and recording photography. See the media notes for source context.