Oh wow! This Quadro
is really interesting! I think I’m probably going to end up working this or something like it into my workflows, so thank you for sharing!
Sorry for the delay. Life got in the way. Hopefully, Quadro
turns out to be your solution .
So as I said before, I feel it’s hard to grok the situation and your preferences in text so that I can provide useful feedback, but I was trying. In the end, I decided to just give my use-case as an example, though some of it may or may not work for you, and so I went back and forth on if it was constructive.
Just in case it’s helpful here’s that long update I only just finished editing to post:
Personally, I subscribe to a let the best parts rise to the top approach, so if we’re thinking the same thing, I endorse that strategy.
I don’t worry too much about the input method as long as things end in text.
Here are some strategies that I use that I found helpful reprocessing my own vault:
Since I first started writing this note, my vault got to a point of maturity/stability where I just felt 2.0
was redundant because the system really worked. I decided I could just move all the directories out of 2.0
into my vault’s root directory and delete the now empty and superfluous 2.0
. There are still a bunch of notes in 1.0
, but that directory is dwindling every day. Some week soon, it’ll be gone, and all my vault will feel in a much less “scrambled” state.
There are other things I have been doing, but I feel this strategy with normal tag connections, dataview, and wikilinks creates a lot of the relational data map without index notes or properties, etc. Keeping it simple has been key to this process’s success. I think it can be applied to your desperate note types. It also breaks the whole process down to basically:
- Rebuilding the file structure off of what you’ve learned, but without the clutter of the old one because it’s hidden away
- Adding tags at the top of a page (I have a line under the H1 and will just turn important words into tags in line).
- Following a maturity grade. It gamifies things a bit and makes the vault less scrambled.
If this is helpful at all, please let me know. I am working on a basically fool proof backup strategy that I’d be happy to share as well (since you mentioned that in your original edit), but I feel your current 1 note with a printout strategy would be untenable in the long run as the vault grows. For me, my vault has become enormous and I need to remain agile with it and every day I revisit ideas and improve things, as is the Zettelkasten way.