How to Use the Obsidian Dataview Weekly Review Prompt to Build Views From Your Real Vault
Design Obsidian Dataview TABLE, LIST, and TASK queries from your real folder layout and YAML frontmatter fields, then assemble a weekly review dashboard that surfaces open tasks, stale notes, and projects waiting on others without inventing fields you do not use.
Dataview only helps if the queries match the YAML you already write. Invented fields and fake note counts make a pretty dashboard that shows nothing. The Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard prompt builds TABLE, LIST, and TASK queries from your folder map and frontmatter, then nests them in a weekly review note with human checklist steps between the embeds.
What the prompt produces
- A schema echo of your folders and fields, refusing silent invention.
- Three TABLE queries for open projects, due soon, and stale notes.
- Two LIST queries for indexes like waiting_on.
- Two TASK queries limited by folder.
- A weekly review outline with queries in order.
- A troubleshooting card for DQL and date formats.
- Migration tips when status versus State drift appears.
- Paste ready labeled blocks so you copy one query at a time.
How to fill the inputs
FolderMap should list real paths: Projects/, Daily/, and so on.
YamlFields must be fields you already use. If you do not have waiting_on, do not pretend.
ReviewGoals keep the dashboard purposeful: stale, due, waiting.
PluginConstraints should say DQL only if you are not ready for DataviewJS.
SampleNotes with real frontmatter snippets ground the examples.
Reading the example output
The sample vault uses status, due, project, area, priority, up, and waiting_on.
- Open projects table sorts by due.
- Stale notes use up older than 21 days.
- Tasks pull from Daily and Projects without inventing completion rates.
Tips for better results
- Normalize field names before you build the dashboard.
- Put a breathing room checkbox before the first query so review stays human.
- Confirm Dataview version quirks for tasks inside callouts.
Mistakes to avoid
- Do not ask for fake counts of how many notes matched.
- Do not mix DataviewJS when you asked for DQL only.
- Do not point FROM at folders that do not exist.
Who it is for
Obsidian users who want a weekly review that respects their vault schema.
Related PromptDig links
Open the Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard prompt with your folder map and YAML. For more productivity prompts, Browse more prompts. If your weekly note finally stays honest, Share a prompt.
Making the weekly review stick
Put the weekly review note on a recurring calendar block. Open it, breathe, then run the queries top to bottom. When a TABLE is empty, that is success, not failure. When stale notes pile up, archive or bump the up field the same day.
If waiting_on lists the same person three weeks running, the query is doing its job. Send one nudge or clear the field. Do not add a second waiting field.
Keeping Dataview honest
Refuse optional proposals until you actually create the YAML key in templates. A dashboard that references review_date before any note has review_date will train you to ignore empty panels. Start with the fields you already type on every project note.
From daily notes to projects
TASK queries that only look at Daily/ will miss work captured inside project notes. Include both folders, then spend two minutes moving orphan tasks into the right project during review. That migration step is why the outline places human checkboxes between embeds.
If your vault uses periodic notes plugins, keep the FROM paths matching the folders you actually write to. A beautiful query pointed at the wrong year folder will look like you have no work left.