Has there been any discussion of adding a set of tables (with corresponding service and UI changes) to support the concept of a composition? This is particularly important in classical music. Due to it’s complexity, it would need to be a full-fledged high-level entity that allows many-to-many mapping relationships to movements/parts, tracks, and releases. I didn’t see anything like this in the schema diagram, but haven’t been able to get to the FTP site to see if it happens to be in the database schema anyway (but not documented).
The reason I mention it is that this is not the kind of data that is easy to maintain in tags alone. A single track may represent just one part of a movement of a larger composition. Compositions may span discs and a release may have multiple multi-part compositions. My desire is to fully represent how a track relates back to a composition (if there is one), so ultimate meaningful tags can be applied downstream to actual files.