Skip to main content
CUSTOMBUYER-SCOPED

Buyer-Scoped Custom Collection

Some projects already have a clear data contract, internal schema or model objective that does not fit a standard collection format. Buyer-Scoped Custom Collection starts from that requirement rather than asking the buyer to adapt it to a predefined template.

The useful unit of observation, source media, inputs, targets, metadata and annotations can be defined around the existing workflow. Depending on the project, the delivery can also incorporate temporal structure, multimodal relationships, provenance fields or other technical elements needed to make the data usable inside the buyer's pipeline.

Technical structure

  • Buyer-defined unit of observation and record schema
  • Project-specific inputs, targets, metadata and annotations
  • Modality relationships or temporal structure where required
  • Delivery structure aligned to the agreed data contract

Typical applications

Existing internal schemas, combined-modality projects, evaluation-specific datasets, extensions to buyer-provided material and unusual record structures.

Delivery note

Nothing beyond the agreed specification is implied by this collection. The format is defined from the buyer requirement outward.

Delivery

The exact package depends on the collection scope. Where relevant, delivery can include task-specific records, manifests, provenance fields, stable identifiers, SHA-256 hashes, MLCommons Croissant 1.0 metadata and loading instructions.

Related datasets

Explore all collections