Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
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?
Using org, I'm naturally drawn to org-roam, however, I dislike the bulk of dependencies and its complexity stemming. Furthermore, I dislike, that I can't get a textual overview of a subset of notes belonging together (using a webserver-solution like org-roam-ui is not what I want here). Looking at the new zk-package, I want to note that I like its simple and clean approach, but I dislike, certain design decisions, like using spaces in file names and the fact, that it doesn't integrate deeply in the org-ecosystem, e.g. not utilizizing org-IDs. The last point is the biggest downside imho. While one could hack on the codebase to change this, another drawback seems to be that it is not really mature and doesn't seem to have a large userbase.
Honestly I've been in the same boat as you for ages and have even tried writing my own zettelkasten packages here and there on top of things like deft (I started with zetteldeft, which shows).
Honestly I've been in the same boat as you for ages and have even tried writing my own zettelkasten packages here and there on top of things like deft (I started with zetteldeft, which shows).
I tried to do this on top of deft, but unfortunately deft is designed as a user-focused package and can't be reasonably used as a library. I tried, mind you (warning: this package is very broken and hacky), but even if I had gotten that to work I think I would end up wanting a richer index and pre-processing of input data (when entered into the zettelkasten index, I should be able to parse out all forward-links for example, and store them separately so they're searchable without a regex over full-text).
I think you might be looking for delve. It allows to create collections of notes and operate on them.
zk does seem to be a consistent approach with clever design decisions. Future proofness depends on two factors here I guess: the data collected and the tools support for making use of those links. In Orgdown, access to data and being able to read it is never the issue. Tool-wise, zk uses standard Org-mode features as much as it can. So I'd say you're good to go with that approach.
I'm currently not using any tool, although I am playing around with binding Milli and the most up-to-date Mentat fork to emacs with emacs-module-rs.
I'm currently not using any tool, although I am playing around with binding Milli and the most up-to-date Mentat fork to emacs with emacs-module-rs.
I'm currently not using any tool, although I am playing around with binding Milli and the most up-to-date Mentat fork to emacs with emacs-module-rs.