Convert tag hierarchy to subdeck hierarchy

A simple way to turn a tag hierarchy into a stack view without moving the cards into a new stack.

WHY: Have a large number of cards (Ankiphil) whose subject mapping is organized by tags (also large number). So it is NOT possible to do this manually via custom decks.

This organizational structure of card decks has become popular among card decks intended to be imported, due to various advantages. The gain, while at the same time low programming effort, is therefore not to be underestimated.

Implementation suggestion:
Mark a tag > context menu item > “create tag hierarchy”.
… Window opens
… here are now all subtags of the tag listed
… there is the option to select/deselect these subtags individually
… [Cancel] [OK]
Thereupon the tag hierarchy is created and displayed recognizable as a “tag stack”, where subtags are displayed as sub-stacks. The “tag stack” now contains all cards of a given tag, that are activated. Card learning progress is applied to the cards. Maybe the implementation can be based on custom stacks?

How should this work for cards that have multiple tags? Where should the card be assigned?

What advantages are you suggesting subdecks have over tags? As far as I understand tags are far superior and subdecks are mostly for if you want to study topics separately or if you want different settings

This problem does not exist because
(1) tags are arranged hierarchically
(2) no tag can be part of two paths
(3) cards that are assigned to a child tag should also always be displayed at parent tag level.
(4) tags that are not part of the selected tags sub-path are not relevant.

Am I missing something?

Hey AnKingMed, nice to find you here!

So, suspect I may not have been clear enough.
I do NOT want to assign/reassign cards to a “real” subdeck structure. But simply make the structure of a tag hierarchy available to the user as a view similar to the current deck/subdeck representation.

Cards assigned to a child tag, would be displayed in there respective “sub-tag-deck” as well as at parent tag level. Since the “tag-decks” would represent a tag (instead of a real deck), these “tag-decks” should display all active cards with the corresponding tag. Also newly created cards with the same tag should always be “added” automatically. (=> tag-decks are a view/query of cards not a “real” deck).

Learning progress should be applied to cards. Users should be able to expand/collapse the structure. “Decks” representing a tag hierarchy should be clearly recognizable to the user (e.g. preceded by a blue “#”).

I know that on the computer it is possible to navigate by tags, and also that you can select cards by tag to then create a custom learning stack … but on the phone this is not easily possible, and also on the computer I find this rather cumbersome if I have to create this by hand for all (>200) tags.

I feel like I’m not grasping the suggestion fully - are you looking to be able to visualize the tag tree, similar to the deck tree? That’s what this addon does. If you then want to study a tag, that’s what this addon does.

It seems like you don’t quite understand how to use tags properly.

If you have a note, that note can only belong to one deck. It can, however, have multiple tags. How would you know which “Subdeck” to put it in?

For what it’s worth, AnkiHub does allow for creating a “Subdeck” tag and it will then convert the Subdeck tags into actual subdecks so you could use that method if you really want