It looks like we are on the same page. We’ll need to split the inner logic of Logseq “what kind of structure the data contains” and the presentation “what kind of menu”.
For the feature requests, let’s start with a draft:
Feature request 1: Knowledge organization for tags
Rationale:
- Putting tags into a hierarchy will remove clutter, improve organization, and enable more advanced searches, e.g. faceted and tree searches.
- A single classification hierarchy (a la Dewey Decimal) is not enough, as each item can only have a single place (does a historic novel go under history or literature?). We want to find a historic novel to be both under the history and the literature section.
- We need a polyhierarchy, where each item can appear in multiple places.
Implementation:
I suggest to roughly follow the SKOS system. Each tag can have optional relations specified that state that it is:
- a broader or narrower version of another tag (e.g. “mammal” is a broader tag than “cat”)
- a transitive version of broader and narrower (this probably should be the default)
- related to another tag
- identical to another tag (sometimes items might get tagged automatically, e.g. by Zotero’s imported tags, we might have an item with an automatic tag “History” and need to state that this is the same as “history”).
The other SKOS features, such as documentation, labels, and collections, are not essential and can be added on later.
Feature request 2: Faceted search / Hierarchy view
Rationale: Need an easy way to search hierarchies
- Provide a hierarchies link in the sidebar that links to a hierarchies page
- Provide faceted search (I am not a big fan of faceted searches and prefer a full tree view, but it has some advantages and can be naturally implemented on top of a knowledge hierarchy.)
Feature request 3: Tree search
Rationale: Hierarchies might grow very large, it should be possible to filter hierarchies to narrow down potential matches. The results should still be displayed hierarchically.
- Searches can return trees, i.e. they can return a hierarchy. For example, a user has a hierarchy of books sorted by fiction/non-fiction, genre, author etc. Filter this hierarchy for all books that have an attached file will display the hierarchy with only the books that have a file attached.