⚡ Productivity

Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard

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.

0.0
0Reviews
P
October 8, 2026

Prompt

Act as an Obsidian power user who writes Dataview TABLE, LIST, and TASK queries from a real vault schema, respects existing YAML frontmatter fields, and builds a weekly review dashboard that stays honest about missing metadata.

Inputs:
- Folder map (projects, areas, daily notes, templates paths): [FolderMap]
- YAML frontmatter fields you actually use (status, due, project, area, priority, up): [YamlFields]
- Weekly review goals (find stale, open tasks by project, waiting on): [ReviewGoals]
- Dataview plugin flavor (Dataview queries vs DataviewJS) and any bans: [PluginConstraints]
- Sample note paths and frontmatter snippets: [SampleNotes]
- Output format: [Format]

Generate:
1. A schema echo: list YamlFields and FolderMap as understood; refuse to invent new keys unless marked optional proposal.
2. Three TABLE queries aligned to ReviewGoals (for example open projects, due this week, stale notes where up older than N days).
3. Two LIST queries for lightweight indexes (areas, waiting on people).
4. Two TASK queries that pull unfinished tasks from daily notes and project notes with FROM folder limits.
5. A weekly review note outline that embeds those queries in order with human checklist steps between them.
6. A troubleshooting card: DQL typos, WHERE on missing fields, calendar date formats, and tasks in callouts.
7. A migration tip if SampleNotes show inconsistent field names (status vs State).
8. A paste ready code block set labeled so users copy one query at a time.

Constraints:
- Never invent result counts, fake note titles beyond SampleNotes, or frontmatter fields not in YamlFields without labeling them as optional proposals.
- Prefer DQL over DataviewJS unless PluginConstraints asks otherwise.
- No em dashes.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard - Result

Examples

Example Input

FolderMap: Projects/, Areas/, Daily/, Templates/Weekly Review.md
YamlFields: status, due, project, area, priority, up, waiting_on
ReviewGoals: open projects not done; tasks due in next 7 days; notes with up older than 21 days; waiting_on list
PluginConstraints: Dataview DQL only; no DataviewJS
SampleNotes: Projects/Site Redesign.md status: active due: 2026-10-20 project: Site Redesign area: Work up: 2026-09-01 waiting_on: Dana; Daily/2026-10-07.md has tasks - [ ] Invoice Dana - [x] Standup
Format: schema echo, TABLES, LISTS, TASKS, weekly outline, troubleshooting, migration, paste blocks

Example Output

1) SCHEMA ECHO
Folders: Projects/, Areas/, Daily/, Templates/
Fields used: status, due, project, area, priority, up, waiting_on
Optional proposal only if needed later: review_date (not used below).

2) TABLE QUERIES
TABLE status, due, waiting_on, up
FROM "Projects"
WHERE status != "done"
SORT due ASC

TABLE file.link AS Note, up, area
FROM "Projects" OR "Areas"
WHERE up < date(today) - dur(21 days)
SORT up ASC

TABLE project, due, priority
FROM "Projects"
WHERE due >= date(today) AND due <= date(today) + dur(7 days)
SORT due ASC

3) LIST QUERIES
LIST waiting_on
FROM "Projects"
WHERE waiting_on
SORT file.name ASC

LIST FROM "Areas" SORT file.name ASC

4) TASK QUERIES
TASK
FROM "Daily"
WHERE !completed
SORT due ASC

TASK
FROM "Projects"
WHERE !completed
GROUP BY project

5) WEEKLY REVIEW OUTLINE
# Weekly review
## 1. Breathing room
- [ ] Close browser tabs unrelated to review
## 2. Open projects
`dataview` first TABLE here
## 3. Due in 7 days
second due TABLE
## 4. Stale notes
stale TABLE; bump up or archive
## 5. Waiting on
LIST waiting_on; send one nudge or clear field
## 6. Open tasks
both TASK queries; migrate orphans into a project note
## 7. Shutdown
- [ ] Set next weekly review reminder

6) TROUBLESHOOTING
- Empty table: check FROM folder spelling and status values (active vs Active).
- Dates: use YAML due: YYYY-MM-DD.
- Tasks not showing: tasks must be markdown - [ ] lines; callout nested tasks may need WHERE meta path tweaks [confirm Dataview version].

7) MIGRATION
If some notes use State instead of status, normalize with a search replace before relying on WHERE status.

8) PASTE BLOCKS
(Use three backtick dataview fences in vault; shown here as labeled DQL)
[DQL open projects] TABLE status, due, waiting_on, up FROM "Projects" WHERE status != "done" SORT due ASC
[DQL stale] TABLE file.link AS Note, up, area FROM "Projects" OR "Areas" WHERE up < date(today) - dur(21 days) SORT up ASC
[DQL tasks daily] TASK FROM "Daily" WHERE !completed

Reviews (0)

Please login to leave a review.
Loading reviews...