processing order issue between tagValue and tagFormat

[simoncn]

(29-03-2025 18:49)eseb63 Wrote:  Specifying in tagValue "Composer-Work.Merge = {Work_Set} creates a single value "4 ballades" for Composer-Work.

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

Quote: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.

These individual ballades entries are tagged as Work. My impression (perhaps incorrect) is that you are not including Work in either tagValue/merge or indexFormat, which would explain why these values are not merged into Composer-Work.

The merge option of tagValue merges all source tags specified, whether or not the item already has a value from a previously merged source tag. Some of the other tagValue options check for an already existing target or source tag but the merge option doesn't do this.

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

I don't think so - see above.

Quote: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.

MinimServer has a different approach for browsing ("intelligent browsing"). After making any tag selection, the next index shown is tailored using the results of previous selections. If you start by selecting a composer followed by a work, you will see only works for that composer. If you start by selecting a work followed by a composer (less likely but possible; you might only remember the work name), you will see only composers for the selected work. When you get used to this, you will find it very powerful and convenient because it progressively reduces the size of index lists you need to scroll though.