Templates in Flat, Default or Deeply Nested JDex

New JD adoptee here. Just starting to reorganize my life using this system, and I’m trying to figure out which JDex nesting structure will work best for me in Obsidian. I followed the standard advice, and downloaded a partially nested JDex. I also downloaded the flat structure and the deeply nested structure to compare between the three versions. I have possibly two questions.

I’m struggling to understand why the partially nested JDex does not include the Holiday Template or Work trip template ID’s. Both of the category heading (15.50) reference the same link, but it seems that only the flat JDex structure is ‘up to date’. Is this correct? Or am I missing something? In general it seems that the flat structure JDex is up to date, while the partially nested structure is not.

The second question is how I would replicate the work or holiday template in the flat template in the partially nested template. It seems that I should create a folder to house the template, but Obsidian automatically sorts the folders to be above the the markdown ID’s, which bugs me. Any suggestions?

So there’s a subtle difference between the JDex and the folder structure that is revealed by these two types of download. Both of which are specific/peculiar to Obsidian. You’re forgiven for being confused![1]

‘Partially nested’

Let’s look at the partially nested structure first. Here it is with everything except these IDs of interest deleted.

The first folder (red) is the one you should drag to your Documents folder. It’s where your files go. It has the folder templates which you’ll duplicate each time you need them.

Note that these subfolder templates are not a Johnny.Decimal ID in their own right. They’re subfolders within 15.50.

The second folder (green) is the one you’ll open in Obsidian. It only contains the Markdown file for the ID 15.50 for this same reason: the subfolder templates aren’t an ID. They’re just subfolders within an ID.

‘Flat’

The flat structure just has this second set of (green) files – the Markdown files for your JDex – in a different place. Rather than being in their own folder structure, they’re all at 00.00. But other than that, they’re the same.

And so here, also, there’s no Markdown-file-representing-JDex-entry for the template folders. Only for 15.50.

Did that make sense? So these templates are only folders. They aren’t JDex entries, and so Obsidian has no need of them.


  1. And this is why I recommend Bear for beginners who use a Mac. This confusion just doesn’t exist there. ↩︎

1 Like

Sorry for the late response, and thank you for the explanation, it makes way more sense now! It also took me a moment to fully understand what you were showing because of two things:

  1. I was using an old version of the LAS system (I think it was 1.10 or so, but I deleted the note associated with the versioning, so I’m not sure anymore lol).
  2. The older version of LAS I was previously using that I downloaded from your website, was configured (or maybe I configured it???) to use the Folder Notes community plugin from Obsidian.

I was very confused because in the older version of the LAS, the organization was substantially different (think different set of ID’s, slightly different names for categories and areas, etc.). It looks like in the newer version of the LAS you streamlined the descriptions of the categories, whereas in the older version of the LAS you tended to leave in more description in the note itself. Also in the newer version you directly linked to the online JDHQ website that includes descriptions of the ID, category, and area.

In addition, I realize that the Folder Notes was contributing to my confusion, because I had the plugin installed on my main machine, but not on my phone (I use Obsidian sync to keep them synchronized with each other). So I was a more ‘nested’ version of everything on my phone, where the plugin was not showing the folders as notes. In general, I realized that the use of the Folder Notes plugin has nothing to with your ‘partially nested’ or ‘flat’ folder structure.

I remember some post/conversation you had in the past regarding using Obsidian for everything (considering at some simplified level, it’s just folders and markdown files for the most part). I think you had tried that out, and found it wasn’t the best idea. I would also agree, my reason being that the main worry is that Obsidian can eventually get slow with too many folders/notes/files. Especially considering that I like the Obsidian sync functionality, and paid or free, there is a limit on how much you can store and sync through function. I’m sure it could be optimized through careful exclusion of files from sync’ing, but that sounds like too much effort for me.

However, all that being said, I’m in the process of converting my JDex ID’s into folders for two reasons:

  1. For creating a catalog, or reference of entities, I don’t always have proof for them. Think old receipts that I definitely threw away.
  2. Obsidian links are cool. I can create markdown files inside the ID’s, for example in 14.12 My mobile devices and link to something like another note for example in 12.16 Appliances, tools, & gadgets, to reference a repair I made to the machine, and more information about the repair activity there.

I think I plan on minimizing what I put into the Obsidian folders, to just markdown files, and referencing the location of other documents related to that note. For example in 14.12 My mobile devices I could have a note like Tablets, and in that note write some information about the iPad I have, the version it is, important activities on it, and links to repair activities.

I suppose the alternative would be to simply write in the un-folderized Obsidian note, all this information, but I suppose the note could become rather long over time. All this being said, I’m not completely convinced using notes as folders in Obsidian is the best idea. But it is nice for the category folders to be notes, because I can at least store the description of the category there.

I can include some pictures if that helps :-). Anyways, some food for thought. And by the way, do you have a more detailed versioning catalog for the LAS? It would help me understand some of the changes that were made over time to the organization of everything.

Yep, we ‘moved’ the descriptive text from your JDex to JDHQ. This lets us update it much more easily … there are pros/cons to this and I’m still not sure which side I fall on. I should probably just make that an option if you want to download the full text.

Of course! JDHQ > Support > Version.

The biggest structural change was moving around the headers in 13 so that they match SBS, which matches the standard accounting flow.