Explain the problem as you see it
Changes made to how the #day node is structured apply to all past nodes.
Why is this a problem for you?
Because it discourages changes to the #day node, out of fear that it will "disfigure" my past #day nodes.
In Bullet Journaling, there's this idea that the journaling process is intended to "remember the past, organize the present, and plan the future". Not everyone uses Tana similarly to how one would use a Bullet Journal, but I think we can agree the #day node fundamentally serves a journaling purpose.
In journaling, the structure is often as important as the content: today, I'm primarily focused on using Tana as a work tool in my job, so my #day structure (the collection and ordering of the fields I use) reflects that; in the future, I might instead be more interested in using Tana for a different purpose, and my #day structure should reflect that. However, any changes made then will retroactively impact and disfigure all my #day nodes, impairing my ability to look back and properly "remember the past".
Suggest a solution
As each day goes by, #day nodes for dates in the past should have their field structure preserved, as well as the content.
Of course, it should always be possible to delete and edit nodes, and references should update normally. But if I use a "Weight" field to track weight loss daily for a month, for example, in the future I should still be able to go back in time and see that field, even if by that time it's not part of my #day node anymore.
2 Comments
@Fabio Bracht But isn't it working like that already?
Hi I am also using Tana for bullet journaling.Please have a look at my today's suggested idea(s):
https://ideas.tana.inc/posts/290-incorporate-these-4-concepts-from-the-twos-app-bullet-journal-related