Using series entity to store work related data

[ListMyCDs.com]

@Dibou

alternative would have been be to create a (sub-)Work for each Livre

I fail to see benefits of storing this data on series entity. Now data about the work is split between 2 different entities. Currently it’s well hidden: full structure can’t be seen on (main) work page and it’s no way related to composer (there’s no relationship types for this).

I don’t understand how more complex tree structures should be divided between these entities. Instead of trying to fit this data into series (by adding new relationship types with some UI changes) we could improve the current work entity. For me it would make more sense to store all work related data with work entities without trying to store data which is only related to structure with another entity.

@Dibou

Personally, I do not like such a multiplication of Works, when it is just a way to structure a rather complex Work made of several parts, sub-parts, etc., like an e.g. operas, set of songs, suites,

I believe there’s quite many of us who believe that work structures could be handled somehow differently. Pretty long discussion about it already started on another topic. Levels in the structure of works. Topic is pretty long but I recommend checking it if you haven’t already done so.

@Dibou

Should then the Études works be related to both upper-level Works: to the intermediate one Livre and to the top one Douze Études ?

I see no reason to do that. I guess with this we just need to trust common sense. If opera has acts, parts of act are also part of opera. People should be able to understand this without linking all pieces with act and the main work. That’s how hierarchies in tree structures work.