Bug 238836

Summary: Feature request: Allow to specify additional collection folders which appear separatedly in the collection browser
Product: [Applications] amarok Reporter: Jochen Bauer <skywalker_99>
Component: Collections/LocalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: marc
Priority: NOR    
Version: 2.3.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jochen Bauer 2010-05-26 00:09:17 UTC
Version:           2.3.0 (using KDE 4.3.5) 
OS:                Linux



Reproducible: Didn't try
Comment 1 Jochen Bauer 2010-05-26 00:15:37 UTC
Sorry for my mistake filing that Bug. Somehow the focus switched to the submit Button too early.

I was really glad if you could implement the possibility to specify additional folders which are treatened as a completedly separated collection. 

That would be great for users like me, who have a "main collection" which includes the well-tagged Albums and Songs and an other folder where the Music is messed up. 

Atm I don't include my untidy music folder in amarok's collection to avoid messing up my well-tagged music. That music can now only be accessed via the integrated Browser, where filtering and sorting is impossible. 

With a second collection these Problems will vanish immediately.
Comment 2 Marc Ermshaus 2010-06-14 22:00:43 UTC
It would also allow to split a library into separated subcategories like "classical music", "audio books", "own recordings", or "popular music". Items from different categories don't mix well in terms of grouping by artist or in random playlists.

This might be combined with the existing filter interface. If a set of filters could be stored as a top level item in the collection browser, it would be possible to create filtered views like:

- include-dir:"~/music/own-recordings" AND year="2010"
- include-dir:"~/music/classical"
- ...

Maybe worth a thought. Thanks for reading! --Marc
Comment 3 Myriam Schweingruber 2010-06-15 00:03:42 UTC

*** This bug has been marked as a duplicate of bug 197573 ***