obsidian-bases

To create Obsidian Bases, you build a .base file with YAML frontmatter, define global and per-view filters, wire optional formulas and summaries, and configure table, card, list, or map views. This generates queryable, database-like dashboards from your note metadata.

Obsidian Base files are used to organize notes into queryable databases, building dashboards for tasks, reading lists, indexes, and location collections. They apply filters and computed formulas to note metadata to display aggregated metrics and derived values across multiple view types.

Yes, you can add formulas and summaries to compute derived values like statuses, durations, and averages in Obsidian Bases. These computed metrics are wired into your views, allowing you to display aggregated data directly within your table, card, list, or map configurations.

You validate YAML syntax and property references in Obsidian Bases to reduce common rendering failures from syntax errors or undefined properties. This ensures your filters, formulas, and view configurations correctly reference the defined properties before the file renders.

Obsidian Base views fail to render correctly due to YAML syntax errors, incorrect filter syntax, or undefined property and formula references. Validating your .base file structure, ensuring correct frontmatter, and verifying formula wiring reduces these common rendering failures.

Yes, Obsidian Bases supports multiple view types including table, cards, list, and map configurations. You can apply configurable ordering and grouping within these views to match how you want to read and interact with your filtered, formula-backed note collections.