Implementing group tags in Logseq in the style of org-mode

[gax]

I think this is very important! There are already a bunch of feature requests on this topic

High level:

Knowledge Management for Tags / Tag Hierarchies

Why do we need Knowledge Management for Tags? Graphs will quickly have far too many tags We need a way to organize and browse tags The Problem Tagging leads to a large number of unrelated tags (thousands) without any structure Browsing these tags through a list, graph, or tag cloud, is not very efficient As shown in another thread by @ChrisYT and @Zdenek_Hurak items imported from other systems (e.g. Zotero) have many overlapping tags, such as “History, 20th Century”, “history”, “History / …

Discussion:

Would a rich commitment to hierarchies and classification be an anathema to Logseq culture?

First of all, I’d like to thank the adventurous team at Logseq for committing to the endless and sometimes thankless work of building a new software platform from scratch. I really appreciate what this tool is, and am excited for what it may yet become. I’d also like to thank the company and key influencers in the Logseq community for not being entirely hostile to the idea of hierarchy in information organization. For many of us, hierarchy is a natural way to construct access paths into our gra…

And one way to implement hierarchical searches along properties and display them as a tree:

Specify and display relations between pages/tags

Premise Following the discussion here I think I have a viable and concise proposal to address most use cases of the “hierarchically organize pages/tags”. The point is specifying hierarchies using page properties. For me the ideal would some syntax that, given an arbitrary user-defined <property>, (for example extends::), looks like this: Specify relations between pages Parent.md <property>:: [[Child]] Child.md <property>:: [[Teddy]] Display these relations Tree {{tree <p…