Explain the problem as you see it
Currently, the only way to find a date is to specify it exactly.
Sometimes I'd like the option to generically mention a more 'generic date'. For example:
- Thursday - and this would refer to ALL Thursdays, not just one particular Thursday
- January - and this would refer to ALL Januarys, not just this year's
- Quarter 1 - and this would refer to ALL Quarter 1s of all years
- Week 52 - and this would refer to ALL Week 52s of all years
- 15th - and this would refer to 15ths of ALL months
Why is this a problem for you?
When I want to create a recurring date, this becomes a problem.
For example, if my pay-day is on the 15th of each month, I want to be able to specify exactly that.
When I type:
- payday @Every 15th
I would want this node to appear everytime on the daily note node under References. This would serve as a reminder for me to work on that node.
==
Or another example, if I gym on Mon/Thu/Sats, then I want my node to surface on these days. When I type:
- gym record @Every Mon @Every Thu @Every Sat
I would want this node to appear everytime on a Mon/Thu/Sat under References. Likewise, this would serve as a reminder for me that such a node already exists and I do not create a duplicate, neither do I need to go hunting for the node and thinking about what I named it.
==
Another example, if I want to do a monthly review, then I want my node to surface on the 31st of every month. When I type:
- monthly review @Every 31st
I want to be able to see what I had written in the previous month in one go. This referencing allows me to have continuity to "build and accumulate things over time". This makes compounding nodes much easier.
====
Yet another benefit that would arise from generic date references is that when you visit the node itself - that's when the magic happens. It would serve as a 'container' to house all the different reviews you've made over time (especially if I used contextual nodes). I would be able to see trends over time, how things changed, or whether there are any patterns over time.
I believe whenever a system is amassed with a large amount of data, there always needs to be some form of clustering - and generic dates can do what specific dates cannot do - they can clarify patterns over time.
I can already think of many ways to use this - for example, if I filtered the different week days vs energy levels, I would be able to see which days I am more energised and see a pattern over time. Or I can see what my spending habits are like.
At the same time, this would easily work for any kind of recurring date, if you could at the same time, specify the Start and End date as a date range (which is already possible in Tana).
Suggest a solution
Would love generic date specifiers.