My JD setup (so far...)

I started my JD journey last year but didn’t follow through and finish nor create the index/JDex structure. I think I finally have figured it out, and wanted to share my setup.

I’m using Obsidian for notes and the index. Part of my hesitation has been wrapping my head around the structure, where to use folders, where my notes fit in with the index etc. I think I have clarity now for my own use cases.

Folders

I’m using a semi-flat structure as follows, in one Obsidian vault.

  • One _JD folder which is a list of folders at the AC level. I was getting annoyed with a more hierarchical structure of nested folders, but also did not want a folder just full of ID notes either. This is my happy medium. 3 areas - one personal, one business, one for a relative I’m power of attorney for.
  • “Obsidian” specific functionality in their own folders outside of JD: attachments, templates, and daily notes.
  • The “notes (other)” is where I am taking a slight departure from the norm. More on this below.
  • The “notes to be filed” are all the Obsidian content I’ve had that I have not organized or linked to indexes yet, UGH, lol.

00.00 System Index file

I’m using dataview queries to have 3 separate queries showing the indexes within each “area”. I could just have them all in one list but this is where I preferred to display them by area. Properties for this index are just a “category” and “subcategory”. I’m using “category” generically in this context, using an out of the box property instead of creating a new one for JD. I labelled all of my .00 to .09 notes with a subcategory of “Standard Zeros” only so I can filter them out of the views in my queries. In the screenshot for example, I don’t need to see the standard zeros in each area, I know they exist, I only want to see the OTHER IDs.

My query is the same for each except a hard coded path because I could not figure out a cleaner way to do this. (dataview query)

table category as Category, created as Created
where category
	  and contains(file.path, "_JD/1")
	  and subcategory != "Standard Zeros"
sort  file.link

I do something similar on my area indexes (10.00, 20.00, 90.00) and category indexes (11.00, 12.00 etc.). These 2 screenshots are perhaps not a great example since I haven’t yet organized my “JMK” files and don’t have much in them yet.

Into the weeds

Lastly here is an example of what I’m doing at a more granular level. An example of one AC is below. Orange icons for indexes, green icons for headers.

This isn’t pretty but it’s an example of a header. I have a dv query to show all notes linked to this 91.20 header. I can’t figure out how to get it sorting properly but that’s a problem for another day! I’m just cleaning up notes so the naming convention leaves a lot to be desired here. Some are ID notes AC.ID format, and some are/will be “note notes” in the “notes other” folder, like the bottom one in the screenshot.

And this is what an ID note might look like when it has other notes related to it, plus what I settled on for properties which will be on all of my notes. In this example it is a scenario where I’m tracking a lot of info about doctor’s visits for the family member and don’t want one gigantic note so I will have (when I’m done) a bunch of “daily notes” wiht links to this note, some other notes with links back to this for medical history etc. I will follow the same logic for my consulting business client notes because I take notes every day as I work on things and it’s too much for containing in one big note.

I know seeing other people’s setup helped me so I am sharing this hoping it helps some others out there with ideas on how they might do things.

3 Likes

Thanks for the detailed tour!

This is officially condoned! It would be silly to postpone using the new system until you’ve indexed everything from ages past. Feel free to leave stuff in there unsorted, forever, if it doesn’t bother.

1 Like

I used to be really anal about having everything sorted, to the point of obsession.

But then I read this:

Searching for something you didn’t sort is inefficient. But sorting something you’ll never search for is a complete waste of time

Completely changed my attitude and freed me up.

3 Likes

I’m taking that and adding it to my Index at the top. Thanks.

1 Like

Your Index looks good. It’s a different layout than mine but I see the vision. We all have to make it our own.

1 Like

I’ve changed my mind on a few things since I documented some of this in my original post above. I realized I was duplicating functionality tht already exists in Obsidian by having some queries in places where Backlinks already would show it if I had it turned on.

My 00.00 index is now one Dataview query

My code (filtering to just my folder “_JD” where all of my IDs are). I changed my mind on hiding the standard zeros so now this is one grouped query with it all indexes, not the notes related to the indexes though.

I am grouping by property subcategory which is a short phrase for each of my ACs. It was too complicated to try to group by the prefix of a given folder or filename so I am just explicitly putting it a property now to make queries easier.

table without ID subcategory, sort(rows.file.link) as index
where contains(file.path, "_JD")
group by subcategory

What this looks like for me:

No more “Linked Notes” query needed

I realized I was using a dataview query where out of the box functionality already existed. On headers for example, I want to see the notes linked to that, and the core plugin Backlinks already does that if you turn on Show Backlinks at the bottom of notes.

Example: header 91.20 Medical Records for the relative I’m power of attorney for: Linked mentions already shows all the IDs related to this header (and it would show notes if any were related). The note itself is empty so just the Linked mentions footer appears.

Example 2: a “regular” ID where I have multiple notes related to it instead of a giant note, I’m using the Related to link and this shows me all the dates where there is a daily note for this relative. I create a new separate daily note for their care if/when somethig notable comes up. I used to have one gigantic note that was too big to find anything in. Now I have a format for it, a template, and can see patterns in their health etc., by seeing the dates of various occurrences of things.

1 Like

Any distinct reasons for using data view queries instead of Obsidian bases?

1 Like

I am trying bases in some places, but I haven’t figured out a way to display it nicely.

For that JD index example, this is the “same” code in bases as the code above in dataview: filter to the folder that contains my indexes (“contains _JD”) and group by subcategory, this is what it looks like:

I just don’t love the grouped field as a bar, that it includes the field name being grouped (I just want the category value, I don’t want/need to see “subcategory” each time). I like the cleanliness of the dataview result above. If that is possible on bases, I would switch but I haven’t figured that out yet and hoping it is possible or that it gets there. Until then some queries will be in dataview for me.

I intentionally put subcategory in as a visible property because without that, the name is directly under the group name and it looks even worse IMHO.

(List view instead of Table view in bases is slightly better but still not as nice looking to me.

The bases view looks good to me. Yes, List view would be an alternative.
I’m starting fresh with JD.
Where can I read about your obsidian implementation of JD.

All I’ve posted about mine is above in this post.