The framing of a collection for a specific purpose, balancing comprehensiveness with the actor’s immediate focus. Data view combines varied representations with filtering, sorting, and grouping to let actors scan, explore, and interact with items within the view system.
Saved views
Saved views persist particular framings to reduce friction for repeat tasks, support different actor roles, and provide continuity across sessions.
- Developers define default views that align with the application’s core use cases or intended actor journeys
- Administrators configure role-specific or task-specific views shared across teams or departments
- End users create personalised views tuned to their workflow or preferences
Related components
- Representation: Table, cards, list, timeline, canvas, grid, calendar, gallery, kanban, gantt, the list goes on
- Action bar — the container for batch actions once a selection has been made
To-do
Follow-up patterns to capture: inline editing (direct manipulation of displayed data), search, pagination.
Related patterns
Enables
- Selection — staking a subset of items as the target of subsequent action
Complements
- Semantic zoom — scale-bound traversal between collection and item granularities, uniform across the population
Related
- Needs-based view — Collection representations with framing intents
- Item view — Single-entity counterpart
- View — Collection representations with filtering, sorting, and grouping
- Charting data — a chart is one of the representations a collection framing can take — the analytic sibling of table and cards
- Overview and detail — The "Overview" component.