I use Logseq for my index.
When you use double brackets [[page]] in Logseq, you create a page
For searchability (unique) - when using in email subject, or using Everything (software) to search, I keep single brackets in numbers IF there is a folder created in my storage
That means:
23.01 Title here < — no brackets = no folder created, no Logseq page created
[23.02] Title here < — brackets on number = folder created in my storage system (NAS)
[23.03] [[Title here]] < — brackets on number and double brackets on title = folder created in my storage (NAS) and page created in Logseq
23.04 [[Title here]] < — no brackets on number and double brackets on title = NO folder created in my storage (NAS) and page created in Logseq
I like the low-tech approach. If I understand correctly, I think I’ve found a similar one. By ‘passive information’ do you mean the fact that this information about the structure of your files is just encoded ‘passively’ in the text itself, as a kind of convention?
I work in Vim with various add-ons for wiki-like functionality, including a database-driven search, but a fuzzy finder that just reads every line as I type often works so well. So I put information similar to yours in the title of each file. In my case, I’m experimenting with a / to show that a file is a child of an ID folder as opposed to the index for that folder. This helps to disambiguate when these titles show up in various places:
# 23.01 Something I'm working on #title of 23.01/23.01_index.md
# 23.01 Something I'm working on / reference 1 #title of 23.01/reference1.md
You could put any plain-text amenable tags on that line, and as long as you have less than a hundred thousand files or so, any fuzzy-finder full text search will let you filter that down in near real time.
This could be done with a complicated database setup, and I’d like to implement that sometime for a few advanced features, but this is really a case where 90%+ functionality comes with the tools already available.
My main motivation is speed, and as you point out, keeping it low-tech.
Logseq has this convenient function where it does the bracket on both sides with single keypress when text is selected.
I can then copy-paste directly to create folder…
I’ve tried more complex / convoluted workflows, but this one appears to keep me at a good cruising speed.
I find that I have no good way at the moment to extract “complete index, including files that are in the folders”. But with the number of files, that would have made my index very large. I will keep your input in mind. Thank you.
Example of workflow from Logseq (I was supposed to keep it at 21.ID, sorry for mis-typing 22, 23, 24)
I find that I have no good way at the moment to extract “complete index, including files that are in the folders”.
does your file manager allow a ‘tree view’ where you can collapse/open folders without opening them? would that be a ‘good enough’ low-tech solution, in combination with your index page in logseq?
2; Get a bit familiar (create your first logseq “graph” (as they call it) - but it’s really only a config and a bunch of markdown files - and get to know a little about daily journal, [[pages]], #tags, slash commands, left and right menu)
(a lot of good youtube stuff out there). I’ve been down the Logseq rabbithole since april 2023 - and for me - it’s life BEFORE and AFTER
3; When ready, Create [[00.00 Index]] as page - (and if you prefer make it your homepage (in config.edn) - so that it’s the first thing that loads when you start Logseq)
4; Create your Areas as [[Pages]] - here are mine:
5; Continue with the Categories under each page - just as shown in the above .gif example
Everytime you want to create single brackets around a number, just select the text and press [ > brackets are created on both sides
Everytime you want to create [[page]], you just select the text and do [[ > brackets are created on both sides
6;
Export your index?
If you wish to export your index out of Logseq, there are nice plugins that can easily be installed via Logseq Marketplace (included, find it in settings)
There is also a cool function in Logseq called “embed”, which means you can cherrypick information from different locations, piece them together (like building blocks) and export them.
7; (I do not use Logseq Sync between devices - I let Syncthing and AOMEI Backupper do my backups, I can access a computer (Win10 Pro) from anywhere via Chrome Remote Desktop / VPN & rdp- so I keep all my stuff on that computer - but access it from everywhere)
FYI:
Here is the embed function I mentioned, which gives you direct access to what you embed (I’ve embedded the next level Areas > Category, so can quickly expand / contract and nagivate with keyboard or mouse)
Also shown;
How to input link in (markdown) - so if you click it, it opens File Explorer - for easy access to storage.
Let me know if you get stuck on something, I’ll try to advice.
In case there are other users of Logseq out there.
I tweaked sethyuan’s logseq-plugin-wrap to accommodate that I use single brackets in the index to show there is a folder created in the JD storage system :
This was done by replacing this code (since I don’t use annotate) in .logseq\settings\logseq-wrap.json
)
