+1 on the response of memeplex. I frequently need to store and retrieve files corresponding to projects.
Without file system hierarchy, I would always have to open LogSeq to find the right files, which makes a simple 5 second “select dir, select subdir, select file” task a 1 minute “open LogSeq, find the right note, find the asset link, find the asset in the asset directory”.
And should I ever decide to use another tool, I would have to go through all the assets and manually sort them into subdirectories.
I’m generally quite happy with LogSeq, but I don’t like feeling locked in.
I find it nice that there are ideas of using hierarchies in novel ways, but I would very much like to have the option to make the choice of having one of them being the primary one, and have it represented as file system hierarchy.