Side effects of custom sort tag with alphabetical grouping

[simoncn]

The sort value is used to control the order in whch names appear in an index. For example, with these tags:

Artist: The Beatles
ArtistSort: Beatles, The

the artist The Beatles will appear among artists whose names start with B, not among artists whose names start with T. Alphabetical grouping doesn't change this sort order, so you will see The Beatles listed in the B section.

Each tag index value can only have one sort value. By adding a Z to the Work_Sort value of the single track, you are creating a conflict between two different sort values for the same index value. In this case, MinimServer ignores both conflicting sort values (it has no way to know which is "correct") and writes a message to the MinimServer log saying that it has done this. Because the sort values for this work have been ignored, you are seeing the work sorted under V.

Quote:I've noticed another problem: if I specify alphagroup="all", the indextags are correctly grouped alphabetically, except for Work_Rated:Work; omitting the alias doesn't change anything; I think this is another side effect of the Work_Sort tag.

I am not sure I have understood what you are saying here. There is no difference in sorting or grouping between specifying alphaGroup: all and alphaGroup: all=50.