DDEX Feed Delivery Spec

Here are the specifications and requirements for DDEX feed deliveries to Labelcamp.

DELIVERY SET UP

After receiving your S3 bucket login information from our support team, you will be able to make deliveries in your assigned bucket.

DELIVERIES

Our DDEX information:

• DDEX Party Name: Labelcamp

• DDEX Party ID: PADPIDA2011111602K

File Formats

Depending on the context, you can deliver:

• audio files (FLAC preferred, but we also support WAV, most bitrates accepted except over 48khz for 16-bit audio),

• booklets (PDF required, in accordance with Apple requirements),

• cover arts (JPEG required, square format, min 3000px - max 4500px, RGB color space, max size 20MB),

• and metadata XMLs.

DDEX specifications

Deliveries are validated through the DDEX XSD and are rejected if not compliant.

We expect deliveries to be compliant with versions of the DDEX ERN 3.8 specifications. We will validate them according to the related XSD schema, as in the example here: http://service.ddex.net/xml/ern/41/release-notification.xsd

We may also support other DDEX versions, but please let us know in advance which version you would like to use to confirm that we can support it.

Release LabelName

We expect strict "LabelName" in your XMLs. Make sure to deliver releases with identical LabelName when they belong to the same label. Otherwise, if it is not recognized as an existing label from your Labelcamp's catalog, it will automatically create a new Label.

Note that there's a little tolerance on the casing, eg. "My Label" will be considered identical with "my label".

→ In Labelcamp, a "Label" can be linked to a "Contract", which is meant to represent a distribution deal or legal entity, and can be used to group multiple "Labels" per Contract (a useful functionality for sales reporting and distribution management). Our support can help you map the Labels identified in the XML deliveries with your Labelcamp’s Contracts.

BATCH REQUIREMENTS

All Batch folders should be named using the file naming convention outlined per the DDEX ERN Choreography Standard, where each Batch is identified by the date and time of its creation in the form 'YYYYMMDDhhmmssnnn':

• 'YYYY' represents the year in which the Batch is created

• 'MM' represents the month in which the Batch is created

• 'DD' represents the day on which the Batch is created

• 'hh' represents the hour in which the Batch is created

• 'mm' represents the minute in which the Batch is created

• 'ss' represents the second in which the Batch is created

• 'nnn' represents the millisecond in which the Batch is created

Please ensure that each BatchID is unique.

SERVER ORGANIZATION

Each Batch should go into its own Batch folder, named with the BatchID as outlined above.

All releases included within that Batch are required to be placed in their own Release folder named with the product's ReleaseID (e.g. UPC). The release's sound recording files should go into a subfolder called "resources/".

Here is an example of the batch structure supported by our system.

Root/

|-- 20100310130322000/

| |-- 3663729899990/

| | |-- 3663729899990.xml

| | |-- resources/

| | | |-- 3663729899990_T1_001.flac

| | | |-- 3663729899990_T2_002.flac

| | | |-- 3663729899990.jpg

| |-- 3663729899998/

| | |-- 3663729899998.xml

| | |-- resources/

| | | |-- 3663729899998_T1_001.flac

| | | |-- 3663729899998_T2_002.flac

| | | |-- 3663729899998.jpg

| |-- BatchComplete_20100310130322000.xml

|-- acknowledgments/

| |-- ACK_3663729899990.xml

| |-- ACK_3663729899998.xml

The ManifestMessage/BatchComplete file must be placed into the BatchId's root folder as seen in the above example (BatchComplete_20100310130322000.xml).

FTP ACKNOWLEDGEMENT MESSAGES

After any successful ingestion, we will place FtpAcknowledgementMessages into the acknowledgements folder located at the root path.

→ Please consult the acknowledgement file for each release sent and redeliver the content if a modification is required on your side.

FILE NAMING CONVENTION

The ManifestMessage's file name for each Batch should align with the following naming convention: BatchComplete_BatchId.xml (e.g. BatchComplete_20100310130322000.xml).

SUPPORTED DELIVERY TYPES

We support the following DDEX messages:

• delivery for insert of new products,

• update for an update regarding metadata only,

• redelivery for an update regarding assets (cover, booklet, audios, videos),

• delete for a takedown from the platform.

MUSIC GENRES

Standard Feed Delivery

We accept all Music Genres. However, if the genre set on the album isn't part of your Labelcamp's Genres grid, it will be subject to additional manual mapping. Please make sure to only use existing genres from your list in Labelcamp.

Feed Delivery for Trends-only Clients

We expect to receive Genres from the following master list to ensure a functional ranking for Genres. Otherwise, the genre will not be considered:

• Alternative/Indie

• Audio Book

• Children's / Educational

• Classical

• Country

• Electronic

• Hip-Hop/Rap

• Inspirational / Religious

• Instrumental

• Jazz / Blues

• Miscellaneous (Comedy / Fitness / Holiday / Karaoke / etc.)

• New Age / Spiritual

• Pop / Rock

• R&B/Soul/Funk

• Reggae

• Singer/Songwriter / Folk

• Soundtrack

• Spoken Word

• World