01
Where it fits—and where it doesn’t
Use these four checks before committing implementation time.
- Use it when
- Multi-omics and multi-assay study metadata at the boundary between experiment design and repository submission.
- Do not use it as
- Do not treat ISA as a complete solution on its own. Rich metadata entry is labor-intensive and local templates can drift without governance and validation.
- Best for
- Teams working with Discovery and Laboratory and Omics data across Plan → Acquire → Harmonize.
- Maturity
- EstablishedEstablished enough for serious use; still pin the exact release and any implementation profile.
02
See it in the workflow
A standard creates value by changing a handoff, not by existing in a catalog.
- InputWhat starts
Discovery and Laboratory and Omics data, metadata, and the local decisions around them
- ISAWhat changes
ISA applies a shared data model / schema across Plan → Acquire → Harmonize
- OutputWhat becomes possible
A more consistent, reviewable handoff for the next system or team
03
A concrete example
A multi-omics study records subjects, specimens, extraction protocols, LC-MS and sequencing assays, and derived files in one investigation.
Why it matters: Captures experiment and sample lineage that models need for stratification, provenance, and reproducible train/test construction.
04
What it fits with
Normatively serializes as ISA-Tab and ISA-JSON, uses ontology annotations, and complements RO-Crate packaging; RDF representations are community/tooling layers.
- Ontology ecosystemOBO Foundry
Both support Discovery and Laboratory and Omics work and meet around Plan, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileSDRF-Proteomics
Both support Omics and Laboratory work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaAllotrope
Both support Laboratory and Discovery work and meet around Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaOME-NGFF
Both support Laboratory and Discovery work and meet around Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Name an accountable owner and the decision ISA must support.
Pin the exact version and companion artifacts: ISA Model · ISA-Tab · ISA-JSON 1.0.
Map one representative input to the required data model / schema artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Limitation to test first—and the tests that catch it
Rich metadata entry is labor-intensive and local templates can drift without governance and validation.
Run one representative end-to-end pilot and record exactly where ISA loses context, needs an extension, or depends on another standard.
A structured or machine-readable result can still be unfit for analysis or AI.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Captures experiment and sample lineage that models need for stratification, provenance, and reproducible train/test construction.
07
Why we believe this
Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.
Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.
08
Source shelf
Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.
ISA tools and model
The canonical publisher or steward source used to verify this data model / schema profile.
- Publisher
- ISA Commons
- Rights
- Rights remain with the publisher; this knowledge base links to the source rather than copying it.
- Access
- Opens the publisher's source in a new tab; no external media loads on this page.
- Verified
- 2026-07-13