Refactor ISRC and ISWC tables to have one entry per ISRC/ISWC

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Normal
    • None
    • Affects Version/s: None
    • Component/s: Schema Change
    • None

      Currently our ISWC and ISRC tables store ISWC-work and ISRC-recording pairs, respectively. This means that even though we have pages such as https://musicbrainz.org/isrc/USSM19932777 (that can list multiple codes), there isn't one DB row nor one DB id for this ISRC.

      This is blocking MBS-7406 and would in general make our DB structure match the way we actually think about and use the codes.

      We should move the work and recording association out of the ISRC and ISWC tables, and onto their own iswc_work and isrc_recording tables.

            Assignee:
            Unassigned
            Reporter:
            Nicolás Tamargo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Version Package