To follow the DDEX (Digital Data Exchange) metadata scheme, a distributor must organize your upload into a specific hierarchy of data fields.
Here is the standardized list of fields required for a compliant DDEX message:
Message ID: A unique identifier for the data transmission.
Sender/Recipient Info: Identifiers for the distributor and the DSP (e.g., Spotify).
Timestamp: The exact date and time the message was created.
Resource Type: Identification as "Audio," "Video," or "Image".
Audio Requirements: 16-bit or 24-bit WAV/FLAC files at 44.1kHz.
ISRC: The International Standard Recording Code for each individual track.
Duration: The exact length of the audio file in ISO 8601 format.
Encoding Profile: Technical specifications of the audio file.
UPC/EAN: The barcode identifier for the entire release.
Release Title: The official name of the single, EP, or album.
Display Artist: The main artist name shown to the public.
Label Name: The imprint or entity releasing the music.
Genre: Primary and secondary genre classifications.
Release Date: The global start date for streaming (YYYY-MM-DD).
Full Legal Name: The real names of all contributors.
Role Codes: Standardized codes identifying contributors (e.g., Composer, Lyricist, Producer).
IPN/IPI: Identification numbers for performers and songwriters if available.
Territory Rights: A list of countries where the music is cleared for streaming.
C-Line (©): The copyright owner of the composition.
P-Line (℗): The copyright owner of the master recording.
Explicit Content Flag: Indication of explicit lyrics (True/False).
Pricing/Tier Info: Instructions for the DSP regarding subscription vs. ad-supported tiers.
Would you like me to show you how to map these DDEX fields to a MySQL database table for the CentricBeats distribution system?
