Side effects of custom sort tag with alphabetical grouping

[eseb63]

my need was to handle these two use cases :

• if i know what i want to listen to (a Brahms trio), i choose Brahms as composer and pick the work in its first letter alphabetical group (T for Trio ...)
• if i want to listen to a trio but without knowing specifically which one, i choose Trio as Genre and want to list all works beeing trios, ordered by period and composer: I thought about using the alphabetical group T to retrieve the trios, then making a selection from the sorted list. However, as minimServer alphabetical groups are based on the sort tag first letter, it doesn't work.
  

So, i manage this another way:

• use case 1: Work_rated tag without a sort tag associated with it to use normally alphabetical grouping
• use case 2 : i create a Work_Listing index tag by script whose format is <Period> - <Composer> - <Genre> - <Work_Rated> and associate it with my sort tag. As all sort values start with a zero, alphabetical grouping is not shown : i can browse the ordered list and choose among the items.
  

the sort tag format is a bit different from the Work_Listing one:
<numPeriod><Period>§<Composer>§<Genre>§<Opus>§<Work>

• numPeriod : to sort the periods chronologically
• Opus : to sort the works in the opus order