A case of mis-identification of classical work

[kr]

In an earlier thread I reported hundreds of cases of Songkong misidentifying what should be grouped together as a classical work. I am in the process of rerunning SK over my whole library and am happy to report that “hundreds” is now reduced to just one single case! But as I am at a loss to understand why it fails for just this single work (*) I thought i would ask. The 24 Chopin preludes form part of a collection, but are not a “work” in the classical performance sense of an entity to necessarily be performed together in sequence. The overall MBID, https://musicbrainz.org/work/d1f6b371-c9b4-4c6e-bb85-16bcfc369d5e does not have a “type”, so I thought would not be considered for this. Any thoughts on what the distinctive factor here might be?

There’s a log file on its way.

(*) - There are actually two albums with the complete Chopin 24 Preludes by the same performer and both behave in the same manner.

[paultaylor]

@kr

I am in the process of rerunning SK over my whole library and am happy to report that “hundreds” is now reduced to just one single case!

Your comprehensive testing and Classical knowledge has been very useful for improving SongKong classical support, thanks.

It is because the Work Type logic we added was for multi level works e.g if we have an Opera and each track is a recording of a Scene, and that scene is part of an Act, then if the Act was part of something larger we check it is of type Opera/Concerto ecetera before allowing it.

In this example we are only going up to equivalent of Act level and we don’t check the type at this level. Whether or not we should I’m not sure but I don’t think so because there are going to be too many cases where the Work Type is not set when it should have been so if had to be a certain type it would prevent Work getting set.