So then do you really need the index file per se?
You can just have this right? You have the note for each entry and it’s automatically indexed when you list it in Bear - so then you see what the next number is.
This basically seems parallel to my thinking - of not needing the index as a file per se - on your setup you have the note for each entry with the appropriate tag and its location, pointing you to the system where it resides.
In my thinking I’d have it in the directory structure - there in the appropriate directories also have the individual Obsidian note files for each entry, giving me also the location - i.e. Work email etc?
It is an index - as you say - albeit not an index file, I was thinking you have one note file, or spreadsheet where you list everything.
As a side note - this way (as it basically seems to me the same, just with me it’s one main directory structure - with you it’s the note tag structure in one app) could entail many local separate directories - referenced via the main index.
I was thinking there are let’s say files you want to keep in a separate directories - but still have them in the JD structure - photos as an example.
I was thinking it might not be beneficial - in my case where I have the directory for all files - to also bring them into this and file it inside - as it would bloat it. Like this they could have a separate “Photo” dir and the subdirectories there - and these would then be indexed in the main index - with location “Photos” or whatever. This way you could have many file structures locally - where appropriate - yet all indexed centrally.
What do you think?