I am about to setup my jdex and the file-system. I am leaning towards using one jdex file which captures the structure and the category IDs. I would like to know if anyone in the community has tried it and what their experience been on using one jdex file instead of several *.md or *.txt files for indexing?
More context
Coming from …
I have been using org-mode (https://orgmode.org/) within Emacs for taks and project managements. Briefly, It can:
take notes in plain text but interpret and present it pleasantly
collapsible headers and sub-headers
add tasks and schedules which can be pulled up as an agenda for the day/week/year.
Have links to files and folder and open them within emacs.
In short, the *.org files are just text files, similar to *.md files.
Going to …
Currently have a boquet of other *.org files for tracking tasks and notes. These are in git synced across different computers and mobile.
I am planning to add one jdex.org org-mode file intoto this for indexing the JD File System.
The jdex.org file will maintain the structure of the Life Management System. For e.g.
If I go down this path I will perhaps ask our good man @johnnydecimal to extend his already cool LFS generator to be also able to generate one jdex.org file for org-mode users. Till this is done can I get source data (xml?/json?) which you use to generate LFS files in various structure and format. So that I can programmatically generate the one org file from that.
Neat! Would you mind elaborating what made you move away from the single jdex file. Did you discover any issues or inefficiencies?
One particular case for me is while syncing the jdex to different devices for reference, i would have to deal with only one file and i will have all the IDs with me to look up no matter which device i am on.
Oh that’d be interesting. Easily done if I have a spec for it… I’ll add it to the list.
Nothing that fancy, I’m afraid. They’re a bunch of Markdown files with structured frontmatter which Astro, the site generator, can manipulate via its content collections feature. So there’s nothing you could do with the ‘raw’ data that you couldn’t do with the Markdown files as-downloaded.
Oh cool! Then I guess it would be easier for me to actually generate the org file programmatically from one of the LFS zips than to write the spec .
Just to give you an idea putting this into a JDex - Life Admin System.org file ….
* JDex - Life Admin System
** 00-09 System-management area
*** 00 System-management category
**** 00.00 JDex for the Life Admin System
:PROPERTIES:
:CATEGORY: 00.00
:END:
- Description
This reserved ID is where you store this system's JDex.
- Locations
[[https://jdhq.johnnydecimal.com/las/00.00/][Open in JDHQ]]
[[../../../00-09 System-management area/00 System-management category/00.00 JDex for the Life Admin System][Open in JDFS]]
- Relates To
- KeyWords
-----
**** 00.01 Inbox for the Life Admin System
:PROPERTIES:
:CATEGORY: 00.01
:END:
- Locations
[[https://jdhq.johnnydecimal.com/las/00.01/][Open in JDHQ]]
[[../../../00-09 System-management area/00 System-management category/00.01 Inbox for the Life Admin System/][Open in JDFS]]
- Relates To
- KeyWords
-----
**** <TODO similarly upto 00.09, skipped for brevity>
** 10-19 Life admin
*** 10 Management of area 10-19
**** 10.00 JDex for area 10-19
:PROPERTIES:
:CATEGORY: 10.00
:END:
If you need to, this reserved ID is where you store area-specific JDex data.
- Locations
[[https://jdhq.johnnydecimal.com/las/10.00/][Open in JDHQ]]
[[../../../10-19 Life admin/10 Management of area 10-19/10.00 JDex for area 10-19/][ Open in JDFS]]
- Relates To
- KeyWords
-----
**** <TODO: Similarly 10.01 to 10.09, skipped for brevity>
*** 11 Me & other living things
**** <TODO Skipped for brevity>
**** 11.11 Birth certificate & proof of name
:PROPERTIES:
:CATEGORY: 11.11
:END:
- Description
Proof of your birth and name (or change of name) – where it all begins!
- Locations
[[https://jdhq.johnnydecimal.com/las/11.11/][Open in JDHQ]]
[[../../../11 Me & other living things/11.11 Birth certificate & proof of name/][Open in JDFS]]
- Relates To
- KeyWords
-----
Sure, it quickly became too cumbersume and unwieldy because I tend to add a note or two (or more) to IDs. Also synchronizing was an issue when I made changes on different devices that weren’t able to sync in between. Having it in extra files allows me more flexibility for the price of not having it “at a glance” but that can be solved by tec and tooling like searching for and jumping to specific IDs. In my case with vimwiki and I’m pretty sure orgmode can handle this also with ease. Having the wiki/jdex data in a vcs repository helps with syncing and handling possible conflicts. However I didn’t have conflicts since I switched to single ID notes.
Basically I have a “one page JDex” like you intend but mine is automatically generated from the single ID notes. I use that as a main entry point but for everything “more down below” I simply use the search.
Thank you! That helps. I am planning to take your route, start with a single and split when things start to bloat. I will start with a custom system for my day work which doesn’t fit LFS LAS. The numbering scheme should help tie various pieces together. In a few weeks time I should have a sense of how best to proceed with LFS LAS.
.
