every night i dream of this feature and every day i check and although i have yet to be rewarded i refuse to give up hope

Nested tags please. It's too cumbersome - and disorganised - otherwise.

This would be fantastic to reorganise everything for 2023

+1

would also appreciate something like when i save an image or link from the web using right-click(which I often do) - i can save this to a folder, and some tags are auto-added because i placed a link in that folder, and so do the parent tags if it is a child folder

I think people only use "collections" because they are used to a traditional file system. Gmail before also had "folders" and nowadays they completely removed that concept and only have "labels" which are basically tags that allow each one to have a parent.

Let's say I have an url that is a "mp3" and also a "power-songs". I can add mp3 and/or power-songs. Later I can find all "mp3" or all "power-songs" that clearly are "mp3". Otherwise I will end up needing to prefix all my subtags like "mp3-power-songs" or I just lose the information that a power-song really belongs to mp3s. In Gmail in the search they make it such as: https://mail.google.com/mail/u/0/#label/sports%2Fdance which would translate to "sports/dance".

This way we have total control through tags and to be honest I think the concept of "collections" is kind of useless. Why just don't remove that and make it like "favorite tags". Gmail once had the concept of "folders" and "labels" at the same time and it was pretty confusing because a "folder" was nothing more than a tag. Even nowadays their concept of "moving to" means "remove all tags and add the one you want to move to"

tag hierarchy in Obsidian is very useful

Tags, which could be very useful, are all over the place.

I think that some Linux Desktops have looked at this, but Linux always seemed a bit of a labour of love in other ways.

I think it would be a start to have a tag manager, and that the tag manager could work with imported files, and be able to export files.

I understand that a capable tag manager is another software product in itself.

Schema.org has been mentioned in these comments. They decided not to follow an hierarchical encoding of relationships between concepts as too many possibilities and not central to their use-case of increasing visibility for e.g. search engines.

When people search they do not search applying concepts in an hierarchy.

It is fair to say that Schema.org is a commercial solution that is a watered down version of the capabilities of semantic web technologies.

But when we organise we do apply concepts of hierarchy, and we are prepared to learn or create hierarchies to ease comprehension.

So web search and information storage and retrieval are different but complementary tasks.

I hope that any tag manager will have the ability to facilitate creation and also suggest hierarchies.

It would be a good start.

But it seems more likely that such a tool would be very complex, hence the alternative would be for file import and export with internal recognition of some useful formats, TBD by Raindrop.io. This would be the simpler solution I expect.

Very keen for this. Tags are arguably a more natural case for nesting than collections are.

I have started to hack it, eg. "Conditions/Hayfever", PKM/Highlighting", "Tools/Snipd" - but, whilst it's a workaround, it's not quite right.

--

I am also playing with the idea of different tag types... one use of tags is to describe the content topic. Another could be to describe the content _format_. So I have been experimenting with tags like "@article", "@episode", "@thread" etc...

That has got me curious about aligning this with the existing Schema.org CreativeWork type, which already includes a number of content type entities (eg "Episode", "Guide", "Conversation", "Clip")...

But (getting back to "hierarchical tags") these, too, are naturally hierarchical in nature - eg. Thing > CreativeWork > Article > NewsArticle > AnalysisNewsArticle". So I see another application of tag hierarchies in approximating this.

Hierarchical tags could be handled by interpreting punctuation as dividers, so that software.pdf creates a tag pdf within a tag software. Ideally, the user could set the punctuation mark in the settings, to identify which character (e.g. dot . or dash -) is interpreted as divider

I'm guessing that many of you would also like the "Tag "Clusters"" and "Tag Refactoring Tool" requests. Please upvote them if you like those ideas:

Ultimately, it seems like what people are looking for in this request (and the "Tag Refactoring Tool" and "Hierarchical Tags" requests) is a powerful tag management tool.

Supporting hierarchies in the tag management tool would be fine, but a more robust solution might be some sort of ontology or network/graph-like structure in which relationships between tags could be defined.

For me, this is a problem that comes up over and over in lots of contexts (e.g. organizing my email folders, my Google Drive layout, etc etc). There must be a well-studied academic solution for this kind of information management. If anyone can reply with an article along these lines, I'd be very interested.