3 ms·
You could hypothetically collapse the two though. You can have tags and could use those to automatically generate efficient organization structures. For exampl
by culi 5y ago
You could hypothetically collapse the two though. You can have tags and could use those to automatically generate efficient organization structures.
For example, say you have the following datums with the following tags
apple: plant, Rosaceae, tree, fruit
peach: plant, Rosaceae, tree, fruit
rose: plant, Rosaceae, shrub, flower
dandelion: plant, Asteraceae, herb, flower
carrot: plant, Apiaceae, herb, root
pig: animal, Suidae
You can then try to generate a folder structures that optimizes certain parameters like keeping the average number of children to not too far away from ~6 and/or minimizing the depth of the repo structure or whatever. Depending on how you wanna optimize it, you could end up with a number of structures such as:
root
- plant
- tree
- apple
- peach
- herb
- dandelion
- carrot
- rose
- animals
- pig
or
root
- Rosaceae
- apple
- peach
- rose
- animal
- pig
- other
- dandelion
- carrot
You can use your imagination to think of better structures or optimization problems, but you get the basic point. We can have tags be our primary classification method and have the organizational structure be an outcome of that.
- pphysch 5y agoI 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.
- githubalphapapa 5y agoHere's a library for writing such classification systems in Emacs Lisp: https://github.com/alphapapa/taxy.el https://github.com/alphapapa/taxy.el Especially, see this example: https://github.com/alphapapa/taxy.el#sporty-understanding-completely https://github.com/alphapapa/taxy.el#sporty-understanding-co...