use of project zettelkasten
Table of Contents
1. For specific project
obviously.
For example, I have a robotics course in which I’m instructed to implement a robot controller(which as of now Tue Jan 9 01:57:25 2024 is 2 hour overdue), I get a lot of ideas and informations with lots of details that only make sense to this project, and I want to use zettelkasten to manage them, ’cause that would improve my mental health so much.
However, the size of nodes and text is very heavy, including lots of designs, logics that I don’t think would matter much in the long run, hence it would not be appropriate to have them scattered into my main zettelkasten.
2. For experiments
When I want to do some experiment on the note taking system, such as switch to one-giant-file instead of one-node-per-file mode, use org-id-get-create instead of org-roam-node-find to create node, use Luhmann Id, etc.
3. For privacy levels
There’d be some private information I’d like to record with zettelkasten, but don’t want them to be published publicly, such as accounts, financial info, notes on aniversaries, on friends and family, health condition, private memory, etc. It make sense that one would one to management with a Zettelkasten.
in org-roam, Draft tag is a means to the problem, but have them in a seperate notebase is obviously easier, clear and more fault-proof.
Backlinks
In the old days this is the main way to go: to have a zettelkasten for each project, and according to wikipedia. Nowadays software make a lifelong main zettelkasten not as enormous, space consuming and labour heavy as they used to be, but project zettelkasten is still good practice.
- setting up multiple org-roam notebases