eduKateSG · Why Science?
Request the slice of processed RNA data you actually need—and keep its study, units, coordinates and integrity attached
Choose the closest route, then return to the full index whenever you need the wider evidence chain.
Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. RNAget is a GA4GH API for discovering and retrieving processed RNA-sequencing data through common endpoints. GA4GH lists RNAget as current and v1.2 as the last approved version. The product page describes retrieval by expression, genomic coordinates, project and study, while the API supports expression matrices and continuous matrices, metadata, direct byte responses and download tickets. RNAget can reduce transfer by selecting projects, studies, samples, features or coordinate ranges, but it does not create the processed values, harmonise every biological annotation, grant access or prove that measurements from different studies are comparable. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.
Related eduKate reading: htsget and secure genomic streaming; GA4GH Data Repository Service and portable access; refget and globally identifiable reference sequences; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: Official GA4GH RNAget product page, current RNAget v1.2; Official RNAget v1.2 API documentation; Official RNAget schema repository; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Standards, service interfaces and recommendations can change, so preserve the dated documentation and versions used.
A deeper reading route
RNAget begins after many scientific choices have already happened. Reads were generated, aligned or quantified; features were defined; values may have been normalised or transformed; samples were grouped into studies. A common retrieval API makes those products easier to discover and subset, but it must never make the processing history invisible. A matrix without units, annotation, reference and study design is a neat rectangle with uncertain scientific meaning.
Expression and continuous data answer different spatial questions. An expression matrix usually places features against samples, while a continuous matrix describes signal along genomic coordinates. Selecting genes from a table is not the same operation as cutting a chromosome interval from a track. RNAget exposes both styles, so a responsible client must keep row, column and coordinate semantics explicit instead of treating every response as a generic file.
Selective retrieval is powerful because RNA studies can be large. A researcher may need a small group of samples, a short feature list or one genomic interval rather than an entire archive. Smaller transfer saves time and storage, yet it also creates a new analytical object. The exact sample order, feature identifiers, thresholds, coordinate convention and version must travel with that object so another person can reconstruct what was omitted as well as what was returned.
Tickets separate the first API response from the later byte transfer. A ticket can carry a URL, required headers, format, units and checksum, allowing storage delivery to be handled efficiently. That convenience introduces a security lesson: headers or signed URLs can be capabilities, and logs can leak them. Clients should protect those values, observe expiry and verify the downloaded bytes before analysis.
For students, RNAget is a bright example of how biology, matrices and computing meet. The same habits used in a small science table still matter: name the measurement, preserve units, know which rows and columns were selected, and state what comparison is fair. The scale changes dramatically; the logic of careful evidence does not. A useful classroom extension is to give groups the same fictional matrix but different selection instructions, then compare their summaries. Different answers can all be arithmetically correct because the selected samples or features differ. The lesson is wonderfully practical: before debating a result, first make sure everyone is looking at the same slice, the same units and the same version of the data.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Discover | Which project, study and data product exist? | Metadata and stable identifiers | A candidate processed RNA dataset |
| Filter | Which samples, features or coordinates are needed? | Lists, thresholds, chromosome and half-open ranges | A bounded matrix slice |
| Retrieve | Should bytes arrive directly or through a ticket? | Format, URL, headers, units and checksum | A transferable data object |
| Interpret | What does the returned value mean scientifically? | Processing method, units, reference, annotations and design | A qualified evidence table |
Inside this guide
1–12 · Foundations and design
- 1. Start with processed data
- 2. Understand the current product
- 3. Distinguish RNAget from raw-read retrieval
- 4. Use project and study context
- 5. Read metadata before bytes
- 6. Treat identifiers as scoped
- 7. Discover expression products
- 8. Request a specific expression object
- 9. Filter by project and study
- 10. Filter samples explicitly
- 11. Filter features explicitly
- 12. Use value thresholds cautiously
13–24 · Models and estimation
- 13. Choose a supported format
- 14. Read units as scientific metadata
- 15. Use tickets for deferred download
- 16. Use direct bytes deliberately
- 17. Protect ticket headers
- 18. Verify MD5 with context
- 19. Understand continuous matrices
- 20. Use chromosome, start and end precisely
- 21. Request selected samples in tracks
- 22. Keep reference assemblies visible
- 23. Handle unsupported operations honestly
- 24. Handle missing objects honestly
25–36 · Diagnostics and interpretation
- 25. Connect RNAget to htsget
- 26. Connect RNAget to DRS
- 27. Compare studies cautiously
- 28. Connect to Primary Science
- 29. Connect to Secondary Science
- 30. Connect to mathematics
- 31. Connect to computing
- 32. Connect to pathways
- 33. Did you know?
- 34. Write a reader-ready retrieval report
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with processed data
RNAget serves processed RNA data such as expression or continuous matrices. Those values already reflect alignment, quantification, normalisation or summarisation choices upstream.
Working checkpoint — RNAget: Write the intended biological comparison and required processing provenance. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 2 of 36
2. Understand the current product
GA4GH lists RNAget as current and v1.2 as the last approved version, with a common API for RNA data retrieval.
Working checkpoint — expression matrix: Record RNAget v1.2, implementation version and access date. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 3 of 36
3. Distinguish RNAget from raw-read retrieval
htsget serves reads and variants, while RNAget focuses on processed RNA products. The scientific questions and validation checks differ.
Working checkpoint — continuous matrix: Choose the interface that matches the evidence layer. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 4 of 36
4. Use project and study context
Projects can organise broad programmes, while studies describe bounded investigations. Identifiers prevent titles from becoming the only join key.
Working checkpoint — study identifier: Preserve projectID and studyID with every returned object. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 5 of 36
5. Read metadata before bytes
Metadata can reveal available formats, samples, features, units, versions and study context. Downloading first invites avoidable mismatches.
Working checkpoint — download ticket: Confirm the requested slice is interpretable before transfer. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 6 of 36
6. Treat identifiers as scoped
Sample, feature, expression and continuous-matrix IDs can be meaningful only within a service or study unless a global scheme is declared.
Working checkpoint — coordinate range: Store service endpoint and namespace with each ID. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 7 of 36
7. Discover expression products
Expression matrices organise values across biological features and samples. The matrix may use genes, transcripts or another defined feature set.
Working checkpoint — RNAget: Read feature definitions and annotation release before comparison. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 8 of 36
8. Request a specific expression object
RNAget can retrieve metadata, a ticket or bytes for one expression identifier. These routes represent the same logical product at different access layers.
Working checkpoint — expression matrix: Verify identifier, version, study and checksum across routes. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 9 of 36
9. Filter by project and study
Expression requests can narrow results using projectID and studyID. A project-wide query and a study-specific query need not have the same denominator.
Working checkpoint — continuous matrix: Write the inclusion scope beside every summary. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 10 of 36
10. Filter samples explicitly
sampleIDList can request selected sample columns. Selection changes the matrix and can change downstream normalisation or interpretation.
Working checkpoint — study identifier: Preserve the ordered sample list and selection reason. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 11 of 36
11. Filter features explicitly
featureIDList and featureNameList can select rows, but names can be duplicated or version-sensitive. Identifiers are usually safer when their namespace is known.
Working checkpoint — download ticket: Resolve names to identifiers and report unmatched items. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 12 of 36
12. Use value thresholds cautiously
Minimum and maximum feature-value filters can reduce a matrix, yet selection on observed values changes what remains and can bias summaries.
Working checkpoint — coordinate range: Treat thresholds as part of the analysis design, not a neutral download option. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 13 of 36
13. Choose a supported format
The request names a data format, and the server can return 406 or 501 when formatting or an operation is unsupported.
Working checkpoint — RNAget: Negotiate supported formats and test the parser on a small object. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 14 of 36
14. Read units as scientific metadata
A returned ticket can carry units. Counts, TPM, FPKM, normalised values and transformed scores are not interchangeable.
Working checkpoint — expression matrix: Reject analysis when units are missing or ambiguous. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 15 of 36
15. Use tickets for deferred download
A ticket can return a URL, headers, file type, study ID, version, units and MD5 checksum instead of embedding all bytes in the first response.
Working checkpoint — continuous matrix: Protect headers and verify the checksum after retrieval. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 16 of 36
16. Use direct bytes deliberately
A bytes endpoint can stream a matrix directly, which is convenient for clients but still needs format, authentication and integrity handling.
Working checkpoint — study identifier: Record response headers, size and digest. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 17 of 36
17. Protect ticket headers
Download-ticket headers may include credentials or signed capabilities. Publishing them can grant unintended access.
Working checkpoint — download ticket: Keep secrets out of notebooks, screenshots and logs. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 18 of 36
18. Verify MD5 with context
An MD5 value can detect accidental transfer corruption for the described object. It is not a modern proof of authorship or a replacement for secure transport.
Working checkpoint — coordinate range: Recompute the advertised checksum and preserve algorithm name. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 19 of 36
19. Understand continuous matrices
Continuous RNA data represent values along genomic coordinates, such as signal tracks, rather than feature-by-sample expression tables.
Working checkpoint — RNAget: Name the biological quantity and reference coordinate system. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 20 of 36
20. Use chromosome, start and end precisely
RNAget documents continuous ranges with chromosome plus zero-based, inclusive start and zero-based, exclusive end. One coordinate convention error shifts every interval.
Working checkpoint — expression matrix: Convert conventions once and test boundary examples. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 21 of 36
21. Request selected samples in tracks
A continuous request can filter by sample list as well as project, study, version and range.
Working checkpoint — continuous matrix: Check that all samples use compatible processing and reference. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 22 of 36
22. Keep reference assemblies visible
A chromosome label such as chr10 is not enough without a genome assembly and sequence identity.
Working checkpoint — study identifier: Attach assembly and, where possible, refget identifiers. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 23 of 36
23. Handle unsupported operations honestly
A 501 response means the server does not implement the requested operation; it does not mean the biological data do not exist.
Working checkpoint — download ticket: Fall back only to a documented supported route. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 24 of 36
24. Handle missing objects honestly
A 404 for one identifier is service-specific and can reflect version changes, retention or a wrong namespace.
Working checkpoint — coordinate range: Check metadata and study version before searching elsewhere. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 25 of 36
25. Connect RNAget to htsget
RNAget can provide processed matrices while htsget can retrieve underlying read or variant slices. Comparing layers can reveal where processing choices enter.
Working checkpoint — RNAget: Keep raw and processed object identifiers linked. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 26 of 36
26. Connect RNAget to DRS
A large exported RNA matrix may also be represented as a DRS object, separating logical object identity from the RNA-specific query API.
Working checkpoint — expression matrix: Verify that both routes resolve to the intended bytes and metadata. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 27 of 36
27. Compare studies cautiously
Common response structures improve interoperability, but batch, tissue, library preparation, sequencing depth and normalisation can still differ.
Working checkpoint — continuous matrix: Harmonise design and processing before statistical comparison. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 28 of 36
28. Connect to Primary Science
A table of plant heights can be filtered by class or measurement day, illustrating that a smaller view comes from a larger dataset.
Working checkpoint — study identifier: Use invented non-health data and keep the original table. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 29 of 36
29. Connect to Secondary Science
Gene expression links cells, regulation and environment while reinforcing fair comparison, replication and measurement units.
Working checkpoint — download ticket: Compare small fictional matrices with clearly defined units. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 30 of 36
30. Connect to mathematics
Matrices, thresholds, intervals, subsets and transformations connect RNA data retrieval to algebra and statistics.
Working checkpoint — coordinate range: Mark rows, columns and interval endpoints before calculating. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 31 of 36
31. Connect to computing
REST endpoints, query parameters, pagination, tickets, formats, checksums and authentication show how APIs carry scientific meaning.
Working checkpoint — RNAget: Test invalid IDs, unsupported formats and boundary coordinates. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Section 32 of 36
32. Connect to pathways
RNA data services connect molecular biology, bioinformatics, data engineering and research infrastructure and can illuminate STEM pathways.
Working checkpoint — expression matrix: Check current official study and professional requirements separately. Read every matrix value beside processing provenance, annotation, study design and measurement units.
For future study, connect RNA biology to matrices, APIs and data engineering while checking official pathways separately.
Section 33 of 36
33. Did you know?
RNAget can request continuous genomic data with a zero-based inclusive start and zero-based exclusive end—the same half-open interval idea used widely in computing.
Working checkpoint — continuous matrix: Test a one-base range to confirm the client convention. Preserve unmatched IDs, unsupported requests and excluded rows or columns; a returned subset is not the complete study.
For scientific writing, name RNAget, study, version, units and selection parameters.
Section 34 of 36
34. Write a reader-ready retrieval report
Name the RNAget and implementation versions, endpoint, project, study, samples, features or coordinates, format, units, ticket or byte route, size and checksum.
Working checkpoint — study identifier: Keep access headers private and interpretation boundaries visible. Separate API interoperability and successful retrieval from biological comparability and statistical validity.
For students, ask which rows, columns and coordinate ranges were selected from the larger dataset.
Section 35 of 36
35. Build a validation ladder
Inspect metadata, validate identifiers and units, request a tiny slice, verify format and checksum, test coordinates and missing cases, then retrieve the full governed subset.
Working checkpoint — download ticket: Resolve meaning before scaling transfer. Treat samples, features, reference sequences and units as scientific identities: a silent mismatch can reverse interpretation.
For parents, ask whether data access is authorised and whether studies are truly comparable.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver queries, identifiers, metadata responses, ordered samples and features, coordinate conventions, files, checksums, processing provenance, permissions and analysis links.
Working checkpoint — coordinate range: Make every matrix value traceable to study context and retrieval parameters. Keep the RNAget endpoint, project and study IDs, samples, features or coordinates, units, format, files and checksums together.
For a classroom model, use fictional plant measurements instead of personal or genomic records.
Contents · Previous section · Continue to the Science Learning Hub