eduKateSG · Why Science?
Give genomic features useful detail pages—while preserving coordinate rules, stable identifiers, safe descriptions, field counts and evidence provenance
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. UCSC describes BED detail as an extension of BED that uses the first four to twelve standard BED columns plus two added fields for richer track detail pages. The first added field is an ID that can be used in place of the name field for external links. The second is a description that may be long and may contain HTML such as tables and lists. BED detail custom-track records must be tab-separated, declare type=bedDetail and keep identifying fields specific enough to retrieve the correct details. Rich display is useful, but it does not strengthen the underlying evidence. 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: BED and genomic feature coordinates; bigBed indexed genome annotation tracks; genePred gene prediction tables; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: UCSC Genome Browser FAQ: BED detail format, checked 12 October 2026; UCSC Genome Browser Custom Tracks, checked 12 October 2026; UCSC Genome Browser bigBed Track Format, checked 12 October 2026; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Specifications, tools and recommendations can change, so preserve dated documentation, exact source data, coordinate rules and software versions.
A deeper reading route
BED detail extends a familiar positional record with two presentation-oriented fields. The standard BED prefix tells the browser where and how to draw the item. The added ID supports stable linking, and the description supplies explanatory content on the detail page. These layers should remain distinct so descriptive prose cannot silently redefine the coordinates.
The prefix may contain four through twelve standard BED columns. Optional BED fields remain positional: higher-numbered fields require the preceding fields. Every record in a track should use a consistent declared shape. A file that mixes BED4-plus-two and BED12-plus-two rows invites column shifts that can turn an ID into a block count or description.
The first added field is an item ID. UCSC notes that it can be substituted for name when creating links from detail pages. The ID should therefore be stable, unique within the track and documented with its namespace. A readable label is not automatically a persistent key, and reusing an ID across releases can make old links land on new biology.
The second added field is a long description that may contain HTML, tables and lists. This makes detail pages expressive, but it also creates responsibilities for sanitisation, accessibility and source attribution. Only trusted markup should be admitted; scripts, event handlers and deceptive links do not belong in a scientific annotation description.
UCSC requires tabs for BED detail custom tracks because the description may contain spaces. The track line must declare type=bedDetail, and the name and position should uniquely describe records so the correct ID and description appear. Delimiter, declared field count and identity are therefore functional parts of the track, not stylistic preferences.
The ordinary BED fields retain their exact meanings. Starts are zero-based, ends are open, strand and score remain optional under BED rules, and block arrays require consistent geometry. BED detail adds reader context; it does not create a new coordinate system. Reuse a tested BED validator before validating the two extra fields.
External URLs can interpolate the item ID under track configuration. This is convenient for connecting a browser feature to a source database. It also means URL templates, encoding and redirect destinations need testing. An identifier containing reserved characters can break a link or produce an unintended request if it is not handled safely.
Rich descriptions should name evidence, release and limitations in reader-visible prose. If a feature is predicted, provisional or derived from a particular assay, say so. A polished detail table can feel authoritative even when its source is uncertain. Design should make provenance easier to inspect rather than making uncertainty disappear.
Large BED-detail collections can be converted to bigBed with a suitable autoSql schema, as UCSC’s bigBed guidance demonstrates. That changes storage and access while retaining defined fields. The text source, schema and conversion command should be archived so an indexed detail track can be audited back to its exact descriptions.
Validation should check coordinate geometry, declared field count, unique IDs, non-empty descriptions, permitted markup, accessible link text and successful URL expansion. Include duplicate names at different positions, special characters, long descriptions and missing optional BED values. A browser click test is necessary but not sufficient for whole-file integrity.
For students, BED detail resembles a museum label attached to a map pin. The pin locates the object; the catalogue number identifies it; the label explains it. A beautiful label cannot move the pin or prove the object’s history. That simple separation is a cheerful lesson in evidence-aware communication.
A reproducible package contains the BED-detail text, field declaration, track line, ID namespace, description-markup policy, external-link template, source citations, optional autoSql conversion inputs, hashes and validation report. It makes every visible detail page traceable to one positional record and one evidence note.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Locate | Where is the feature? | Four to twelve standard BED fields | A validated genomic interval and display model |
| Identify | Which stable record owns the page? | Added item ID and namespace | A durable link target |
| Explain | What should the reader know? | Long description with safe, accessible markup | A source-attributed detail page |
| Verify | Do position, ID and page agree? | Field count, uniqueness, links and browser tests | A reproducible rich annotation |
Inside this guide
1–12 · Foundations and design
- 1. Start with the detail-page need
- 2. Keep the BED prefix intact
- 3. Choose a consistent prefix length
- 4. Read chromosome and bounds
- 5. Read the name field
- 6. Read optional display fields
- 7. Read the added ID
- 8. Use IDs in external links carefully
- 9. Read the added description
- 10. Allow only trusted HTML
- 11. Use tabs as required
- 12. Declare bedDetail in the track line
13–24 · Models and estimation
- 13. Make records retrievable
- 14. Keep coordinate semantics unchanged
- 15. Keep identifiers release-aware
- 16. Write concise opening detail text
- 17. Add visible source attribution
- 18. Explain prediction status
- 19. Make tables accessible
- 20. Make links understandable
- 21. Validate unique IDs
- 22. Validate markup length and safety
- 23. Validate URL expansion
- 24. Test the browser detail page
25–36 · Diagnostics and interpretation
- 25. Convert large tracks deliberately
- 26. Protect sensitive annotations
- 27. Separate explanation from evidence
- 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 detail note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with the detail-page need
BED detail is useful when a positional track needs richer per-item information than a short name.
Working checkpoint — BED detail: Name audience, source and intended detail content. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 2 of 36
2. Keep the BED prefix intact
The first four through twelve fields remain ordinary BED with binding optional-field order.
Working checkpoint — genomic feature: Validate them before the extensions. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 3 of 36
3. Choose a consistent prefix length
All records should use one declared count of standard BED fields.
Working checkpoint — item ID: Reject mixed shapes and shifted columns. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 4 of 36
4. Read chromosome and bounds
The feature begins with BED chromosome and zero-based half-open interval.
Working checkpoint — rich description: Check against the exact assembly. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 5 of 36
5. Read the name field
Standard BED name remains a visible label under the chosen prefix.
Working checkpoint — custom track: Keep label and stable ID distinct. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 6 of 36
6. Read optional display fields
Score, strand, thick bounds, colour and blocks retain BED meanings when included.
Working checkpoint — detail page: Do not let descriptions override them. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 7 of 36
7. Read the added ID
The first field after the BED prefix is the detail identifier.
Working checkpoint — BED detail: Require a documented namespace and uniqueness. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 8 of 36
8. Use IDs in external links carefully
Track configuration can substitute the ID into a URL.
Working checkpoint — genomic feature: Encode values and test destinations. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 9 of 36
9. Read the added description
The final field supplies long content for the item detail page.
Working checkpoint — item ID: Require source-aware reader-visible prose. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 10 of 36
10. Allow only trusted HTML
Descriptions may contain tables and lists, but rich markup needs sanitisation.
Working checkpoint — rich description: Disallow scripts, handlers and deceptive links. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 11 of 36
11. Use tabs as required
BED detail records must be tab-separated so spaces inside descriptions remain unambiguous.
Working checkpoint — custom track: Reject space-only parsing. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 12 of 36
12. Declare bedDetail in the track line
The custom-track header must identify the specialised type and field count.
Working checkpoint — detail page: Keep configuration beside the data. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 13 of 36
13. Make records retrievable
UCSC recommends name and position combinations that retrieve the correct ID and description.
Working checkpoint — BED detail: Test duplicate labels and nearby intervals. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 14 of 36
14. Keep coordinate semantics unchanged
The extension adds page content, not a new coordinate convention.
Working checkpoint — genomic feature: Reuse BED boundary fixtures. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 15 of 36
15. Keep identifiers release-aware
An ID can change meaning across database releases if namespaces are not versioned.
Working checkpoint — item ID: Publish release and mapping history. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 16 of 36
16. Write concise opening detail text
Lead with what the feature is, how it was produced and its status.
Working checkpoint — rich description: Place limitations before decorative context. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 17 of 36
17. Add visible source attribution
Readers should be able to follow claims to an official database, paper or project.
Working checkpoint — custom track: Include dates and stable links. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 18 of 36
18. Explain prediction status
Predicted and experimentally supported features should not look identical in prose.
Working checkpoint — detail page: Label evidence class explicitly. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 19 of 36
19. Make tables accessible
Description tables need headings, simple structure and meaningful surrounding text.
Working checkpoint — BED detail: Avoid presentation-only grids. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 20 of 36
20. Make links understandable
Anchor text should describe the destination instead of saying click here.
Working checkpoint — genomic feature: Test keyboard and screen-reader meaning. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 21 of 36
21. Validate unique IDs
Duplicate identifiers can route several positions to one unintended record.
Working checkpoint — item ID: Run whole-file uniqueness checks. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 22 of 36
22. Validate markup length and safety
Very long or malformed descriptions can damage usability or expose unsafe content.
Working checkpoint — rich description: Apply length and allow-list rules. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 23 of 36
23. Validate URL expansion
Every external-link template should produce the intended encoded destination.
Working checkpoint — custom track: Test special characters and missing IDs. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 24 of 36
24. Test the browser detail page
Open representative items and compare page content with the source row.
Working checkpoint — detail page: Include blocks, duplicates and long descriptions. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 25 of 36
25. Convert large tracks deliberately
A bigBed conversion needs an autoSql schema describing the extra fields.
Working checkpoint — BED detail: Archive text, schema and command. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 26 of 36
26. Protect sensitive annotations
Descriptions may reveal sample, patient or unpublished project information.
Working checkpoint — genomic feature: Apply governance before publication. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 27 of 36
27. Separate explanation from evidence
Rich prose helps readers but cannot upgrade the underlying observation.
Working checkpoint — item ID: Keep evidence class and uncertainty visible. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 28 of 36
28. Connect to Primary Science
A map pin, catalogue card and short museum label model position, identity and explanation.
Working checkpoint — rich description: Ask what each layer contributes. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 29 of 36
29. Connect to Secondary Science
BED detail shows how scientific communication adds context without changing raw coordinates.
Working checkpoint — custom track: Separate data, annotation and narrative. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 30 of 36
30. Connect to mathematics
Half-open intervals and block geometry remain exact even when prose becomes rich.
Working checkpoint — detail page: Check coordinate spans before reading the label. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 31 of 36
31. Connect to computing
Delimiter contracts, stable keys, safe HTML and URL encoding show practical data design.
Working checkpoint — BED detail: Test duplicate IDs and unsafe markup. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 32 of 36
32. Connect to pathways
Genome curation joins biology, information science, accessibility and web engineering and can illuminate STEM pathways.
Working checkpoint — genomic feature: Verify current study routes separately. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 33 of 36
33. Did you know?
A BED detail record can add a long HTML description after as few as four or as many as twelve BED fields.
Working checkpoint — item ID: Declare the chosen field count clearly. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 34 of 36
34. Write a reader-ready detail note
Name assembly, prefix length, ID namespace, evidence source, markup policy, links and validation.
Working checkpoint — rich description: Keep it beside the track line. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 35 of 36
35. Build a validation ladder
Check BED geometry, field count, tabs, IDs, descriptions, markup, URLs and live pages.
Working checkpoint — custom track: Stop at the first mismatched item. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver text, configuration, schemas, source citations, hashes, fixtures and bounded interpretation.
Working checkpoint — detail page: Make every detail page traceable to one record. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Contents · Previous section · Continue to the Science Learning Hub