filetags VS org-transclusion

For my personal tool-set, I've settled for "everything in the file name" because in my experience, this ensures that no meta-data gets lost when moving paths, on thumb drives with ancient file systems, OS-borders and so forth (https://github.com/novoid/filetags + other tools + https://karl-voit.at/managing-digital-photographs/ as an overview).

Technically, it makes use of filename-based time-stamps and tags by the "filetags"-method which also includes the rather unique TagTrees feature as one particular retrieval method.

What do you mean by filetags? This?

I don't know if this is perfect but for me, this method with its tools is working pretty great since a decade or so: Managing Digital Files (e.g., Photographs) in Files and Folders using filetags (all sorts of things related to tags), guess-filename (generates most file names for me), guess-target-folder and move2archive (moving files to their destination) + some more tools I wrote.

filetags and companions

filetags and its companion tools is a direct result of my PhD projects with tagstore. For the basic concept of filetags, I worked with file tagging methods for at least six years.

I've always thought that personal files, photos, or any other kind of just needed more connections between them to improve my information retrieval experience. That's how I had become a Zettelkasten evangelist. I believed it would be the cure for the information overload disease of our era.

But life made me use Emacs org-mode more and more, and I'm now in love with tags. Retrieving information has become so easy, especially with org-mode's tags inheritance, that I hardly think making connections between headings or notes is necessary anymore[1]. And I believe that applying tags to filenames (a la Karl Voit [2]) will create the same effect

[1] A Zettelkasten-like system is still unbeatable imo when it comes to ideas repositories, i.e. a second brain you can talk to and get new insights. It's just not that great for personal knowledge management or project management.

[2] https://github.com/novoid/filetags

Technically, it makes use of filename-based time-stamps and tags by the "filetags"-method which also includes the rather unique TagTrees feature as one particular retrieval method.

nobiot/org-transclusion: Emacs package to enable transclusion with Org Mode

There is nobiot/org-transclusion, but i haven't tried it personally.

This is it: https://github.com/nobiot/org-transclusion

As wWA5R... already noted, you can structure large org files with headings and subheadings, where each heading can be handled as an own note. But addtionally, you can export org files a html document or as latex document. There exists also a emacs package which is called transclution (https://nobiot.github.io/org-transclusion/) which makes it possible to construct a new org file out of snipped of other org files. So you can create a new document by combining several peace of other documents. The package/project HyperOrg I didn't know, this seems really interesting for publish the whole org-roam data (thanks a lot for mentioning it @wWA5R...!).

Since I started Uni, I've taken my notes in separate .org files, one per subject. This is ok, but it doesn't allow me to link concepts across subjects. At the same time, I don't think graphs are easy to navigate linearly, which is something I need for revision. I wish to be able to, when necessary, read all nodes in a single file, either by exporting the nodes or by having them all in one file to begin with. Reading the documentation, I haven't seen how to do it. I considered using packages like org-transclusion but I don't think that's the most efficient way. Does anybody know of a configuration to use or have any suggestions?

I found out about org-transclusion and hacked together something that works (feedback is more than welcome).

After finding out about org-transclusion I hacked up the following. As I'm not very experienced with elisp/orgmode/org-roam I'd love some feedback. I'm particularly interested in shortening the code by using more built-in/standard functions.

If I'm understanding your use-case correctly, I think you should look at org-transclusion