For a registration maniac like me following all your journal videos has been awesome. I've been meticuously noting everything from number of beers to the consistency of my feces (intestine problems) =D Thanks a lot!!
Such an amazingly wonderful series. Going through each part really helped me in using what I need, not including what I don't want and also learning to use the knowledge and tricks to create my own things. Thanks so much for this series.
You made a much valuable series in detail which will help all the beginners to do some advance usage of obsidian in intelligent way. Thankyou for that 😊. It will help me always.
for the yearly, it is likely possible to have the code look for the "now" date and if 2024 would use 12/31/2023 as the end of year, otherwise the last day would be the current date and the number of days possible would show a year-to-date value vs. 365, so your table calculations could be more accurate for averages. someday I will play with and will share the upgraded coding to allow for this. could make it more useful to compare how a week is vs. the yearly average, for instance to see if I am improving or regressing.
This content is a bit outdated, as I've since moved to newer and more future-proofed code in my later videos. Updating the freely downloadable "old-structure" vaults is on my to-do list. I appreciate your comments!
31:40 can we also make a inline query for that dynamic variable numberDaysdivide which output the number of daily notes that has been created yet? So that will always be dividing with the number of daily notes exist dynamically.
Thought about doing it as I was recording that bit. The variable at the top was impromptu. Originally I wanted to keep the 365, but then I wanted to do it in my personal vault. But still, need to find the time and motivation to sit down and figure it out. 😅Will create a video or reply here once I have it.
I have one thing to say. I don't know whether it is possible or not but I have read some documentation on dataview query in a dataview example vault in which in one of the example they trimmed the prefix and suffix of the note name. So can we do the same with our log query in which we trim the hashtags which render in the render of dataview query of log? And also as you are showing all the daily notes of the year. Can we just trim them all in such a way that it only shows number of the day but still open that days daily note. I think we could do it by giving alias to every daily note as the day number and then by calling day number as link may be?
Hi there Gourav! I like the way you think! I am playing around with something similar as we speak! My use case is: "log-spending:: Coffee - 10" I managed to create code in the dataview that will look for the dash in the log query and return everything to the left of the dash and everything to the right of the dash: ```dataview TABLE WITHOUT ID file.link as Date, split(log-spending, " - ")[0] as Type, split(log-spending, " - ")[1] as Amount FLATTEN log-spending WHERE contains(lower(log-spending), "-") ``` This returns a data view with one column called "Type", which has "Coffee", and another called "Amount", which has "10". This effectively breaks up the log query. And this should also do the trick for what you want.
For a registration maniac like me following all your journal videos has been awesome. I've been meticuously noting everything from number of beers to the consistency of my feces (intestine problems) =D Thanks a lot!!
Glad that my videos are helping you feel more at ease while shitting 😂😉
Such an amazingly wonderful series. Going through each part really helped me in using what I need, not including what I don't want and also learning to use the knowledge and tricks to create my own things. Thanks so much for this series.
I'm glad it helped you a little bit!
You made a much valuable series in detail which will help all the beginners to do some advance usage of obsidian in intelligent way. Thankyou for that 😊. It will help me always.
Excellent system and videos, I'll be buy you some coffee, thanks again
Thanks for the kind words! My your kin have all the carrots they desire.
for the yearly, it is likely possible to have the code look for the "now" date and if 2024 would use 12/31/2023 as the end of year, otherwise the last day would be the current date and the number of days possible would show a year-to-date value vs. 365, so your table calculations could be more accurate for averages. someday I will play with and will share the upgraded coding to allow for this. could make it more useful to compare how a week is vs. the yearly average, for instance to see if I am improving or regressing.
This content is a bit outdated, as I've since moved to newer and more future-proofed code in my later videos. Updating the freely downloadable "old-structure" vaults is on my to-do list.
I appreciate your comments!
31:40 can we also make a inline query for that dynamic variable numberDaysdivide which output the number of daily notes that has been created yet? So that will always be dividing with the number of daily notes exist dynamically.
Thought about doing it as I was recording that bit. The variable at the top was impromptu. Originally I wanted to keep the 365, but then I wanted to do it in my personal vault. But still, need to find the time and motivation to sit down and figure it out. 😅Will create a video or reply here once I have it.
@@construct_by_dee yes sure🥳
I have one thing to say. I don't know whether it is possible or not but I have read some documentation on dataview query in a dataview example vault in which in one of the example they trimmed the prefix and suffix of the note name. So can we do the same with our log query in which we trim the hashtags which render in the render of dataview query of log?
And also as you are showing all the daily notes of the year. Can we just trim them all in such a way that it only shows number of the day but still open that days daily note. I think we could do it by giving alias to every daily note as the day number and then by calling day number as link may be?
Hi there Gourav! I like the way you think! I am playing around with something similar as we speak!
My use case is:
"log-spending:: Coffee - 10"
I managed to create code in the dataview that will look for the dash in the log query and return everything to the left of the dash and everything to the right of the dash:
```dataview
TABLE WITHOUT ID file.link as Date, split(log-spending, " - ")[0] as Type, split(log-spending, " - ")[1] as Amount
FLATTEN log-spending
WHERE contains(lower(log-spending), "-")
```
This returns a data view with one column called "Type", which has "Coffee", and another called "Amount", which has "10". This effectively breaks up the log query. And this should also do the trick for what you want.
@@construct_by_dee oh this is nice way. I will try it and let you know if found any confusion. Thanks 😊