There is a particular moment in the life of a well-kept Obsidian vault. The properties are consistent. Every note has a type, a status, and a next. The Base works. And yet working in it feels like reading a phone book: active projects, a dentist reminder with a date, three unfiled captures, and last Tuesday’s meeting notes all in one long table, sorted by nothing in particular.
The usual response is to add something. A priority field. A context field. A second set of properties just for meetings. A few weeks later the new fields are filled in on some notes and not others, and the vault has two dialects again.
The better response is almost always to add a view, not a field. The facts you need are already in the frontmatter. What is missing is a cut of those facts shaped like the work you are doing right now. The Bases View Pack (for Obsidian) gives you those cuts, ready-made: table, list, cards, and kanban layouts on the same short property set, plus a dedicated Meetings base, in a starter vault you can open in the first hour.
Get it here: Bases View Pack (for Obsidian)
What does “one table for everything” actually cost you?
Five problems, each with a recognizable shape.
Consistent properties, one table. The property work is done, and it still does not feel organized, because active work, dated work, unfiled captures, and projects want different shapes. A table is excellent for scanning columns. It is mediocre for triaging an inbox and poor at giving you the picture of where everything stands.
A second property set, invented for a second view. This is the expensive one. To get a meetings view, someone adds meeting_date, attendees, and meeting_status. Now meeting notes have their own vocabulary, the main Base ignores them, and the two sets drift apart a little more with every new note.
No dedicated cut for inbox, dated work, or active projects. Each of those deserves its own view because each one prompts a different action: decide, schedule, or do.
Meetings mixed into general work. Meeting notes are perfectly good notes. They are also a different kind of thing to review, and they deserve a place where only meetings appear.
Expecting a Base to read inline fields. Bases read YAML frontmatter. They do not read Dataview-style inline fields such as status:: active written in the body of a note. If a view looks empty, the fact you want probably lives in the body.
None of these require more properties to solve. They require more lenses on the same ones.
Why is “same data, many views” such a durable idea?
Because people who manage information seriously have converged on it again and again.
When Luca Pacioli published his account of double-entry bookkeeping in 1494, merchants were already keeping the same transactions in more than one book: a journal in date order and a ledger arranged by account. Nobody invented new transactions to get the second book. The ledger was a different arrangement of facts that were already recorded, and it answered questions the journal could not.
When Charles Ammi Cutter published his Rules for a Dictionary Catalog in 1876, the catalogs he was writing for routinely gave one book several cards — under author, title, and subject — so a reader could arrive from whichever direction they started. The book did not change. The number of ways to find it did.
When Florence Nightingale presented army mortality figures in 1858, the numbers already existed in tables. Her polar-area diagrams were a new view of those same records, and they made the pattern — far more deaths from preventable disease than from wounds — impossible to miss.
A Base view is the same move at a smaller scale. Your notes already hold type, status, next, area, and due. A table, a list, a set of cards, and a kanban board are four ways to read those five fields. You get the ledger without writing new entries.
What is in the pack?
The zip contains a 4-page guide, a starter vault, and a README.
The starter vault is a folder you open as a vault in Obsidian 1.15.1 or later. Inside:
00-Start-here.mdandProperty-set.md.- Five official Templates-plugin templates —
note,project,meeting,source, anddecision— all sharing the same keys. Bases/Work.base, with five views:- Active (table): notes whose status is not done, parked, or inbox. Columns: name, type, status, next, due.
- Due soon (table): notes that actually have a due date, with
dueas the leading column. - Inbox (list): notes whose status is inbox.
- Active projects (cards): notes with type
projectand statusactive. - By status (kanban): grouped on
note.status, in the order inbox → active → waiting → done → parked.
Bases/Meetings.base, with a Meetings table and a Meetings list, already filtered totype == "meeting".- A fictional Northshore Studio note set — a made-up studio, clearly labelled, with its own short
FICTIONAL-readme.md— so every view has rows the first time you open it.
The guide covers the official layouts the pack uses, the shared property set, the first-hour walk, what each view is doing, how to copy the Bases into a vault you already have, a short daily pass, and the rule for when a new view — or, rarely, a new field — has earned its place.
The Markdown and Base files were checked as valid YAML when the kit was built. The views themselves use the official core Bases layouts: table and cards (official since Obsidian 1.9), list (since 1.10), and kanban (since 1.14). A map layout also exists from 1.10, but official Help states it requires the Maps plugin, so this pack does not ship one. Everything here works with core plugins only — no community plugin required.
Why does each layout fit its job?
This is where the pack earns its keep, because the layouts were not chosen for variety. Each one matches the action the view is meant to prompt.
Tables are for scanning. Active and Due soon are tables because you read them column by column: what is it, where does it stand, what is next, when is it due.
Lists are for triage. Inbox is a list because the only question for each row is “what is this, and what happens to it?” A list keeps the noise down while you give each capture a type and a next action, park it, or delete it.
Cards are for focus. Active projects are cards because a project is the kind of thing you want to see as a whole — name, next action, due date, area — one tile at a time, without a dozen columns of context.
Kanban is for the big picture. By status shows every note in its column, which is the fastest way to notice that “waiting” has quietly become the largest pile in the vault.
And the Meetings base exists because meetings are a different review. When you want last week’s meetings and their open next actions, you want only meetings — and because the filter is type == "meeting" on the same property set, no meeting-only fields are required.
What does the first hour look like?
Open the vault/ folder as a vault in Obsidian 1.15.1 or later. Enable the core plugins Bases and Templates, and set the template folder to Templates. Open 00-Start-here.md, then Bases/Work.base.
Walk the views in order: Active, Due soon, Inbox, Active projects, By status. Then open Bases/Meetings.base and switch between the table and the list. Create a new note, insert the project template, fill type, status, next, and a due if it has one, and watch it show up in the views it belongs in.
Finish by reading Property-set.md. The set is short on purpose: type (note, project, meeting, source, decision), status (inbox, active, waiting, parked, done), next (one action, or empty), area (optional), and due (a real YYYY-MM-DD date, or empty).
How do you use the Bases in a vault you already have?
Copy Bases/Work.base and Bases/Meetings.base into your vault. If your notes already use these five keys, the views pick them up once the folder filter matches where your notes live; if they live somewhere other than Notes/, change or drop the file.inFolder("Notes") filter. If you do not use these keys yet, copy Property-set.md and the templates as well, and start new notes from a template so the views keep receiving notes they can read.
The guide’s daily pass is short enough to actually do:
- Open Inbox. Give each row a type and a next action, park it, or delete it.
- Open Due soon. Do what is actually due, or change the date honestly.
- Open Active, or the project cards, and do the thing in
next. - Leave parked and done notes alone. The Active view already hides them; the kanban still shows them when you want the full picture.
When has a new view earned its place — and when has a field?
Write the view you want as a sentence first. “I need a list of waiting notes in the recital area.” If type, status, area, and next can already answer that, add a view. Do not add a field. If they genuinely cannot, add one field, document it in Property-set.md, put it on the templates that need it, and then add the view.
That order matters. A field without a view is a souvenir. A view without a new field is free.
How does this sit next to the Properties Day-1 Kit?
The Properties Day-1 Kit is the property set, the naming rules, the templates, and a first working Base. The Bases View Pack is the view layer on that same set. If you own both, copy these Bases into the vault that already uses those keys and you are done. If you only have this pack, the starter vault still includes the property set and templates, so it stands on its own.
It is also not the Ontology & Knowledge-System Starter Kit. That kit is a knowledge-graph starter. This one is everyday views on everyday note properties. They complement each other; none replaces another.
Obsidian is a trademark of its trademark owner. This is an independent tool for people who use Obsidian. It is not an official Obsidian product, and it does not include the Obsidian application.
The same notes, finally in the right shapes
You are not paying for a new property system. You are paying for five ready views on a set that is already short, a Meetings base that is already filtered, templates that will not drift from those keys, and a guide that teaches the one rule that keeps a vault lean: add a view before you add a field. The fictional example notes mean every view has something in it the moment you open it.
Get the Bases View Pack (for Obsidian): Bases View Pack (for Obsidian)
It will be listed on our Tools for Obsidian page alongside the rest of the tools in that line. You can browse every Organa Obscura tool on the Products page.
Leave a Reply