3 ms·
I like this approach: building a simple folder interface on top of a more flexible tag system, which can always be accessed when necessary. I think many systems
by pphysch 5y ago
I like this approach: building a simple folder interface on top of a more flexible tag system, which can always be accessed when necessary. I think many systems would benefit from it.
There are tradeoffs, though: a fair bit of overhead for each heavily nested item. And you would want some support for ensuring the integrity of the hierarchies (i.e. someone accidentally removes "tree" from the tag set of "apple").
- throwaway_Aef8 5y agomaybe on top of your idea ensure there's a graph feature like at the top right of https://help.obsidian.md/Obsidian/Index https://help.obsidian.md/Obsidian/Index
- bo1024 5y agoI implemented this for my email. Each email can have any number of tags. Each tag can have a directory hierarchy. So for instance an email can be tagged fun/ski, social/facebook/marketplace, money/receipts. If you open the social/facebook/marketplace “folder” you’ll see the email, but also if you open the money/receipts “folder”. You could also see it in the intersection of the social tag and the fun/ski tag, etc.