obs-obsidian-bases

Obsidian Bases are created by generating valid YAML specifications that define global and per-view filters alongside computed formulas. You configure note targeting by tags, folders, and properties, then render results as table, cards, list, or map views within a single .base file.

Date math and duration expressions are fully supported in Obsidian Bases formulas for computing derived properties. The generated YAML validates safe date and duration handling, ensuring computed fields reference existing properties correctly without syntax errors.

Organizing multiple views in an Obsidian Base involves defining global filters that apply across all layouts, then configuring per-view filters for specific note sets. You can generate table, cards, list, and map views with consistent property naming and per-view summary metrics.

Obsidian Bases support per-view summary metrics for computed properties through formula definitions. The YAML specification validates that every referenced formula and property exists, producing accurate aggregate calculations for targeted note collections.

Obsidian Base YAML validation fails when formula references, property names, or filter configurations contain syntax errors or inconsistent naming. The generation process verifies that every referenced formula and property exists in the YAML structure before producing the vault-ready .base file.

You need an Obsidian Base when you want to turn note collections into reusable database-like views with computed formulas. Standard note views lack global filtering, per-view configurations, and formula-based computed properties that Bases provide through validated YAML specifications.