processing order issue between tagValue and tagFormat

[eseb63]

(29-03-2025 13:23)simoncn Wrote:  

Quote:I tried tagValue : Composer-Work.Merge={Work_Set}
this time, when browsing Composer-Work i get only the "4 ballades" entry and not the individual ballades ?

This is because you are merging Work_Set, which contains the single value "4 ballades".

I read again the documentation and maybe found my misunderstanding about indexFormat processing :

When specifying nothing in tagValue, indexFormat creates entries for each WORK and OVERALL_WORK, so in this case for each individual Ballade.

Specifying in tagValue "Composer-Work.Merge = {Work_Set} creates a single value "4 ballades" for Composer-Work.

I thought indexFormat would after that create individual ballades entries.

BUT according to the documentation, this tag won't be added if the item already has a tag occurrence.

I was wrongly reasoning in terms of tag value, when I should have been reasoning in terms of tag existence : am i right ?

If i use Composer-Work.Merge {Work_Set, Work} i get all but without prefix (for the same reason, indexFormat finds a tag and doesn't change it).

So, Composer-Work loses its usefullness and i will finally simply use Work.Merge={Work_Set, Overall_Work}, giving the same result.

I come from LMS, which shows all works grouped by composer. But after thought, directly browsing all works won't be very usefull and lisible : i endly will need to choose the composer.