Systems Architecture, DDEX & Metadata Integrity

6.1 Universal Music Identifiers

Building scalable, production-ready software for music administration requires a robust metadata architecture that integrates with global music registries. You must understand and map three core identifier classes:

• ISRC
  International Standard Recording Code (ISRC):

  An ISRC uniquely identifies a specific sound recording or music video recording, not every physical or digital distribution of that recording. Under standard copyright practices, a remaster, new recording, or materially different version of a track generally receives a new ISRC.

• ISWC
  International Standard Musical Work Code (ISWC):

  An ISWC uniquely identifies the underlying musical work (the intellectual composition, lyrics, melodies, and arrangements), rather than the physical or digital recording itself.

• IPI
  Interested Party Information Number (IPI):

  An IPI is a unique identifier assigned to interested parties (songwriters, composers, lyricists, and publishers) within the CISAC member systems, mapping rights holders to registration records.

6.2 Identifier Relationships and Relational Schema

In music rights management, a single underlying composition (ISWC) often relates to multiple separate sound recordings (ISRCs)—such as remixes, cover versions, or live performances. While a sound recording normally references one musical work, complex recordings like medleys, mashups, or classical arrangements may reference multiple works. Because of these variations, this relationship should be represented as a flexible relational mapping rather than an absolute one-to-many rule.

{
  "MusicalWork": {
    "iswc": "T-030.294.812-5",
    "title": "Neon Horizon",
    "alternate_titles": ["Neon Horizon (Original Mix)"],
    "writers_and_publishers": [
      {
        "ipi": "00839485712",
        "legal_name": "Maria Korhonen",
        "role": "Composer/Author",
        "pro_affiliation": "TEOSTO",
        "performance_split_percentage": 50.00,
        "mechanical_split_percentage": 50.00,
        "publisher": {
          "ipi": "00921475833",
          "name": "Horizon Creative Publishing"
        }
      }
    ],
    "sound_recordings": [
      {
        "isrc": "US-A1B-26-01234",
        "recording_title": "Neon Horizon (Original Mix)",
        "duration_seconds": 245.00,
        "upc": "190294857214"
      },
      {
        "isrc": "US-A1B-26-01235",
        "recording_title": "Neon Horizon (Radio Edit)",
        "duration_seconds": 180.00,
        "upc": "190294857221"
      }
    ]
  }
}

6.3 Industry Registries and APIs

Many commercial APIs and databases require licensing agreements, authentication credentials, rate limits, and contractual access. Developers use these integrations to query, normalize, and match catalog data:

6.4 DDEX Electronic Release Notification (ERN) Standards

DDEX Electronic Release Notification (ERN) standards evolve over time, and different distributors and DSPs may support different schema versions during transition periods. Implementations of these XML protocols vary across trading partners.

<?xml version="1.0" encoding="utf-8"?>
<ERNMessage xmlns="http://ddex.net/xml/ern/43" MessageSchemaVersionId="ern/43">
  <MessageHeader>
    <MessageId>MSG-20260717-001</MessageId>
    <SenderPartyId>DPID:PADPIDA202612345</SenderPartyId>
    <ReceiverPartyId>DPID:PADPIDB202654321</ReceiverPartyId>
  </MessageHeader>
  <ResourceList>
    <SoundRecording>
      <ResourceReference>A1</ResourceReference>
      <SoundRecordingId>
        <ISRC>USA2Y1800124</ISRC>
      </SoundRecordingId>
      <DisplayTitle>
        <TitleText>Neon Horizon</TitleText>
      </DisplayTitle>
      <Duration>PT4M5S</Duration>
    </SoundRecording>
  </ResourceList>
</ERNMessage>

6.5 Database Normalization in Production Music Platforms

A production-ready music administration platform typically stores operational business data (such as subscriber accounts, marketing stats, or active carts) separate from core catalog identifiers. High database normalization is critical in rights management to prevent duplicate metadata, maintain data integrity, and simplify complex royalty calculations.

A fully normalized schema typically allocates separate, relational database tables for:

By isolating these domains into normalized tables connected via foreign keys, a platform ensures that a correction to a composer's IPI or a track's ISRC immediately cascades across all linked releases and royalty statements without risking mismatched records.

Systems Disclaimer: The metadata models and examples shown here are simplified educational representations of common music industry data structures. Actual production implementations vary among distributors, collection societies, DSPs, and enterprise rights management platforms.