Metadata profile · v1.0.0 · approved 2025-10-29

GA4GH Experiments Metadata Checklist

Maintained by GA4GH Discovery Work Stream

What it helps you do

Expmeta supports minimum experiment-level properties for high-throughput sequencing, focused on library preparation, sequencing instruments, run context, protocols, and relevant identifiers.

  • Omics
  • Discovery
  • Laboratory
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits and where it does not

Use these four checks before committing implementation time.

Use it when
Repositories, laboratories, and federated discovery systems that need comparable descriptions of WGS, RNA-seq, methylation, and other sequencing experiments.
Limits
The current scope excludes biological sample descriptors, clinical data, downstream processing, and analysis. A completed checklist is not a reproducibility record, and the checklist does not require one canonical serialization.
Best for
Omics and Discovery and Laboratory teams working across Plan → Acquire → Harmonize → Exchange → Learn + reuse.
Maturity
ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.

02

See it in the workflow

This view shows the input, the change the standard introduces, and the resulting output.

  1. InputWhat starts

    Omics and Discovery and Laboratory source data, metadata, and local mappings

  2. ExpmetaWhat changes

    Use Expmeta as a pinned metadata profile across Plan → Acquire → Harmonize → Exchange → Learn + reuse

  3. OutputWhat becomes possible

    A handoff the next system or team can validate against the same release

Readiness gateThe current scope excludes biological sample descriptors, clinical data, downstream processing, and analysis. A completed checklist is not a reproducibility record, and the checklist does not require one canonical serialization.

03

A concrete example

Map local experiment fields to the core and identifiers checklists, preserve ontology identifiers and protocols, record the checklist version, validate required local constraints, and publish mappings with the data.

Why it matters: Exposes assay, library, instrument, and protocol variables needed to assess comparability and batch effects, while sample biology, processing provenance, QC, and labels require other standards.

04

What it fits with

Complements ISA and MINSEQE study metadata, sample and clinical models, HTS file formats, and Beacon discovery filters; future categories target single-cell, targeted sequencing, and other assay-specific detail.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Define one handoff, its accountable owner, and the decision Expmeta must support.

  2. Pin the exact version and companion artifacts: v1.0.0 · approved 2025-10-29.

  3. Map one representative input to the required metadata profile artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Test the main limitation

Risk

The current scope excludes biological sample descriptors, clinical data, downstream processing, and analysis. A completed checklist is not a reproducibility record, and the checklist does not require one canonical serialization.

Test

Run one representative end-to-end pilot and record exactly where Expmeta loses context, needs an extension, or depends on another standard.

Risk

Machine-readable output may still be unfit for analysis or ML.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Exposes assay, library, instrument, and protocol variables needed to assess comparability and batch effects, while sample biology, processing provenance, QC, and labels require other standards.

07

Official resources

Specifications, diagrams, examples, and guides from the organizations that maintain them.

  • Primary sourcev1.0.0 · approved 2025-10-29

    GA4GH Expmeta v1.0.0

    Official publisher or steward guidance for this metadata profile profile.

    Publisher
    GA4GH Discovery Work Stream
    Open official source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.