As a maintainer and long-time user of Dataview I’m somewhat biased, but I do like this write up and suggestions, and would just add a few more thoughts related to this:
- I’ve also used to have my tasks mainly in the daily notes, and kept going back and forth. Next step was to start building queries to gather them from previous sources and display that in the daily note. However, I also arrived at the thought that I don’t really need for the daily note to be cluttered by this list of tasks which is changing, and doesn’t really have any use when looking at past daily notes. So I created a dedicated page for task handling (which admittedly uses both Dataview and Tasks for various operations)
- I still add my tasks to the daily notes, but the task handling is done on that dedicated page. To me this makes sense since I also uses custom tasks with alternating status characters to display my various events/actions/thoughts/reflections during the day
- I’ve recently installed the Contextual sidecar plugin which I’m evaluating, but it has an interesting concept of changing its panel in the right sidebar according to file context (and/or) tags. This can allow you to have that dedicated “widget” readily available, and have it change according to the context of the note you’re viewing.
- This allows for having it display something if you’re in a daily note. Like the current tasks
- It also allows for generally having this or that buttons and information generally available. Maybe like having dedicated link buttons to go somewhere or open certain files in your vault
- One final point I would like to make: Please don’t duplicate tasks around in your vault. I’m a strong believer that an open task should only exists once in your vault! You could show it off/display it various place if you want to, but it should only be defined once. I’m not in favor of copying tasks over to the next day and leaving a duplicate open in an earlier note. The closest thing I do, is to migrate some tasks between months, where I copy the task and mark the previous task defintion as migrated (using
[>]) so it’s closed off. (Yes, it’s a personal preference, but I see so many issues when you just copy and get a multitude of duplicated tasks in your vault, so just please don’t do it!)