Questions about tag formatting limitations

[eseb63]

(20-04-2025 22:57)simoncn Wrote:  I am investigating a possible fix for this issue with groups and indexFormat. Instead of having Work.indexFormat produce a single merged Work value for the group, it could apply Work.indexFormat to each item in the group and add all these formatted values to the group. In your example, the group groupW would have these tags:

WORK=work1 [Rating1]
WORK=work2 [Rating2]
WORK=work3 [Rating3]

This would give you the Work index entries that you want. Selecting any of these Work index entries would show the group, not the individual item, maintaining the principle that items within a group cannnot be accessed directly from outside the group.

Back after some holidays far from internet and minimServer...
good news, thanks a lot !

I still need some explanation about displayFormat with groups.

I ripped a CD Bach by Angela Hewitt, which contains:

• 1) Fantasia in C minor (1 track)
• 2) Two-Part Inventions (15 tracks)
• 3) Three-Part Inventions (15 tracks)
• 4) Chromatic Fantasia and Fugue in D minor (2 tracks)
  

Tagging :

• each Fantasia and Invention has a WORK tag
• each Invention track has a GROUP tag "Inventions à deux/trois voix"
• each Invention track has a WORK_SET tag "Inventions à deux voix (15)"
• each Invention track has a WORK_SET tag "Inventions à trois voix (15)"
• each Fantasia track has a WORK_RATING tag ♪♪♪♪
• 3 two-part Inventions have a different WORK_RATING tag (***, ****, *****)
  

MinimServer settings:

• indexTag : Work
• itemTag : Work_Set, Work_Rating
• tagValue : Group.Default={Work}, Work.merge={Work_Set, Overall_Work}
• tagFormat : Group.displayFormat={$composer^^ : $Overall_Work$Group^$Work_Rating^----------[^]}
  

What is displayed in album view:

• 1) Johann Sebastian Bach (1685-1750) : Fantasia en Ut m BWV 906 ♪♪♪♪----------[♪♪♪♪]
• 2) Johann Sebastian Bach (1685-1750) : Inventions à deux voix----------[***, ****, *****]
• 3) Johann Sebastian Bach (1685-1750) : Inventions à trois voix
• 4) Johann Sebastian Bach (1685-1750) : Fantaisie chromatique et Fugue en Ré m BWV 903----------[♪♪♪♪]
  

for 4) : displayFormat merges the WORK_RATING tag values of the group (created by default), which are the sames, so the result is as expected
for 2) : displayFormat merges the WORK_RATING tag values of the group (explicitely created), which are not the sames, so the result is also as expected
for 1) : there is also a group (created by default), with only one track : i don't understand why i get " ♪♪♪♪" before the expected "----------[♪♪♪♪]"

Any idea ?

[simoncn]

Your description doesn't say how Overall_Work is set. Please provide this information.

[eseb63]

(28-04-2025 19:54)simoncn Wrote:  Your description doesn't say how Overall_Work is set. Please provide this information.

Overall_Work is only used for works having two levels such operas (OVERALL_WORK="Carmen" , GROUP for each act) or by exemple Iberia Suite from Albeniz (OVERALL_WORK="Iberia", GROUP for each book).

it's not used for the Bach-Hewitt Album.

[simoncn]

I have set up a test to match what you said in your post and I don't see the issue. Instead of this:

1) Johann Sebastian Bach (1685-1750) : Fantasia en Ut m BWV 906 ♪♪♪♪----------[♪♪♪♪]

I see this:

1) Johann Sebastian Bach (1685-1750) : Fantasia en Ut m BWV 906----------[♪♪♪♪]

[eseb63]

weird, and with my data and settings?
(i didn't include the three-part inventions as they are not concerned and the zip file was too big)

[simoncn]

I tried using your files and your profile and the results were the same as in my test.

I couldn't apply your tag update file as you didn't include this. Could this be the reason for the difference in what we are seeing?

[eseb63]

Yes... I wrote this in update.tag before my holydays to see if updatetag could be an alternative, but unfortunately completely forgot about it: I apologize.

@WORK=Fantasy in C major BWV 906
&COMPOSER=Bach, Johann Sebastian (1685-1750)
=WORK=Fantasy in C major BWV 906 ♪♪♪♪

Another note: when testing multiple features, it's convenient to use profiles, but it's easy to forget which one is being used: it would be useful to display it under the MinimServer displayName, to avoid having to go to the profile section to check.

[simoncn]

(29-04-2025 11:13)eseb63 Wrote:  Another note: when testing multiple features, it's convenient to use profiles, but it's easy to forget which one is being used: it would be useful to display it under the MinimServer displayName, to avoid having to go to the profile section to check.

You can do this by editing the displayName property. The custom name will automatically be saved in the profile.

[eseb63]

I'm not sure if we're talking about the same thing: I'm talking about the server properties web page, for example, "http://192.168.2.100:9790/properties-server.html." This page doesn't mention the name of the active profile, but simply the displayName property.

Editing the displayName property doesn't solve the problem : you have to remember to edit the displayName property each time you change the profile, which you might forget to do. It would be more useful and secure to display something like this on the web page: displayName - activeProfile (or the profile name just below the displayName property). This information would be automatically updated when you switch profiles.

[simoncn]

Thanks for clarifying. As the current active profile name can be viewed with one click from the server status web page or properties page, I don't think any change is needed.