Description
Dotabase Browse Views let one schema-backed collection support different working perspectives without duplicating its data. Users can open saved views, switch among the supported list, table, board, gallery, timeline, feed, graph, dashboard, and other rostered presentations, then configure filters, sorts, grouping, visible properties, widths, display details, and ordering. A saved view restores its complete URL and display state as one coherent selection.
The browse layer is schema-driven. Property renderers come from a central registry, row actions and metadata overlays are shared, and view-specific chrome mounts through the page top bar. Large collections use virtualization and lazy detail reads where needed, while every presentation carries explicit loading, empty, error, and ready states.
Selling Points
- Lets teams adapt the same trusted records to planning, scanning, reviewing, and visual analysis without maintaining parallel databases.
- Saves view configuration, so each recurring workflow opens with its useful filters and fields already applied.
- Keeps property rendering consistent across views, reducing mismatched values and controls.
- Handles large collections through virtualization and lazy metadata access rather than loading every secondary detail.
- Supports collaborative schema-driven workflows while preserving a single underlying source of truth.
User Story
A product manager opens one Roadmap Dotabase as a board grouped by status for planning, switches to a table with selected fields for review, and saves a filtered timeline for upcoming launches. Every view reflects the same rows, and reopening a saved view restores its intended configuration.
Extension Surface
The capability is configurable through saved view records and their settings. apps/web/src/modules/dotabases/CustomizeViewPopover.tsx exposes display options, and apps/web/src/modules/dotabases/SavedViewModal.tsx creates or updates durable view definitions. New view types require product approval and code, so end-user configuration does not amount to an external renderer plugin.
Capabilities & Limits
- Presents a Dotabase through multiple schema-aware view types.
- Saves filters, sorts, grouping, visible fields, display configuration, and view order.
- Supports bulk actions, row context actions, virtualization, and view-specific toolbars.
- Limit: users configure the sanctioned view roster; they cannot upload arbitrary view code or create an unsupported presentation from the UI.
Implementation Map
apps/web/src/modules/dotabases/DotabasesBrowsePage.tsxapps/web/src/modules/dotabases/views/Table.tsxapps/web/src/modules/dotabases/CustomizeViewPopover.tsxapps/web/src/modules/dotabases/SavedViewModal.tsx