Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-3574

Missing ordering in works that are part of work

XMLWordPrintable

      We can't set the work parts order in a parent work in the work-work "part of" relationship (related to STYLE-69).

      example : 組曲「九尾」〜玉藻前〜照魔鏡〜殺生石 (all examples in MBS-3062 tag)

          [MBS-3574] Missing ordering in works that are part of work

          nikki added a comment -

          There's no need for multiple tickets trying to solve the same problem. MBS-3375 doesn't say anything about implementing it with sort names and actually proposes an attribute on the relationship. If you think the description isn't clear enough, ask someone to improve the bits you don't understand.

          nikki added a comment - There's no need for multiple tickets trying to solve the same problem. MBS-3375 doesn't say anything about implementing it with sort names and actually proposes an attribute on the relationship. If you think the description isn't clear enough, ask someone to improve the bits you don't understand.

          jesus2099 added a comment -

          Reopening because the later MBS-3375 seems to « propose a solution based on sortname which isn't the same at all. I wouldn't want a sortname nor anything based on a hackish work name, I would want a cardinality on AR. »

          jesus2099 added a comment - Reopening because the later MBS-3375 seems to « propose a solution based on sortname which isn't the same at all. I wouldn't want a sortname nor anything based on a hackish work name, I would want a cardinality on AR. »

          nikki added a comment -

          closing this in favour of the ticket which already has a number of votes and watchers

          nikki added a comment - closing this in favour of the ticket which already has a number of votes and watchers

          Oliver Charles added a comment -

          Ok, that's fair enough

          Oliver Charles added a comment - Ok, that's fair enough

          nikki added a comment -

          It is a server problem since the server does not support ordered relationships. Linking each part to the next part is just a hack - it doesn't work when some parts are missing (e.g. if parts 3 and 19 are in the database, we should be able to say that part 3 comes before part 19 even though part 19 is not the next part after 3) which requires twice as many relationships to be entered. It's also not just a problem for the parts relationship, other things like medleys and DJ-mixes should be ordered too.

          nikki added a comment - It is a server problem since the server does not support ordered relationships. Linking each part to the next part is just a hack - it doesn't work when some parts are missing (e.g. if parts 3 and 19 are in the database, we should be able to say that part 3 comes before part 19 even though part 19 is not the next part after 3) which requires twice as many relationships to be entered. It's also not just a problem for the parts relationship, other things like medleys and DJ-mixes should be ordered too.

          Oliver Charles added a comment -

          This doesn't seem to be a server problem - do we need an RFC on how this should happen? Should we add a "part of" relationship (next part/previous part)?

          Oliver Charles added a comment - This doesn't seem to be a server problem - do we need an RFC on how this should happen? Should we add a "part of" relationship (next part/previous part)?

            acid2 Oliver Charles
            jesus2099 jesus2099
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package