Obsidian Dataview: Stop Searching, Let Your Notes Come to You

Dataview lets you write queries once and have your notes surface themselves. Here's how I use it in daily notes, task tracking, and long-term review — without turning Obsidian into a database.

When I first started using the Dataview plugin seriously in 2021, the thing that changed most wasn’t my notes — it was how often I had to look for them.

Before Dataview, I’d open my daily note every morning and manually hunt for today’s due tasks, then flip through past notes to see what I was thinking about a year ago. After Dataview, those things just appeared. The information came to me. That shift sounds small. It isn’t.

Dataview shifts notes from static filing to dynamic retrieval

Folder-based organization locks information into fixed categories at the time you create a note. That structure breaks the moment you need a cross-cutting view — “show me everything tagged ‘project-x’ from last quarter, sorted by last updated.”

Dataview takes the opposite approach. Put notes anywhere. Write a query to generate whatever view you need at that moment. The analogy I find useful: Zettelkasten’s physical index cards had the benefit of clustering related ideas together on your desk. Dataview does that digitally, on demand, with filters.

Read queries as English sentences, not code

The biggest reason people avoid Dataview is the impression that it requires programming knowledge. It doesn’t — if you stop reading it as code.

TABLE file.mtime AS "Last Updated"
FROM "notes"
WHERE contains(tags, "review")
SORT file.mtime DESC
LIMIT 10

Read that line by line: “Give me a table / from the ‘notes’ folder / where the note has a ‘review’ tag / sorted newest first / show only 10.” No syntax to memorize. Just English with a bit of structure.

Once the intimidation is gone, the fastest way to learn is to copy a working query and change one thing at a time.

Four output formats cover almost everything

Dataview has four ways to display results. Knowing which one fits your use case makes the rest of the query easy to fill in.

Format	When to use it
`LIST`	Simple file name lists. Start here.
`TABLE`	Multiple properties as columns — reading logs, task overviews
`TASK`	Checkbox-style output for task management
`CALENDAR`	Visualizes date properties on a calendar grid

Don’t try to learn all four before starting. Get LIST working first. Move to TABLE when you actually need the columns.

Daily notes are the best place to start

The highest-leverage place to use Dataview is your daily note template. Write the query once, and every time you open a daily note, it runs fresh.

Surface today’s due items automatically

LIST
FROM ""
WHERE due = date(today)

Add a due: YYYY-MM-DD property to any note. That’s all it takes.

Pull up what you wrote exactly one year ago

LIST WHERE file.cday = date(today) - dur(1 yr)

I’ve had this in my daily note since 2022. It’s become one of the most reliable reflection triggers I have — past context arrives without any effort on my part.

Keep a reading log that never goes stale

TABLE read AS "Finished", title AS "Title"
FROM "books"
SORT read DESC

With a read: YYYY-MM-DD property on each book note, the list stays current automatically. “Forget to update the list” stops being a failure mode.

Dataview vs. Obsidian Bases

Obsidian’s core Bases plugin covers similar ground — filter notes, display properties in columns. The choice between them is simpler than it looks.

Start with Bases if you want a UI-driven experience. You can edit properties directly from the table without touching a note. Better for daily interaction.
Switch to Dataview when you need date arithmetic, multi-condition filters, or aggregated calculated fields. Also better for templates you set once and never touch again.

Durable “always-on” queries belong in Dataview. Interactive working tables belong in Bases.

Use Dataview sparingly to keep Obsidian flexible

Once Dataview clicks, there’s a temptation to query-ify everything. Resist it. When every note requires a specific property structure to appear in your queries, Obsidian stops feeling like a frictionless writing environment and starts feeling like a form to fill in.

Dataview earns its place in three spots: daily note templates, scheduled reviews, and deadline tracking. Those three alone cover the majority of what makes the plugin genuinely useful.

The goal isn’t to build a database. It’s to make the notes you already have easier to find when you need them — or better, to make them show up before you think to look.