zk VS Dotfiles

Hey there, here's some packages that might help you: - Org Roam - Denote - Zk

The citar package, which I created, has note integration packages available for both org-roam and denote (along with zk).

You could try denote as some others suggest. I found this, which takes inspiration from zettelkasten like roam but uses plain text and no database, https://github.com/localauthor/zk

You might try zk. I think it checks most of those boxes. https://github.com/localauthor/zk

Thanks for the links. A lot of ideas are very relatable and I agree, that the Zettelkasten might not fit the general note taking needs. As I pointed out, I am specifically interested in utilizing the zettelkasten-method in a research-workflow aiming to assist (and track) a structured cognition process. However, tools like org-roam and delve (which I recently checked out) introduce a certain degree of complexity to the system -- especially if you want to understand the technicalities of the utilized solution. Therefore, I'm very much intrigued by zk, developed by /u/oldjawbone recently. Asking you as the die hard PIM-enthusiast who you certainly are: What is your opinion on zk's general design decisions? Do you think it is reasonably future-proof,/u/publicvoit?

Located here: https://github.com/localauthor/zk

For describing my workflow very briefly (not as well as Sonke Ahrens in the aforementioned book, but I will try), I try to follow the main points of Zettelkasten. Whenever you learn something, take notes about it. Make the notes brief, but very descriptive. Give it a large title describing everything contained in it so you can find it easier later. If its too large, split it into multiple files, so the note is atomic (meaning it can no longer be separated into multiple files). If you don't have time to write a note correctly, make a fleeting note about it to remind you and write it later. Densely link your notes with one another. Thinking about the connections between notes is sometimes half the work of writing it. This way, I never lose information. If I need something later down the line, I can always search with org-roam-node-find, as I use very descriptive titles as I mentioned. If not, there is also grep, which if you are not aware is a text editing utility that allows for searching all your notes. There are many grep tools in Emacs (i.e. counsel-rg being the one I use personally). For more explanation, you can check my literate org-mode config.

There is definitely a way to do this in Citar which should be mentioned in the wiki if you read through it (and if there is not the author of the package is very helpful in general) but I do not know what that is. This way, when you select a bibtex entry it will automatically create a note with the title being the title of the article, automatically associate the entry with its pdf and ready org-noter for use to annotate it. Its a very streamlined and automated way to work with this system of packages that I highly recommend. For more info on this, you can also look at my literate config for notetaking which naturally has a lot as I take tons of notes. Link to it is here.

For more info on my workflow, you can check my config over on github. This part is specific to my org roam, references and general note taking workflow, so you won't have to look for the relevant parts. Its a literate config and I explain some things more than I do here. If this all interests you I suggest giving it a check. I also couldn't recommend Ahrens' book more. Its an incredible read for academics of every science as its really applicable everywhere imo.

Also if something is not clear here you can check out my full i3 config over on github.