Behavior of Artist tag

[simoncn]

(09-05-2012 19:13)Raphaël Thévenin Wrote:  I noticed following behavior on my library:
- tags like performer, orchestra, conductor... which are added in the "userTags" property are added to the artist browsing
- the composer tag is not mixed with the artist browsing, maybe because it's a standard tag from minimserver ?

For me, there should be 2 different behavior (with a prop switch to choose ?) :
1 - I want minimserver to scan userTags and I want them to appear at topmost level for browsing as individual tags, but in this case, I don't want the tags to be miwed with "artists"
2 - I want minimserver to scan userTags, to be able to refine some searches, but I don't want my top level tree to be "polluted" by theses extra tags and I'm fine with mixing them in the "artists" tree entry

Best regards

RTh

It isn't possible to have different userTags in the top-level tree from those that appear in lower-level trees (your option 2). I'm not keen to change this (or provide a switch to change it) because one of the fundamental principles of MinimServer is that the browse selection should work in a consistent way whether it's at the top level or a lower level.

Your option 1) will be possible in the next release of MinimServer by removing Artist from indexTags (the new name for userTags). This will give you a separate index entry for each tag in indexTags, with no unexpected combinations.

The Composer tag isn't mixed into the Artist index entry because the artist information only includes performers.