#Subfolder structure for librarian minds
45 messages ยท Page 1 of 1 (latest)
Fantastic, thanks a lot, I was not aware of that
Is it gonna be integrated or officially supported?
I am afraid I have no idea. You would be better off pinging Sawhney a message to get an update. It would be a plugin but hopefully something native can come out of it
Thanks a lot man, you are a life saver
In the mean time, do check out this forum post by @potent vessel for some ideas: https://discuss.logseq.com/t/different-ways-to-structure-data/8819/37?u=alex0
Greetings. Iโm still rebooting with Logseq and Iโve been struck by your reference to a Telegram bot since I use it a lot. I know this is not related to this thread, but Could you, even if it was private, tell me something about that bot or tell me where to find information about it? Thank you
lol I replied the same a minute ago in #italiano . @hard fiber check that
Sure, I think I'm going to stick to my set up for now, I have been using obsidian but logseq's tags are just on an other level, I will compleatly migrate once the plug in is ready
Hahaha, true, thanks a lot to you too man
About that plugin, it is not clear if it is supposed to be used to manage actual folders inside the graph folder or to organize pages in virtual folders inside Logseq only
@spice flume I would love an update and a bit of insight on the folder plug in
Great point, we should ask
A few updates about how it goes.
initial version will be an abstraction on namespaces in a way that js fundamentally the same as namespaces just represented in a way akin to folder with dragging and dropping and stuff. Plus some neat ui tricks to hide stuff like long file names
Second phase is limited by the API but it is actually possible to create a 100% local web app that can asccomplish this. Could be an option as a sort of arrange items into folders button
How about the real pc subfolders?
Won't be in real time. You'll have to click a button to persist changes to the PC level.
But should be automatabke so that it persist pretty regularly
I wouldn't mind to be honest, I just really need subfolders
I really love organizing that way on a macro level
Completely get that. Just curious about ho important PC level sub folders are to you?
Why would they be more impactful than just within logseq?
Out of curiosity
I work with a NAS on my home network and I use it as an archive and everything is neatly separated in folders
My notes too
I just want my folder structure to reflect in logseq and modify within it
I don't know if I understood your question correctly
@spice flume
The approach I'd take (and will do when I will have some time) is a script that uses Logseq HTTP API to read some specific indented lists (that I'd tag with [[index]]) and build a folder structure on the filesystem (alongside the graph folder) containing only relative symlinks to the pages. I already a script that opens .md files in Logseq when I click on them and they are in a graph, so I would be able to browse pages as I structured in the outliner using fs folders
Why not just have folders like in Obsidian, Notion, Evernote, Roam Research ecc.
Organizing everything in a single hierarchy with no duplication of the same node is a problem
I was on the same boat, then I realized that the outliner let you structure in a ordered hierarchy Pages&blocks (using references), text, links etc. The way we normally organize files in folders in the file system is just a subset of the above, with the following restrictions:
- Leafs (nodes with no children) would be pages
- All the other nodes are text strings i.e. the title of the folder
Now that I realized this I don't see why one would want to apply the restriction of a filesystem-like hierarchy, since you can smoothly move between different kinds of hierarchies with the rules being in your mind and not imposed by the software ๐
Example of a hierarchy restricted by classic filesystem rules ๐
Tbh i like the basic pc style folder structure, documents in folder and then you can link them
So I can see my pc folders structure in logseq
Why can't it reflect the pc folder structure so if I change a page position in logseq it does the same in the computer
So practically what I said, right?
@hard fiber yes, I never said I disagreed
My mistake, I misunderstood
Thanks for taking the time on creating the plug in (when you will have time obviously)
Not sure if it's related, but Another Embed offers a hierarchical favorites/recents feature.
Yes, your findings are all correct. This feature is not well documented and certainly some behaviors can be tweaked for better usability too.
- The ordering of the items is just as you described and they are ordered by name by default.
- Regarding the automatic updating, I have some techniques in mind that I'd like to try. BTW, Logseq currently has a caching bug related to advanced queries that yield wrong (cached) results when one has items removed (re-index is currently the only way to get rid of the cached result). New fav item causes hierarchy to disappear, this is a bug introduced by a DOM change in Logseq v0.9.x it seems. I can fix it.
- I'll think about this, maybe a fix is possible.
BTW, this hierarchical favorites/recents also works with namespaces (or namespaces and page tags combined).
BTW, Another Embed also allows you to adjust the left sidebar's width by dragging.
Another Embed is updated and solved points 2 and 3.
actually i've always wonder why this feature is in "another embed" ๐ it's so random
it could be a good plugin on its own
๐ You're right, it was a quick idea I had and wanted to experiment with quickly and I was already having too many plugins.