View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014214 | MMW 5 | DB / Backup | public | 2017-05-04 15:19 | 2023-06-28 21:15 |
| Reporter | jiri | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | reopened | ||
| Summary | 0014214: Hierarchical genres implementation | ||||
| Description | For easier navigation in lots of genres, it might be useful to present Genre in a 2-level hierarchy, where the top level would be represented by the main genre categories (Rock, Pop, R&B, ...) and the 2nd level would be the actual genre. Note that a genre could easily belong to two categories (e.g. 'Jazz Rock' would be both in Jazz and in Rock). UI: 1. Create new Genre Categories view, to be available in the Genre node. 1b. So, user will be able to choose between the classical Genres view and the new Genre Categories view in the Genre node. 2. After clicking a Genre Category, navbar would be like 'Genres > Rock genres' and present the Genres within the 'Rock' category. 2b. Or, user can change to another view which could e.g. present all the Albums in the 'Rock' category (ordinary Albums view applied to the particular genre - as already planned to be implemented) DB/Technical: 11. We'd need a hard-coded list of genre-category relationships. It can be stored in the DB, for better transparency, but can be somewhere in our code as well. 11b. We can use https://en.wikipedia.org/wiki/List_of_popular_music_genres as a starting point for this list. We possibly could split some very broad categories and create e.g. Punk and Heavy Metal from Rock and possibly also make some more categories of the Electronic category. Anything not matched would be assigned to Other category. 12. Each genre would get a category assigned in the Genres table. Could be even a text column Category. This would be based on the hardcoded list above (11.). I don't think we need to give user a way how to edit this assignment, maybe an Addon would be created later. 12b. This should be enough to be able to execute (fast) all the necessary queries to create the UI as proposed above. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2066 | ||||
|
|
Added in 2066 |
|
|
UI: 3. Add "Genre tree" option like "Playlist tree" for playlist 1, 2 Verified 2066 |
|
|
3. I don't think it's needed, at least not until this functionality matures a bit. I'd consider adding 'Genre Family' option to Column Browser though, in order to be able to easily browse genres. The same for Filtering/Search/Auto-Playlists. |
|
|
I don't think that 'Genre catgories' view is used much, so resolving as "no change required"... |
