Folders V.S. MOC's & Emergent Structure In Obsidian: How I Approach Taxonomy

[tallguyjenks]

As I can see your Obsidian screen with the looong list of filenames, I realize I always used a completely different approach when trying to organize everything into structured directories.
So, you don't believe (or find useful) in organizing files in folders?

Everything depends on context, intention, and desired outcome.

My vault is meant to be primarily a zettelkasten that uses influences from Evergreen notes. Because of the search capability in Obsidian, the way files are linked, and the organization uses MOC's not a rigid nested folder hierarchy, I find it more effective to not use folders in this instance. I instead prefer the emergent structure to the frontloaded rigid taxonomy of folders and making everything fit into folders even when it's a square peg to round hole type of scenario.

---

Regarding the organization/Taxonomy of notes

A Nested folder hierarchy is like a collection of umbrellas under umbrellas etc. in regards to their granularity everything under 15th century Christianity is also under the umbrellas of Christianity, is also under western religions and .... etc. Where everything is hidden and completely absorbed by the increasing scope of the topic (the larger parent umbrellas).

Index
└── Religions
    ├── Eastern
    └── Western
        └── Christianity
            └── 1500s

In contrast to MOC's where the structure is akin to a neuron or tree roots where you may have the taproot (index) but the roots branch off, again and again, reaching out into more granular topics but everything about those topics is not contained under an umbrella, or connected to that piece of root. rather something may connect to that root and that item connects to the other items. This loose association requires less cognitive load to manage but also allows not only a more organic emergence of structure but also a more organic formation of our interconnected knowledge...

[tallguyjenks]

Converted from issue