obsidian-bases

Dynamic dashboards in Obsidian are created using .base files to transform note frontmatter into queryable table, card, list, or map views. You define global filters, formulas, and display properties to standardize note presentation without manual maintenance.

Filtering Obsidian notes by tags, folders, and properties uses boolean logic within .base files to include or exclude notes. You apply global and per-view filter expressions to ensure the rendered views display only the matching metadata criteria.

Computing derived fields and summaries in Obsidian Bases is fully supported through formulas. You define formula-derived properties to calculate rollups like averages, counts, ranges, and date min/max values for ordering and summarizing note metadata.

The Obsidian Bases YAML format supports defining one or more views within a single .base file. This allows you to render different tables or cards from the same filtered note collection based on global properties and computed formulas.

Building a task tracker or reading list using Obsidian Bases requires defining a .base file with filters for specific tags or folders. You then add formulas to compute progress metrics and configure views to render the notes as interactive tables or cards.

Obsidian Bases formulas and filters require valid YAML syntax and validate that referenced formulas and properties exist. The main limitation is syntax errors from invalid references, which prevent the views from rendering the queryable note collections correctly.