@@construct_by_dee I like it a lot! I'm using the "older" version of your system (with the inline log:: variable), so I haven't upgraded completely to use Tasks for every log. Although I would love to upgrade, because it looks so much better. But yeah, without your videos I've never even considered this type of daily/weekly/monthly system you have going, so I thank you for that! :)
thanks again for your effort on these and continuing to flesh out a system that works well for you in Obsidian. i paused when you suggested at about 10:20 that the log of the [[Cafe more exploration]] #intent/to-go tag would just be removed when the place was visited. It was my intent on day of the note. then when it was visited, it will still show up as a place to go even though it was visited based on the coding. So the tag needs to go, or at least change, and that it WAS my intent on that day I still want to note. It would go away from the note listed, perhaps it would have it's own note... so perhaps #/intent/was/to-go would be appropriate? this of course depends on ones sense of propriety about the accuracy of past daily notes. and the workflow set up around managing updates that impact how tasks and tagged items show up in MoC's and Lists. Have you decided on a solution for this that you follow personally?
There’s definitely room for improvement and personal interpretation in my workflows, so I’m glad you noticed this small gap. Although this issue doesn’t particularly bother me, it’s something I’ve considered in the past. Ideally, the best solution might be to have the log checked and include the date, similar to what you'd expect from the Tasks plugin, to indicate when the "action" or "intent" was completed. This way, you could create a Dataview to retrieve all unchecked "intent/to-go" logs and another Dataview for checked logs to see which places you actually visited, along with the "completed date." But honestly, this problem has many potential solutions, and I’m not completely sold on any of my ideas yet. I’d love to hear your insights!
@@construct_by_dee i think i am getting ahead of myself a little bit and need to wait for the problem to pop up before formulating a solution. i do have a hard sense that changing the daily note sometime in the future isn't a good one, as it's changing history. so completing could work and having the dataview syntax check for this and show uncompleted and completed in the same MoC note. thanks!
I'm very interested in changing my system to your Daily Notes system. However, I do want to take notes on the go. Does this setup work well on mobile? I am trying to figure out how difficult it will be without hotkeys and on the tiny phone keyboard :\
I've been using Obsidian Sync for quite some time and it works well. That does mean that there are some cost involved which isn't ideal. For the 'logging' I find it simple. The hashtags also auto-suggest based off of what is in your vault already. Just remember, it doesn't need to be perfect. The only thing you need is the task box (which we use to pull the data through to the data view), the tags (which gives it context), and the note or link.
Yay! Glad to see you're back making videos!
In fact, your playlist is the biggest reason I got into Obsidian daily note logging in the first place! Love your stuff!
Glad to hear! How are you finding it? And if you don't mind telling me what stuck and what didn't?
@@construct_by_dee I like it a lot! I'm using the "older" version of your system (with the inline log:: variable), so I haven't upgraded completely to use Tasks for every log.
Although I would love to upgrade, because it looks so much better.
But yeah, without your videos I've never even considered this type of daily/weekly/monthly system you have going, so I thank you for that! :)
thanks again for your effort on these and continuing to flesh out a system that works well for you in Obsidian.
i paused when you suggested at about 10:20 that the log of the [[Cafe more exploration]] #intent/to-go tag would just be removed when the place was visited. It was my intent on day of the note. then when it was visited, it will still show up as a place to go even though it was visited based on the coding. So the tag needs to go, or at least change, and that it WAS my intent on that day I still want to note. It would go away from the note listed, perhaps it would have it's own note... so perhaps #/intent/was/to-go would be appropriate?
this of course depends on ones sense of propriety about the accuracy of past daily notes. and the workflow set up around managing updates that impact how tasks and tagged items show up in MoC's and Lists.
Have you decided on a solution for this that you follow personally?
There’s definitely room for improvement and personal interpretation in my workflows, so I’m glad you noticed this small gap.
Although this issue doesn’t particularly bother me, it’s something I’ve considered in the past.
Ideally, the best solution might be to have the log checked and include the date, similar to what you'd expect from the Tasks plugin, to indicate when the "action" or "intent" was completed.
This way, you could create a Dataview to retrieve all unchecked "intent/to-go" logs and another Dataview for checked logs to see which places you actually visited, along with the "completed date."
But honestly, this problem has many potential solutions, and I’m not completely sold on any of my ideas yet.
I’d love to hear your insights!
@@construct_by_dee i think i am getting ahead of myself a little bit and need to wait for the problem to pop up before formulating a solution. i do have a hard sense that changing the daily note sometime in the future isn't a good one, as it's changing history. so completing could work and having the dataview syntax check for this and show uncompleted and completed in the same MoC note.
thanks!
I'm very interested in changing my system to your Daily Notes system. However, I do want to take notes on the go. Does this setup work well on mobile? I am trying to figure out how difficult it will be without hotkeys and on the tiny phone keyboard :\
I've been using Obsidian Sync for quite some time and it works well. That does mean that there are some cost involved which isn't ideal.
For the 'logging' I find it simple. The hashtags also auto-suggest based off of what is in your vault already.
Just remember, it doesn't need to be perfect. The only thing you need is the task box (which we use to pull the data through to the data view), the tags (which gives it context), and the note or link.