01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- A submission and publication completeness gate for functional-genomics studies, especially when preparing repository records and supporting data.
- Limits
- These are minimum-information checklists rather than one executable schema. Stewardship is legacy, and newer assay classes such as single-cell data require current repository guidance and additional profiles.
- Best for
- Omics teams working across Plan → Acquire → Harmonize → Exchange.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Omics source data, metadata, and local mappings
- MIAME · MINSEQEWhat changes
Use MIAME · MINSEQE as a pinned metadata profile across Plan → Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
Before release, a transcriptomics study checks that design, biological variables, sample-data relationships, raw reads, processed matrices, and laboratory and computational protocols are present.
Why it matters: Raises the metadata floor for reuse, but does not standardize expression matrices, ontology depth, QC, batch correction, labels, or cohort representativeness.
04
What it fits with
MAGE-TAB is a MIAME-supportive serialization; ISA can represent richer study structure. Current repository guidance applies MIAME to microarrays and MINSEQE to high-throughput sequencing.
- Metadata profileSDRF-Proteomics
Both support Omics work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Omics work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileMIxS
Both support Omics work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaAIRR · MiAIRR
Both support Omics work and meet around Plan, Acquire, Harmonize, Exchange. 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.
Define one handoff, its accountable owner, and the decision MIAME · MINSEQE must support.
Pin the exact version and companion artifacts: MIAME 2001 guidance · MINSEQE 1.0 (June 2012).
Map one representative input to the required metadata profile artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
These are minimum-information checklists rather than one executable schema. Stewardship is legacy, and newer assay classes such as single-cell data require current repository guidance and additional profiles.
Run one representative end-to-end pilot and record exactly where MIAME · MINSEQE loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Raises the metadata floor for reuse, but does not standardize expression matrices, ontology depth, QC, batch correction, labels, or cohort representativeness.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
FGED legacy standards registry
Official publisher or steward guidance for this metadata profile profile.
- Publisher
- FGED Society legacy standards · operational repository implementers