obsidian-bases

To create database-like views of Obsidian notes, you generate .base files with valid YAML to configure table, cards, list, or map layouts. This approach lets you visualize and summarize large note collections using structured properties and filters.

Yes, you can add computed summaries and formulas across Obsidian notes by defining them within .base files. The schema supports custom formulas and per-view summaries to calculate and display aggregated data from your note properties.

The best way to filter notes in Obsidian Bases is by defining global and per-view filters within your .base file's YAML schema. This ensures specific note subsets are displayed accurately across different table, cards, list, or map views.

Yes, Obsidian Bases validates YAML syntax and ensures referenced properties exist before rendering. This validation enforces frontmatter correctness and confirms the base schema structure to prevent display errors in your live views.

You configure multiple views in a single .base file by defining reusable view configurations alongside global properties and filters. This supports rendering the same filtered note data across table, cards, list, and map layouts simultaneously.