Skip to main content

Assignment 7 Walkthrough and Reference

Where this fits

You have studio drafts from dash06. This page is the bridge from studio work to a submitted Assignment 7. The deliverables here mirror the A7 README exactly — this page explains what goes into each file, how to verify it, and how the work connects to your term-project final dashboard.

Deadline and the decision rule

Assignment 7 is due the Monday after Week 8 class, 4 PM. The required pathway is the Quarto starter dashboard (dash03).

Decision rule pinned at the top: adapt the Quarto starter. The Shiny app is a demonstration only and is not an approved A7 submission pathway. If you are interested in using Shiny for your final-portfolio dashboard, talk with the instructor — Shiny is not a default-approved pathway and requires instructor approval.

The nine A7 deliverables, explained

Each file goes in assignments/assignment07-dashboard/submission/.

testing-log.md, limitation-note.md, and privacy-check.md are brief evidence files. One to three focused sentences or bullets are enough unless the assignment asks for more.

All nine files are [required]. The A7 README marks the brief ones with [brief — 1-3 focused bullets or sentences are enough]; the full tag vocabulary is in How To Read Submission Lists.

1. dashboard.qmd

The adapted copy of the personal-workspace Quarto starter. Make the allowed audience-facing text change here and retain the source with the evidence files.

  • Verify: render this exact submitted file in a fresh Codespace.

2. dashboard-adaptation-note.md

Audience, question, control, visualization, the element you changed, and the KT rationale. Pattern after the studio Step 1 and Step 2 outputs.

  • Verify: a peer can read this and identify your audience and question without seeing your code.

3. before-after-text.md

The original text, the revised text, why the change helps the audience, and a confirmation that no analytic logic changed. Pattern after the studio Step 3 output.

  • Verify: the change is genuinely audience-facing text. If you cannot say “no analytic logic changed”, the change does not belong in A7 (see dash04).

4. testing-log.md

Date tested, the command or render path you used, the values you tried, and the result. Pattern after the studio Step 4 output.

  • Verify: another student could reproduce your test by following your log.

5. limitation-note.md

One sentence on what the dashboard does not support. Use the descriptive-vs-causal patterns from eda05.

  • Verify: the sentence belongs in or beside the dashboard, not just in a separate file.

6. privacy-check.md

Three sentences from dash05: data source and classroom-use boundary, aggregate-only confirmation, no row-level data shared with AI.

  • Verify: three sentences, each specific.

7. dashboard-preview.png

A screenshot or exported preview of the affected dashboard area (after the text change).

  • Verify: the preview clearly shows the revised audience-facing element. No row-level table previews.

8. reproducibility-note.md

One paragraph naming the render command, the relative path, and whether the dashboard renders in a fresh Codespace.

  • Verify: the path is relative, and the note matches what testing-log.md says.

9. ai-use-note.md

What AI helped with (or a sentence saying you did not use it) and how you verified the result.

  • Verify: specific (which prompt? which file?), not vague.

Reproducibility checklist for A7

Before you click submit:

  • The adapted Quarto file renders in a fresh Codespace.
  • The data path is relative (examples/nhanes-equity/data/nhanes_equity_v6.csv).
  • The preview screenshot shows the revised text change clearly.
  • The dashboard contains a visible limitation sentence (not just in a separate file).
  • No row-level data appears in any screenshot or shared output.
  • All nine files are committed and pushed.

A pathway decision template you can reuse

When the term-project conversation comes up later in the term, your team will face the same pathway choice for the final portfolio. Use this short template to document the decision:

Our audience is ______. We need ______ kind of interactivity. The simplest pathway that serves this need is [Quarto dashboard-style page / Shiny app / static HTML/JS]. [If Shiny or static HTML/JS:] We have instructor approval recorded on ______.

Default to Quarto. Justify deviations.

Privacy-safe publishing checklist

Reused from dash05 for your reference:

  • No row-level data in screenshots, AI chats, or public README.
  • No small-cell interpretations.
  • Descriptive limits stated; no causal language; no national-prevalence language.
  • Cached classroom data kept separate from any raw retrieval workflow.
  • Row-level data never uploaded to external AI tools.

Paths you will use repeatedly

What Where
Cached dataset (CSV) examples/nhanes-equity/data/nhanes_equity_v6.csv
Cached dataset (RDS) examples/nhanes-equity/data/nhanes_equity_v6.rds
Student starter dashboard assignments/assignment07-dashboard/dashboard-starter.qmd
Adapted submitted source assignments/assignment07-dashboard/submission/dashboard.qmd
Shiny exemplar (instructor demo only) examples/nhanes-equity/app/app.R
Adaptation template assignments/assignment07-dashboard/dashboard-adaptation-template.md
Submission folder assignments/assignment07-dashboard/submission/

Five quick knowledge checks

  1. Name three differences between a static report and a dashboard.
  2. Which pathway is the required core for A7?
  3. In one sentence, why is the Quarto starter dashboard preferred over editing the Shiny app for A7?
  4. Name two changes that count as “UI-text-only.” Name two that do not.
  5. What three sentences go in privacy-check.md?

Where this goes next

Next week (Week 9) takes one finding from your dashboard and turns it into a concise scientific communication product. The cleaner your A7 limitation sentence is, the easier the Week 9 plain-language summary will be.