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

Report for different works with the same identifier attributes

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Reports
    • None

      These can often either be merged, have IDs wrongfully assigned (1 and 2), or have IDs that aren't actually IDs for the work itself (example).

      Possible query:

      SELECT wa1.work, wa2.work, wat.name, wa1.work_attribute_text
      FROM
        work_attribute wa1,
        work_attribute wa2
        JOIN work_attribute_type wat
        ON wa2.work_attribute_type = wat.id
      WHERE
        wa1.work_attribute_text = wa2.work_attribute_text
        AND wa1.work_attribute_type = wa2.work_attribute_type
        AND wa1.work < wa2.work
        AND wat.parent = 14;
      

      That currently returns 18983 rows, many of which seem to be false positives related to JASRAC. I'm no JASRAC expert, but they seem to assign the same code to different versions. Excluding JASRAC decreases it to 932 rows, so that might be more ideal to make the report actually actionable.

            Unassigned Unassigned
            ROpdebee ROpdebee
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Version Package