Hello FDSC
1. What PKM system do YOU use?
I don’t use a specific PKM.
Requirements and preferences change with time therefore my system as well. No big breaks but “seamless” changes. That’s the theory. In practice it is always more or less messy, but that’s fine for me.
The real challenge in my non-system system is to keep control. Therefore I have some more or (mostly) less clear rules for my orientation.
For example, maybe the most important guideline, I have two kind of files: “Content-Files” and “Management-Files”. In theory no mix! In practice, the exception proves the rule.
Another guideline is the idea of an “autonomous” (NOT atomic) file. A file should contain within itself all infos about itself, which are necessary to manage the file, no matter how I manage my system, today this way, tomorrow maybe upside down Today with Obsidian, tomorrow who knows?
The basic tool I use are “file-stamps” in the file name. Basically these “file-stamps” have the same function as folders.
There are different categories of stamps.
- Function Stamps for files with a specific meaning for the management of my system, e.g. “°bundle” ( basically MOCs) or “°list” (just lists for this and that) …
- Content Stamps for files with a specific content , e. g. “°book”, “°glossary”, …
- Topic Stamps like “°obs” (Obsidian), “°lnx” (Linux) …
- …
For the fine-tuning I use nested-tags.
2. For what purpose and in what context?
I want a specific information, I want it quick, I want it now. Therefore I navigate with the “file switcher” to get direct or at least as near as possible to my target.
If I look for a book about GIT, the query “git °book” will do the job.
If I have some trouble with my Linux System, the query “setup °lnx °bundle” shows me the file where all files for this topic are listed. Same e. g. for Obsidian “setup °obs °bundle”.
Has the forEach-loop a return value? “forEach °js” will (mostly) not answer my question but the link inside will do it.
Most stuff I deal with has a (let’s say) “intrinsic” structure. If you are familiar with it, the orientation is not really hard.
3. For what reasons did you settle with it?
4. What works well for you? What doesn’t?
I started with the file-stamps maybe two years ago. Ten at most - I said. Today I have around 80 and it works better than I ever had hoped.
The fine-tuning with nested-tags is … To be honest, it doesn’t work as I wish. I have to find a better way and I think it will be just tags, no nesting.
I am a little scared of “just” tags because mostly it ends in in a heap of tag-garbage. As I said, if I look for something, I don’t want to be inspired, I just want an answer.
A summary in one two sentences: I want a system which is as simple as possible because of all the future changes, where from I don’t have any idea, except that they will come. On the other hand it has to work the way I need it today - and tomorrow.