Isn't this the functionality of Collections?

To be clear, I support the development of nested tags / hierarchy for tags. The canny discord bot only previewed the quote of my post below that I was disagreeing with, and people that don't click through would miss my point.

"I don't think this is a good idea. I feel it goes against capacities philosophy of not having to worry where to put notes/objects."

I very much disagree with this statement. While notes and objects may not need an organization as a whole, there are some concepts that are already organized scientifically, and my notes need to reflect that. For example, I have a lot of notes about the natural world, and I'd like to be able to tag a particular spider entry as #Arthropods/Arachnids/Spiders/Spinybacked Orbweavers and have any level of those tags bring up my note. Clicking on "spiders" should bring up all spiders, similarly clicking Arachnids bringing up all spiders, scorpions, ticks, mites, etc.

In other words, I would like to see a high level tag produce results of everything tagged at that level along with anything tagged with any subtags. Only by clicking the subtags could I narrow the results of what is returned.

The ability to have "tags within tags" is a must for me and I'm struggling to get Capacities to work for me without this feature. It's not about creating a hierarchical structure, it's about providing an easier / more visual way of more granular tagging. Essentially, it's the ability to create tag lists such as;

Meals

> Breakfast

>Lunch

>Dinner

>Supper

Do we know when this is planned for release?

V

Really don't think this is a good idea, agree with Xiubo Zhang that it goes against capacities philosophy about not having to worry about where to put notes/objects and how to construct the hierarchy. Why not do one better than most notes apps and use AI to auto-tag similar to Napkin.

Instead of adding this complexity the development effort should be to add boolean search with objects AND tag1 AND tag2 and then create a great UI for saved searches (filters). These saved searches could be put in the left panel under the objects so that when objects are closed the saved searches would display.

Tag hierarchy is over rated and comes with a host of user and technical problems. Jump ahead of all the rest and do it better!

Hope this coming soon. It is necessary.

I don't think this is a good idea. I feel it goes against capacities philosophy of not having to worry where to put notes/objects.

What could work though is to allow tagging an object with block references, and the hierarchy of tags can be managed as ordinary outliners --- block is the intended unit of hierarchy, after all.

This is a must-have. Imagine Capacities as a library. For a library, you need hierarchy in catalog to store and retrieve a book.

Without nested tag, you are assuming every tag is perpendicular to each other, and there are no contain-belong or subset relationship between two tags.

I rely on nested-tag heavily in Devonthink.

Nested tag support represents the organized management of tags, so we also need a dedicated page for managing tags.

Once there is a nested tag structure I would appreciate a tag cloud to help navigate. I'm going to end up with hundreds of tags because my research covers so many concepts, contexts, and examples.