![]() org-attach and links and dired to craft small "secondary-level file hierarchies" as a storage management layers, something that hide my real home taxonomy (essentially just notes on one root, other files managed by org-attach under another in a cache-like tree) I access via links Sometimes I need queries to work on things, like "check all active contracts" or "current issue" or "last three days notes" etc In 99% of the case I get "the good answer" (something already done or new content to add), sometimes I need rg/recoll because just heading/tags search do not work and in that case I adjust/add some roam_aliases to easy mach the content in the future. org-roam, org-ql (with a semi-curated catalog to make queries and yasnippets to ensure consistency) and ripgrep as access layer, witch practically means hitting a single key on my keyboard and start typing something. Given the above two consideration I decide for myself to org-attach almost anything. The fact we have many file formats and apps just to craft document is more a limit and an issue of modern systems that a reasonable thing. notes are another interesting things: ALL documents are kind of notes. Essentially a path in a file&folder classic taxonomy is a kind of limited and limited query to reach some content Sometimes a file should be in more than one place, there are links/symlinks but no "backlinks" so it's easy top break things and filenames are not much good for search. Personally, and I can't name a tool for you, I consider that:
0 Comments
Leave a Reply. |