eduKateSG · Why Science?
Read a microbiome analysis as a chain, not a magic answer
Explore how MGnify connects studies, samples, runs, assemblies and analyses so learners can distinguish submitted sequence data from pipeline-produced microbiome summaries.
A microbiome is a community, and community data can become complicated quickly. One study may contain many samples, sequencing runs, assemblies and analyses. MGnify provides a public hub for analysing and exploring metagenomic, metatranscriptomic, amplicon and assembly data, giving students a real example of how computational work turns sequence deposits into structured summaries.
The crucial distinction is between archived source data and MGnify analysis products. A study record organises context; run and assembly accessions connect to sequence evidence; an analysis accession identifies a particular computational result. Taxonomic or functional summaries depend on the data, pipeline and reference resources used.
Did you know? The same microbial community can look different when sampled, sequenced or analysed differently. That does not make microbiome science hopeless. It makes method labels, sample context and analysis versions part of the evidence. MGnify is useful for science education precisely because these layers are visible and linkable.
Use this article as a route-reading guide. It avoids treating a colourful abundance chart as a final biological conclusion. Instead, it asks what was sampled, which data object entered the workflow, what the analysis produced and which comparison is genuinely supported.
Chapter index
Chapters 1–9: study-to-analysis routes
- 1. A microbiome is a community-level question
- 2. Studies organise related material
- 3. MGYS identifies a study
- 4. Samples explain where sequences came from
- 5. Runs are sequence-data units
- 6. Assemblies are derived sequence objects
- 7. Analyses have their own accessions
- 8. Pipelines make choices explicit
- 9. Taxonomy is a classification result
Chapters 10–17: outputs, uncertainty and responsible comparison
- 10. Functional summaries are predictions or matches
- 11. Relative abundance needs a denominator
- 12. Zero does not always mean absent
- 13. Metadata enables meaningful comparison
- 14. The API exposes structured relationships
- 15. Publications provide biological interpretation
- 16. Responsible microbiome stories avoid hype
- 17. Microbiome data connect many careers
CHAPTER 1 OF 17 · Meet the microbiome study
1. A microbiome is a community-level question
Start with the record itself, because a good science explanation names the object before interpreting it. Microbiome research studies microorganisms associated with an environment or host. MGnify supports several sequence-data approaches, including amplicon, metagenomic, metatranscriptomic and assembly-based analysis, which answer overlapping but different questions. For secondary science learning, that distinction turns database browsing into evidence practice rather than fact collecting.
Try this
Ask: Which approach produced this record, and what kind of biological signal can that approach capture? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Make four cards for amplicon, metagenome, metatranscriptome and assembly; give each one a cautious question it could help investigate. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Do not fill a blank with a guess. Record the missing field, follow the linked accession or method, and state exactly what remains uncertain. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the a microbiome is a community-level question evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Here the useful move is to separate what the archive stores from what a researcher may later infer. MGnify study records gather context and relationships for a project or dataset. A study is the broad container, while its samples, runs, assemblies and analyses remain distinct objects with their own identifiers. It also connects classroom habits—defining variables, tracing methods and comparing like with like—to real research infrastructure.
Try this
Ask: What is the study question, and which linked objects supply the actual sequence or computed evidence? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Open a study record and draw its first two layers without counting a run, sample and analysis as equivalent units. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Keep observation and interpretation in separate sentences. That simple discipline makes the reasoning easier to audit and revise. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the studies organise related material evidence you used, keep its identifier or field label visible, and state one limit before moving on.
This part of the record rewards slow reading: labels, identifiers and relationships do different jobs. MGnify study accessions commonly begin MGYS. Keeping that accession in notes lets a learner return to the study even when the title is long or similar to another project. The same habit matters beyond school: technicians, analysts, curators and researchers all need to know which layer of a record supports a statement.
Try this
Ask: Which accession identifies the study, and is an ENA project accession also linked? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Record both MGnify and archive project identifiers when present, then describe why the pair supports cross-resource tracing. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Compare records only after checking that their organisms, samples, methods, reference versions and study questions are compatible. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the mgys identifies a study evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 4 OF 17 · Meet the microbiome study
4. Samples explain where sequences came from
A cheerful surprise in data science is that careful organisation can make a complicated investigation much easier to understand. Sample metadata can describe the organism, habitat, body site, location or experimental condition associated with sequence data. Completeness varies, so environmental context should be read from fields rather than guessed from a title. This is a practical lesson in scientific literacy because structured data can look authoritative even when an essential qualifier is missing.
Try this
Ask: Which sample attributes define the environment, and which comparison variable is missing? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Choose two samples and build a context table before looking at any taxonomic chart; stop if the intended comparison is not supported. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. A database result is a route into evidence, not a verdict. Preserve the accession, date and filters so another reader can retrace the route. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the samples explain where sequences came from evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Treat this as a small evidence puzzle. The visible fields tell you what can be checked and what still needs another source. A sequencing run accession points to raw sequence output deposited in an archive such as ENA. Multiple runs may belong to one sample, and one study may contain many samples, so run count is not automatically sample count. Reading the field in context helps a learner explain both the useful signal and the limit of the claim.
Try this
Ask: How many runs map to each sample, and are technical replicates or repeated measurements visible? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Create a run-to-sample mapping for a small subset and calculate both counts separately. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. When the interface changes, the stable identifier and source documentation matter more than the position of a button on the page. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the runs are sequence-data units evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 6 OF 17 · Trace data into analysis
6. Assemblies are derived sequence objects
Start with the record itself, because a good science explanation names the object before interpreting it. Assemblies combine sequence reads into longer sequences under a computational process. MGnify can link assembly accessions and analyses, but an assembly is not the untouched raw data and should be described as derived. For secondary science learning, that distinction turns database browsing into evidence practice rather than fact collecting.
Try this
Ask: Which run or study links to the assembly, and is the assembly method or archive record available? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Trace one assembly back toward its source runs, noting every step you can verify and leaving gaps explicit. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Do not fill a blank with a guess. Record the missing field, follow the linked accession or method, and state exactly what remains uncertain. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the assemblies are derived sequence objects evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Here the useful move is to separate what the archive stores from what a researcher may later infer. MGnify analysis records identify pipeline-produced results and commonly use MGYA accessions. A study can have multiple analyses because different inputs or pipeline versions may be processed separately. It also connects classroom habits—defining variables, tracing methods and comparing like with like—to real research infrastructure.
Try this
Ask: Which analysis accession, input object and pipeline context produced the view on screen? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Compare two analysis records within a study and list only differences visible in their metadata. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Keep observation and interpretation in separate sentences. That simple discipline makes the reasoning easier to audit and revise. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the analyses have their own accessions evidence you used, keep its identifier or field label visible, and state one limit before moving on.
This part of the record rewards slow reading: labels, identifiers and relationships do different jobs. Computational pipelines perform quality control, classification and other steps according to defined versions and reference resources. The output is reproducible only to the extent that these choices and inputs are recorded. The same habit matters beyond school: technicians, analysts, curators and researchers all need to know which layer of a record supports a statement.
Try this
Ask: Which pipeline version and analysis type are shown, and what would need to match for a fair reanalysis comparison? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Write a reproducibility recipe containing accession, analysis type, pipeline version, input and retrieval date. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Compare records only after checking that their organisms, samples, methods, reference versions and study questions are compatible. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the pipelines make choices explicit evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 9 OF 17 · Read taxonomic and functional outputs
9. Taxonomy is a classification result
A cheerful surprise in data science is that careful organisation can make a complicated investigation much easier to understand. Taxonomic summaries assign or estimate sequence evidence against reference classifications. A bar or table reports the analysis result, not a direct census of every organism living in the original environment. This is a practical lesson in scientific literacy because structured data can look authoritative even when an essential qualifier is missing.
Try this
Ask: What unit is reported, what reference framework was used, and are unclassified sequences visible? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Take one taxonomic output and rewrite “these organisms were present” as a more precise statement about classified sequence evidence. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. A database result is a route into evidence, not a verdict. Preserve the accession, date and filters so another reader can retrace the route. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the taxonomy is a classification result evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 10 OF 17 · Read taxonomic and functional outputs
10. Functional summaries are predictions or matches
Treat this as a small evidence puzzle. The visible fields tell you what can be checked and what still needs another source. Functional outputs connect sequence features with families, pathways or annotations according to computational rules and databases. They can generate useful hypotheses, but function may be predicted rather than experimentally measured in the sampled environment. Reading the field in context helps a learner explain both the useful signal and the limit of the claim.
Try this
Ask: Is the displayed function observed through a direct assay, inferred from sequence, or linked through an annotation database? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Label three functional statements as measured, computationally assigned or interpretive, then revise any sentence that mixes the categories. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. When the interface changes, the stable identifier and source documentation matter more than the position of a button on the page. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the functional summaries are predictions or matches evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 11 OF 17 · Read taxonomic and functional outputs
11. Relative abundance needs a denominator
Start with the record itself, because a good science explanation names the object before interpreting it. Microbiome charts often show proportions among classified observations. Relative abundance can change because one group changes or because the denominator changes; it does not automatically reveal absolute cell numbers. For secondary science learning, that distinction turns database browsing into evidence practice rather than fact collecting.
Try this
Ask: What forms the denominator, and were values normalised before comparison? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Create two toy communities with different total counts but the same percentage, then explain why identical proportions need not mean identical abundance. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Do not fill a blank with a guess. Record the missing field, follow the linked accession or method, and state exactly what remains uncertain. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the relative abundance needs a denominator evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 12 OF 17 · Read taxonomic and functional outputs
12. Zero does not always mean absent
Here the useful move is to separate what the archive stores from what a researcher may later infer. A taxon or function missing from an output may be truly absent, below detection, unclassified, filtered or unsupported by the chosen reference. Careful language protects the distinction. It also connects classroom habits—defining variables, tracing methods and comparing like with like—to real research infrastructure.
Try this
Ask: Which analytical and sampling limits could produce this zero? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Replace “absent” with a statement tied to the method, such as “not detected in this analysis under the reported pipeline”. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Keep observation and interpretation in separate sentences. That simple discipline makes the reasoning easier to audit and revise. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the zero does not always mean absent evidence you used, keep its identifier or field label visible, and state one limit before moving on.
This part of the record rewards slow reading: labels, identifiers and relationships do different jobs. Comparisons need compatible sample context, sequencing approach, pipeline and output units. A habitat label alone cannot guarantee that two analyses are comparable. The same habit matters beyond school: technicians, analysts, curators and researchers all need to know which layer of a record supports a statement.
Try this
Ask: Which variables match, which differ and which are unknown? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Build a comparability checklist for two analyses and decide whether comparison is descriptive, exploratory or unsupported. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Compare records only after checking that their organisms, samples, methods, reference versions and study questions are compatible. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the metadata enables meaningful comparison evidence you used, keep its identifier or field label visible, and state one limit before moving on.
A cheerful surprise in data science is that careful organisation can make a complicated investigation much easier to understand. The MGnify API presents studies, analyses, runs, assemblies, publications and related objects in structured responses. Links between endpoints can support reproducible data exploration and small coding projects. This is a practical lesson in scientific literacy because structured data can look authoritative even when an essential qualifier is missing.
Try this
Ask: Which endpoint returns the object you need, and how will pagination or filters affect the set? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Retrieve one study or analysis through the API view and identify its type, id, attributes and relationship links. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. A database result is a route into evidence, not a verdict. Preserve the accession, date and filters so another reader can retrace the route. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the the api exposes structured relationships evidence you used, keep its identifier or field label visible, and state one limit before moving on.
CHAPTER 15 OF 17 · Compare with care
15. Publications provide biological interpretation
Treat this as a small evidence puzzle. The visible fields tell you what can be checked and what still needs another source. A linked publication can explain sampling, laboratory methods, analysis choices and biological conclusions. MGnify organises data and analysis outputs, while the paper supplies a narrative that must still be evaluated against the records. Reading the field in context helps a learner explain both the useful signal and the limit of the claim.
Try this
Ask: Does the paper refer to the same accessions and analysis version visible now? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Make a two-column claim audit: publication statement on the left, supporting archive or analysis object on the right. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. When the interface changes, the stable identifier and source documentation matter more than the position of a button on the page. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the publications provide biological interpretation evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Start with the record itself, because a good science explanation names the object before interpreting it. Microbiome associations are easily turned into causal or health claims that the study design does not support. Sample size, confounding, compositionality and validation all matter. For secondary science learning, that distinction turns database browsing into evidence practice rather than fact collecting.
Try this
Ask: Is the evidence descriptive, associational, predictive or experimental, and does the wording match? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Rewrite a sensational microbiome headline into a claim that names the sample set, analysis and uncertainty. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Do not fill a blank with a guess. Record the missing field, follow the linked accession or method, and state exactly what remains uncertain. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the responsible microbiome stories avoid hype evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Here the useful move is to separate what the archive stores from what a researcher may later infer. Microbial ecology, public health, food science, environmental monitoring, bioinformatics and data curation all use microbiome evidence. Each role depends on communicating the route from sample to sequence to analysis. It also connects classroom habits—defining variables, tracing methods and comparing like with like—to real research infrastructure.
Try this
Ask: Which career would focus on sampling, laboratory work, pipeline design, statistical comparison or archive stewardship? Write the answer as a claim-evidence-reasoning note. Quote no more than the field needs; instead, paraphrase the record, name the accession or object type, and explain why that field is relevant. If two pages disagree, check their update context and follow the primary documentation before deciding that one is wrong.
Try this: Pick one role and design a handover note containing the identifiers and context the next team member would need. Then add one sentence beginning ‘This record can support…’ and another beginning ‘This record cannot by itself establish…’. Keep observation and interpretation in separate sentences. That simple discipline makes the reasoning easier to audit and revise. That two-sentence finish keeps the activity optimistic, precise and honest.
Evidence checkpoint
Name the microbiome data connect many careers evidence you used, keep its identifier or field label visible, and state one limit before moving on.
Contents · Previous chapter · Continue at the Science Learning Hub
A colourful profile becomes science when its evidence route is visible
MGnify lets learners follow a microbiome study across samples, runs, assemblies and analyses. That layered view supports a happier kind of caution: every identifier is another chance to check the story rather than a reason to distrust data.
When comparing communities, keep the sample context, sequence approach, pipeline, output unit and denominator beside the chart. The result is a clearer explanation and a much stronger foundation for further science learning.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Study accession | Organises the microbiome dataset | Which samples and analyses belong here? |
| Run or assembly | Sequence evidence or derived sequence object | Is this raw input or processed material? |
| Analysis accession | Identifies a pipeline-produced result | Which pipeline context produced it? |
| Taxonomic or functional output | Structured computational summary | What unit, denominator and reference limit apply? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A database record is a structured route into evidence; it does not by itself prove a new biological conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
Primary sources
- MGnify home and service scope — accessed 24 October 2026.
- MGnify API — accessed 24 October 2026.
- MGnify help and documentation — accessed 24 October 2026.
- MGnify studies API collection — accessed 24 October 2026.
- MGnify example assembly record — accessed 24 October 2026.
