OBSIDIAN and BEAR

Hi Folks

The big problem I am encountering is how to actually use Obsidian to implement the JD system using the note for each ID.

I am ok to just copy Johnny Decimal on my mac for my life admin, listen to him, but I have to implement a standard file structure at work and at work they only use windows machines.

Obsidian is quite the beast. Can anyone recommend a great website or you tube video of how to use modern JDEX on an Obsidian system?

Currently Bear has already a beta test for Bear web running. I really like the web version and itsā€™s already very capable.

You can try to join the test here: [Tester wanted!] Bear Web Beta update - #437 by whschreiber - Announcement - Bear Community

Maybe the web version will be sufficient for you.

Weā€™re hoping to do lots of Obsidian starter-level stuff to accompany the small business system, and itā€™ll all be public on YouTube. But no time in the immediate future, sorry.

My tips for Obsidian use:

  1. Forget that plugins exist. For now, just use it out-of-the-box.
  2. Forget the graph. Donā€™t need it.
  3. Lean heavily on Markdown. Learn it well. Specifically [[wiki-links]].

Structurally, Obsidian is identical to Bear. Left pane(s) = list of all your notes. Middle pane = the text. Right pane = optional more information, but you never need to open that.

Just start real simple and gradually introduce yourself to new features as you think you might need them.

2 Likes

Agreed with Johnny. Keep it simple, so when Obsidian or Bear or whatever app dies, you just spin up the next app with your original files.

My workflow in Obsidian is pretty straight forward:

  1. I take a daily note. The daily note has headings. Each heading is a title of what Iā€™m doing for that chunk of time during my day, followed by a [[XX.XX]] wiki-link to my JD ID note that the work Iā€™m note taking about pertains to. This way I can go to my JD ID note and have a chronological list of work done for/in an ID.
  2. Inside each of my JD ID notes I have headings for broad themes of whatā€™s happening in that ID, this can then link to important daily notes/literature quotes so I can see the source of where a conclusion or question comes from.
  3. Whenever an idea surprises me I tag it with the causal and resulting concepts, for example [[playfulness]] causes [[strength]] in line while Iā€™m writing notes (a real example from my recent reading of Jane McGonigalā€™s Superbetter).
  4. Tags are for reversible statuses only (e.g. Active Project, Waiting For Task, Things I want to do in 2025). This way when I remove a tag from a note or line of text, it doesnā€™t lose meaning, just stops being searchable from the tag search.

The resulting file structure based on alphabetical sorting really looks like a notebook.

I have my JDEX at the top of my files 00-49 is all I use for my system, 202X-MM-DD daily notes automatically sort down below my JDEX note files, and way down below I have a growing list of words like ā€œplayfulnessā€ and ā€œstrengthā€ sorting alphabetically, as if Iā€™m assembling an appendix on auto-pilot.

1 Like

To further emphasize the point of sticking to the basics, @clappingcactusā€™s four points are pretty much what I do currently in a bare text editor[1]. A workflow/format like this is the essence. Obsidian provides the automatic linking and backlinks, which makes navigating fast, but the information is all there in the plain text. Currently, I have to do quite a bit of manual lookup to resolve those links, but it is doable. So I would second the suggestion to avoid plugins and focus on getting a workflow working with the basics first.

I also tend to agree with point 4 about how to use ā€˜tagsā€™. I think of them like literal ā€˜sticky notesā€™ that you put on something so you donā€™t forget it, until theyā€™re no longer needed. Point being: good (markdown) titles and links deliver more value.

off-topic @clappingcactus: so you are using a flat structure? I thought I caught that in this recent post.


  1. except point 3, which inspires me. Maybe using a format like this will help me find notes and ideas again better. ā†©ļøŽ

The causal-resulting relationship is now the cornerstone of how I read/write anything. Well ā€¦ maybe not spammy long posts on the JD forums, but you know. It helps me see when a text is circling an idea without really knowing how to formulate it, and helps me realize that I have the wrong argumentation structure in my writing.

Yes, I have now gone and adopted a full flat structure for both my JD and my notes.

The thinking on that was moving away from a filesystem-first mentality. I am a single human, Iā€™m working with a set of concepts that build my life up. One of those concepts happens to be my mental organizational ability, and that happens to coincide with my ability to save things to a computer, but those two things are not the same. My file system now actually exists as 23.22 in my system. Just like I happen to have 37.16 an online backup system that has my JD system in it, or 31.25 my notebook that I carry with me. It so happens that my computer file system reflects the structure of my JDEX and can store a lot of files for it, but it is not the system itself, so I see no reason to have it nested. I now regularly cull folders from my file-system when I donā€™t need them, because the real work happens at the Index level after all.

Sorry for derailing the thread. Iā€™ll continue this elsewhere @clappingcactus ā€“ great stuff and I feel a new topic brewing. :ok_hand:

@kelso, are the tips above getting to your questions? It also seems like youā€™re wrestling with limitations on Windows machines at work. Are you hoping Obsidian will provide a cross-platform place to keep things structured the way you want?

To bring the thread back on point, Iā€™d like to mention that Iā€™m using this system not because Iā€™m afraid of complexity but because Iā€™m past the point of complexity and Iā€™ve realized all other note taking styles can be formatted to be compatible with this one.

Itā€™s not that Iā€™m afraid of plugins, itā€™s that Iā€™ve used them, thought I can replicate their benefits more simply, and then gone ahead and arrived at the ā€œbasicā€ system above.

Open for questions re: the original topic of course. :smiley: Sorry for derailing haha.

Yes, this formulates my point a lot better than I did originally. The text files I work with ā€˜by handā€™ could be imported almost as-is into Obsidian and Obsidianā€™s automagic (back)linking would pick them up and just work. Obsidian would provide speedup and itā€™s only my own stubbornness keeping me from using it and following links with grep instead; but the point is that the real power is in the format, and then maybe in the ergonomics of being able to follow links easily; and all the plugins beyond that are, indeed, either just extras or for very specific use-cases.