Get startedData · Portability
Import and export annotations
Move labels and multimodal training evidence between Score and external systems.
Source reviewed 2026-09-16. Availability depends on your installation, permissions, and compatible runtimes. A supported path is not a guarantee of model quality or production readiness.
Outcome
Preserve visual annotations and their associated VLM text in a version-scoped transfer.
Start here
What you need to know first
Check the inputs below before starting. If you are new, begin with the first-project guide. A dataset holds media and labels; a model produces results; a deployment makes a selected model version callable. Creating one does not create the others.
Bring these inputs
- — A version-scoped annotation package
- — File identity and class/schema mappings
Expected output and limits
- — Imported evidence or a portable export archive
- — Validation and rejection report
Core workflow
Choose a version
Open the exact dataset version whose schema and evidence should move.
Select a format
Choose a compatible specialist or multimodal representation and inspect schema mapping.
Validate the preview
Review matched files, classes, regions, prompts, answers, captions, and rejected records.
Run the transfer
Track the durable task and retain the generated report or export artifact.
What this surface supports
Detection and segmentation formats
VLM prompts, answers, and captions
Linked text spans and regions
Transfer summaries
Expert section
Contracts, signals, and failure modes
Use this section when you are defining acceptance criteria, automating the surface, or reviewing whether its output is safe to promote downstream.
Quality and operating signals
- — Matched asset ratio
- — Accepted annotation count
- — Unknown classes and malformed records
Common failure modes
- — Filename mismatch
- — Coordinate-system mismatch
- — Dropping VLM text or region links during conversion
Expert release checklist
□ Inputs and dependencies are pinned to immutable versions.
□ Acceptance metrics include critical classes and operating slices.
□ Failure, retry, cost, and rollback behavior are understood.
□ The resulting artifact has an owner and a downstream review path.
Engineering safeguards
- — Transfers are version-scoped
- — Schema conflicts surface before acceptance
- — Annotation export is not a full-media backup