Forum Johnny.Decimal forum

Haha yes, I get that It is the burden of tool creators But with the use of your MCP, it’s a breath to reconfigure for my needs ! Thanks for that !

Folder Notes should be a supported config – just haven’t got round to adding it yet. I use FN myself extensively. Honestly, at this point, I think I’ve switched my efforts to a ‘proper’ Mac app, built in Swift. I was spending so much time trying to make Obsidian: Be a database. Be a JDex app. It’s neither of those things, and as soon as you try to rigorously parse Markdown files as if it were, you find yourself banging your head against the wall. There are too many exceptions, too many slightly different ways that people might like to configure their thing. Which is great! For the user. And terrible! For me, trying to control all of these different configs with one tool. I’m not saying the CLI isn’t/won’t be supported. Just that, today, I’m sitting in XCode vs. spending time thinking about the CLI.

Hi! I use an Obsidian vault as both my JDex and my filesystem root. My existing IDs use the Folder Notes plugin, with each note inside its matching ID folder: 72 Disks/ └── 72.11 First disk/ └── 72.11 First disk.md With the unmodified JD CLI, jd new id 72 Another disk appears to look for ID notes directly in the category and creates a note beside the new folder: 72 Disks/ ├── 72.12 Another disk.md └── 72.12 Another disk/ That differs from my Folder Notes layout. More importantly, if all existing notes are inside their ID folders, can jd new id reliably detect which numbers are already taken? Is this layout intended to be supported by the CLI, or should Obsidian users keep their JDex notes beside the ID folders? If Folder Notes support would be useful, would a configurable mode that counts ID folders and creates the note inside each folder be welcome as a PR? I’ve made a local patch for this behavior, but I’d like to understand the intended approach before proposing it upstream. I think that I might have the issue because I use Folder Notes as my JDEX instead of using another file tree as it’s provided in the starter kit. Is it wrong ? What was provided What I use

I maintain my JDEX in Obsidian - using the one note per ID system. They are grouped into area and category folders. I also keep a daily note in Obsidian which can link meeting events and tasks back to the JDEX, so the JDEX note entry serves as a type of project log. In writing type projects, I may draft materials in Obsidian before moving them into my file system.

Basically you take the folders and save them inside your vault then make an index page that links everything together. The basic plugins I recommend are Sync, Calendar, ReadItLater and TimeStamper. But if you are running Obsidian on Windows or Linux you need to know that it’s possible for the plugin creator to get into your computer files. Here is the link to the info. https://www.reddit.com/r/ObsidianMD/comments/1nlyk5f/is_it_true_that_community_plugins_have/?share_id=rAUhEqoVZAX3xJkYWBWJK&utm_name=ioscss

That does indeed help. Thank you very much for that insight and your tips. I just need to decide how I want to move forward with this. Much appreciated!

So the stuff that fits in LAS it really doesn’t actually matter how you store it. If you’re used to clipping into something like Bear, there’s no reason to stop doing that. Let’s look at a concrete example: receipts. Because there’s another split to consider: there’s how do I store this stuff (clipped to Bear vs. filesystem) and there’s also does it fit in LAS ? Because it’s important to remember that the Life Admin System is called that and not the Literally All Of The Things You Could Possibly Store system. We’ll get to that later. For now, LAS does have 13.31 Purchase receipts and that’s where this stuff should go. So how should it be organised? You’ve got a bunch of options – and some of these are Bear-specific, i.e. it would look different if you did it in Obsidian, say. One Bear note with attachments I don’t see why you couldn’t store all of your receipts in one Bear note. Use headings for each thing, add a bit of searchable text, drop in the PDF. – but I wouldn’t do this . It just feels clunky. One Bear note with references Alternatively, use a single Bear note but reference the receipt, which is in your filesystem. This is what I naturally did, without thinking too much about it. (I only keep personal receipts for items that I might need e.g. for warranty, return; if you keep every receipt, this story gets more complicated). Here’s my actual note. You can see how this allows me to tell myself that receipts are in different places – an app, my email, in the filesystem,

I just typically haven’t really taken many notes. I started off using Evernote as a filing cabinet of sorts - keeping receipts, reference articles, and orders. When I left Evernote, I went to Bear. I still use it the same way. Stuff that comes in email from orders, website content I archive, I save into Bear with the clipper or print to a PDF and attach. Invoices, bills and corresponding receipts go into their own notes so I can keep track of keeping them together to track the lifecycle of paying what I owe. Yes I can track financial stuff in a money manager (and I do) but it’s just muscle memory for me to track it all and keep it together in a note to keep it all together. It’s just easier for me to search and find this way. I guess I could just move that stuff from notes to a folder. I was just lost in how I would LAS to manage it and reference it. Or would I not use it for that? I’m sure I use Bear in an unorthodox way and not for its intended purpose, but I’ve managed to make it work for me this way.

I started showing Lucy how to use Obsidian – we released 2 episodes – then we realised that there are already 1,000,000 Obsidian tutorials and me creating another probably wasn’t the best use of our time. (Honestly I’m not even that good at Obsidian. People in the Discord pointed out a bunch of stuff I’d missed.) It is a bit ‘abstract’, I agree. It’s a powerful program with a lot to it – but to use it as an effective JDex you don’t need to use 95% of those features. I don’t. I use it as a note browser and editor. You don’t need any plugins. Plugins just add complexity – the base app does it all. I don’t use note templates. Again, complexity. Start a note, and type whatever you need to type into it. I actually think a “beginners guide to implementing the JD system using Obsidian” is a good idea … last time we focused on Obsidian the app vs. just showing how I use it to manage JD. The problem is just time, unfortunately.

Hi there. What sort of stuff are we talking about? A “note with existing PDFs and content in them” sounds like way more than just a note – sounds like the sort of thing I’d assign to its own ID. Let’s say one of these things is some research you did into … I don’t know, plant care. So you have PDFs of plant types and watering tips and what types of food indoor plants like and so on. In this case that fits neatly into LAS 12.41 Indoor plants , so I’d drop a note in Bear to say that this is where this stuff is, then the PDFs and so on would go in my filesystem. As a rule, I don’t store PDFs and so on in Bear. I keep it pretty light – it’s the JDex, not the main content. Use your filesystem for content. It’d help if you could share a couple of examples, I don’t feel like I’ve got a proper mental picture of the sort of thing you’re trying to manage.

It would be really useful if we could actually get a beginners guide to implementing the JD system using Obsidian, and how to set up Obsidian for the LAS system. Obsidian is a bit abstract, so hard to understand Its not clear which minimal no. of Plug Ins are actually truly helpful for the JD system It would help to know how to set up an obsidian note template properly and why on the website. Has the above been covered somewhere, or could it be placed into a location somewhere so people can read it.