Work with tasks, data views and queries
Your goal
Display notes with properties as tables, tasks or calendars.
Before you start
Try the demo’s sample views with fictional tasks first.
Steps
- Use consistent properties such as
status,priorityanddue. - Open a
.basefile and switch its configured views. Supported configurations render tables, task lists, kanban or calendars. - Edit writable table properties or task status; changes save to the original note.
file.*and formula fields are read-only. Property queries use the limited TABLE/LIST grammar, without arbitrary execution.
Note databases
Use New database in the directory heading/menu to create a .base configuration and choose its record folder. Table, list, board, gallery and draggable timeline views share the same Markdown notes. Configure typed fields, filters, sort, grouping and layout in the toolbar; click a record to edit its properties and body. Use Insert database in the editor to embed a stable view. Removing a field/view keeps note data; recycling a record moves the original note to recoverable trash. Complete database instructions.
Calendar notebook
Use Calendar notebook in the sidebar to schedule linked tasks separately from deadlines, write daily notes and enable reminders. Calendar guide.
For two computers, sync Calendar/LeafLoom/ inside the vault and keep .vault-rag excluded. Use Sync and conflicts to review competing versions, and enable reminders separately on each computer. See the calendar guide above for upgrade and sync steps.
What to expect
Views present existing notes. Moving tasks or editing properties changes their source files.
If it does not work
This supports a bounded grammar and view set, not the entire Dataview or TaskNotes plugin environment. Inspect fields and configuration if a view fails.