Guides and Resources
Start typing to search…

Testing Process for DDEX Delivery

This guide walks suppliers through the testing process for delivering audio content to MassiveMusic. We require specific samples for each testing stage to ensure your content integrates smoothly with our platform. Please adhere to the instructions carefully to avoid delays.

General Instructions

1 Deliver Only the Required Samples: Deliver only the samples requested for the current testing stage.

2 Use One UPC Per Test: Use a single UPC to test each scenario end-to-end.

3 Delivery Method: Deliver the test sample as you intend to deliver your full catalogue to us. You can use either batch delivery or release-by-release delivery.

  • Batch Delivery: Upload multiple releases in a single batch to the SFTP including the batch complete file. The batch complete file name should start with batchcomplete and is case insensitive and it should be delivered after all other files are uploaded.
  • Release-by-Release Delivery: Upload each release individually to the SFTP.

4 Avoid Delivering Extra Releases: Delivering more releases than requested or sending inserts and updates simultaneously can interfere with the tests and cause delays.

Testing Process for a Single Release

The single release should consist of no more than two tracks. If a delivery exceeds this limit, it will not be progressed, and you will be asked to resubmit.

  1. Insert:
  • Deliver a new product: Ensure this is a completely new product for the platform, not already held by us.
  • Future release date: Set the StartDate in the future to avoid conflicts.
  • Upload to SFTP: Deliver the insert sample to our SFTP.
  1. Update (Release Date Change):
  • Wait for validation: We will request an update once your insert passes validation.
  • Change release date: Update the StartDate to a past date to make it live in our testing environment. There is no need to deliver assets with this update.
  • Upload to SFTP: Deliver the updated release date sample to our SFTP.
  1. Takedown:
  • Deliver end date: Provide an endDate to take down the release.
  • Confirm takedown: Wait for confirmation that the release has been taken down successfully.
  • There is no need to deliver assets with this update.
  • Proceed to Album testing: Once confirmed, we can begin testing an album release.

Testing Process for an Album Release

Follow the steps below for testing an album, ensuring it consists of more than 2 tracks and is a single disc release.

  1. Insert:
  • Deliver a new album: Ensure the album is a completely new product for the platform, not already held by us.
  • Future release date: Set the release date in the future to avoid conflicts.
  • Upload to SFTP: Deliver the insert sample to our SFTP.
  1. Update (Release Date Change):
  • Wait for validation: Once your album insert passes validation, we will request an update.
  • Change release date: Update the release date to a past date to make it live in our testing environment. There is no need to deliver assets with this update.
  • Upload to SFTP: Deliver the updated release date sample to our SFTP.
  1. Takedown:
  • Deliver end date: Provide an end date to take down the album.
  • Confirm takedown: Wait for confirmation that the album has been taken down successfully. There is no need to deliver assets with this update.

Testing Process for a Multi-Disc Release

Follow the steps below for testing a multi-disc release, ensuring it consists of multiple discs and tracks.

  1. Insert:
  • Deliver a new multi-disc product: Ensure this is a completely new product for the platform, not already held by us.
  • Future release date: Set the release date in the future to avoid conflicts.
  • Upload to SFTP: Deliver the insert sample to our SFTP.
  1. Update (Release Date Change):
  • Wait for validation: Once your multi-disc insert passes validation, we will request an update.
  • Change release date: Update the release date to a past date to make it live in our testing environment. There is no need to deliver assets with this update.
  • Upload to SFTP: Deliver the updated release date sample to our SFTP.
  1. Takedown:
  • Deliver end date: Provide an end date to take down the multi-disc release.
  • Confirm takedown: Wait for confirmation that the multi-disc release has been taken down successfully. There is no need to deliver assets with this update.

Testing Process for Large Batch Delivery or Multiple Releases

Follow the steps below to test the delivery of a large batch of releases or multiple releases via the release-by-release method. These can be releases intended to go live on the platform. We do not require you to update or take down this content.

  1. Batch Delivery:
  • Deliver a large batch of releases: Upload multiple releases in a single batch to the SFTP including the batch complete file.
  1. Release-by-Release Delivery:
  • Deliver releases individually: Upload each release one by one to the SFTP.
  1. Validation and Confirmation:
  • Wait for validation: We will ensure that each release, whether delivered in batch or individually, passes our validation checks. Once we can verify that all your releases are live on the platform we will move you feed onto our automated ingestion system and you can commence delivery of your backfill.

Backfilling Your Catalogue

Once you have completed the testing, you can commence the backfilling of your catalogue.

  1. Daily Rate Limit: We have a rate limit of 30,000 XMLs per day per feed. This can be made up of inserts, updates, and takedowns.
  2. Scaling Your Feed: If you anticipate requiring more than this daily cap for your backfill, please let us know. We can work with you to scale your feed during the backfilling process to prevent delays or bottlenecks.

By following these steps precisely, you ensure a smooth testing and backfilling process, allowing us to validate your content and prepare it for successful integration with MassiveMusic's platform.

Updated 5 months ago