Sub labels. #911

Closed
opened 2026-02-21 15:22:45 -05:00 by deekerman · 4 comments
Owner

Originally created by @Spork-Schivago on GitHub (Nov 10, 2013).

I would like to see an option for sub labels. For example, I have a label called ISOs and one called Movies. I would like to be able to add the Movies label to the ISO label and vice versa so ISO is a sub label under Movies. Thank you for all your hard work.

Originally created by @Spork-Schivago on GitHub (Nov 10, 2013). I would like to see an option for sub labels. For example, I have a label called ISOs and one called Movies. I would like to be able to add the Movies label to the ISO label and vice versa so ISO is a sub label under Movies. Thank you for all your hard work.
Author
Owner

@Kervius commented on GitHub (Nov 10, 2013):

You basically ask for hierarchically organized labels. Instead of list of labels, a tree of labels.

P.S. I thought it about myself. But I personally would prefer tagging, not labeling. Main difference is that an entity (in that case a torrent/download) can have several tags. While label can be only one. With the tags one can then introduce a search/filter for the tags, and as consequence, filter of the torrents by the matching tags. That would allow to establish a loose hierarchy. But the looseness allows to jump through levels of hierarchy.

@Kervius commented on GitHub (Nov 10, 2013): You basically ask for hierarchically organized labels. Instead of list of labels, a tree of labels. P.S. I thought it about myself. But I personally would prefer tagging, not labeling. Main difference is that an entity (in that case a torrent/download) can have several tags. While label can be only one. With the tags one can then introduce a search/filter for the tags, and as consequence, filter of the torrents by the matching tags. That would allow to establish a loose hierarchy. But the looseness allows to jump through levels of hierarchy.
Author
Owner

@Belove0 commented on GitHub (Nov 11, 2013):

"Tags" and "labels" are sometimes words used interchangeably; and are rarely hierarchical...
Now, I think in Utopia, labels or tags would support hierarchy but still have the feature where you can have multiple labels/tags assigned to each torrent.
This way, when you Assign the label "(in Spork-Schivago's example) "Movies" you implicitly assign Spork's label "ISO" as well. This opens up many more filtering possibilities.

For example, in a contact management application I use, there is a loose labeling scheme. I have labels for "Businesses", "Friends", "Family,", "Government", "NGOs", etc. I also have labels for specific cooperative groups of people I interact with on different subjects an teams of people within organizations. Then, I have labels for geographic region. Just taking the geographic region as an example, I have created labels such as "Africa" "West Africa" and "Cameroon". That is great, and I can assign all three labels to every contact in Cameroon, enabling me to filter by broad or narrow region, but this is tedious and error-prone. Especially since the same contact is also labeled in various other contexts besides region where I must do the same thing.

So, I would argue that labels are much more useful than a strict folder/directory-only filing scheme, but they can be given the same features and we can have the best of both worlds.

Some people achieve a compromise where they create labels such as "Africa/West Africa/Cameroon". That solves a sorting of labels issue; but it does not allow to filter for West Africa or Africa without filtering for a specific country.

So, in short, I think this is a good and useful proposal, but not instead of allowing multiple labels :)

@Belove0 commented on GitHub (Nov 11, 2013): "Tags" and "labels" are sometimes words used interchangeably; and are rarely hierarchical... Now, I think in Utopia, labels or tags would support hierarchy but still have the feature where you can have multiple labels/tags assigned to each torrent. This way, when you Assign the label "(in Spork-Schivago's example) "Movies" you implicitly assign Spork's label "ISO" as well. This opens up many more filtering possibilities. For example, in a contact management application I use, there is a loose labeling scheme. I have labels for "Businesses", "Friends", "Family,", "Government", "NGOs", etc. I also have labels for specific cooperative groups of people I interact with on different subjects an teams of people within organizations. Then, I have labels for geographic region. Just taking the geographic region as an example, I have created labels such as "Africa" "West Africa" and "Cameroon". That is great, and I can assign all three labels to every contact in Cameroon, enabling me to filter by broad or narrow region, but this is tedious and error-prone. Especially since the same contact is also labeled in various other contexts besides region where I must do the same thing. So, I would argue that labels are much more useful than a strict folder/directory-only filing scheme, but they can be given the same features and we can have the best of both worlds. Some people achieve a compromise where they create labels such as "Africa/West Africa/Cameroon". That solves a sorting of labels issue; but it does not allow to filter for West Africa or Africa without filtering for a specific country. So, in short, I think this is a good and useful proposal, but not instead of allowing multiple labels :)
Author
Owner

@JinxDojo commented on GitHub (Jan 6, 2014):

Multiple labels/tagging is what we need: https://github.com/qbittorrent/qBittorrent/issues/13

@JinxDojo commented on GitHub (Jan 6, 2014): Multiple labels/tagging is what we need: https://github.com/qbittorrent/qBittorrent/issues/13
Author
Owner

@alfrix commented on GitHub (Feb 8, 2014):

@sledgehammer999 dupe of #13

@alfrix commented on GitHub (Feb 8, 2014): @sledgehammer999 dupe of #13
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#911
No description provided.