Summary-Detail View¶
Interface — instantiates Progressive Disclosure
A paired view where a compact summary connects to selectable detailed records or explanations.
A Summary-Detail View pairs a compact summary — almost always a list of items — with a detail region, so that selecting an item in the summary shows its full record, and a return path brings the user back to the list. Its defining idea is the pairing: summary and detail coexist as a master list and a detail view, and the user browses many items by their one-line summaries, opens any single one on demand, and returns to keep browsing. It is navigation between a list and its records — not an in-place unfold of content on the same block, and not a descent through levels of aggregated data. The unit of interaction is "pick an item, read it, go back."
Example¶
An email client shows the classic form. The left pane is a list of messages, each summarized by sender, subject, and a snippet — enough to triage without opening anything. Clicking a message fills the reading pane with the full email; a back gesture (or simply the persistent list) returns the user to where they were, scroll position intact. Over a few minutes a user scans forty summaries, opens three that need reading, and returns to the list after each. They get an overview of the entire inbox and the full text of any single message, without the client having to load forty message bodies or the user having to leave the list to see one.
How it works¶
The summary layer is a set of item summaries — each row carrying just enough to identify and triage. Selecting a row is the drilldown: it surfaces that item's full detail, either in an adjacent pane (both visible at once) or by navigating to a detail screen (common on small displays). A return path takes the user back to the summary with their place preserved — the same selection highlighted, the same scroll position held. The pattern's whole value depends on the summary carrying the fields a user needs to choose which item to open; when it does, the user opens only the few that matter. It differs from a data drill in that selection moves sideways to a record, not down into an aggregate, and from an in-place expander in that the detail lives somewhere the user travels to and comes back from.
Tuning parameters¶
- Layout — side-by-side panes (summary and detail both visible) versus a drill-and-return stack (one at a time). Panes suit wide screens and rapid triage; stacking suits mobile.
- Summary richness — how many fields each row carries. Richer rows let users decide without opening records; too rich and the summary stops being a summary.
- Selection persistence — whether the opened item stays highlighted and the scroll position holds on return. Persistence makes browsing feel continuous; losing it forces users to re-find their place.
- Return behavior — an explicit back control versus an always-present list. Persistent lists make return free; explicit-back is unavoidable when detail takes the whole screen.
- Preview versus full detail — whether selection shows a preview or the complete record, trading a lighter open against a second step to see everything.
When it helps, and when it misleads¶
Its strength is browse-and-inspect at scale: a user keeps an overview of the whole set while pulling the full detail of any one item on demand and returning to the set — the master–detail pattern that makes large collections navigable without loading or showing everything.[1]
Its failure mode is a summary that omits the one field a user needs to choose, which forces them to open every record in turn — collapsing the pattern back into the linear slog it was meant to prevent. A second failure is drift: the summary and the detail fall out of sync as data changes, so the row promises something the record no longer contains. The guarding discipline is to put the discriminating fields — the ones that decide whether an item is worth opening — into the summary, and to keep summary and detail sourced from the same data so they cannot contradict each other.
How it implements the components¶
default_summary— the compact list of item summaries is the always-present first layer, the overview the user works from.drilldown_path— selecting a summary row surfaces that item's full record, the connective from overview to detail.return_path— a back control or the persistent list returns the user to the summary with their place preserved, so browsing stays continuous.
It does NOT implement information_layer or reveal_trigger — the in-place accordion unfold of Expandable Section; a summary-detail view moves the user to a separate detail record and back, rather than expanding content on the same page. (Nor does it descend aggregation levels the way Drill-Down Dashboard does — its detail is one item's record, not a decomposition of a total.)
Related¶
- Instantiates: Progressive Disclosure — it is the archetype's browse-and-inspect face: an overview that keeps the full record of any item one selection away, and a way back.
- Sibling mechanisms: Expandable Section · Drill-Down Dashboard · Tiered Decision Support · Advanced Settings Panel · Just-in-Time Help · Staged Onboarding · Progressive Training Module · Wizard or Stepper Workflow
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Summary-Detail View operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it a paired view where a compact summary connects to selectable detailed records or explanations.
Independent corroboration: The frozen evidence defines Summary-Detail View as 'A paired view where a compact summary connects to selectable detailed records or explanations', so its operative form is Interface, Display & Cue.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: A summary linked to selectable detail is the overview-plus-detail information-visualization pattern.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: a paired view where a compact summary connects to selectable detailed records or explanations.
- Data Science & Analytics — Dashboards use drill-down from aggregates to observations.
- Library & Information Science — Hierarchical finding aids connect abstracts to records.
Review resolution: The blind reviewers agree that human_computer_interaction is the primary origin and differ only on alternate origin disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Tidwell, J. Designing Interfaces. 2nd ed. O'Reilly Media (2010). Presents Overview Plus Detail as keeping an overview visible while users inspect selected details without displaying all detail at once. registry ↩