Skip to end of metadata
Go to start of metadata

The Deal List provides the availability of the Releases. It describes when, where and how the releases can be made available. The Deal List provides a list of Release Deals, each having a reference back to a Release and defining the deal terms. Each Release Deal describes the commercial terms and usage information for each available Release. This includes the territories the Release can be made available, commercial model, usage type, pricing and deal validity period for each release listed. The deal start date usually represents the Release Date when the release can be made available to consumers in the specified territory.

Each Release Deal references back to the relevant Release using Release References. For example, the Release Deal for the Album Release references the Release identified by Release Reference R0, Track 1 by Release Reference R1, Track 2 by Release Reference R2, etc.

Within a Deal, a pre-order date can be specified. The pre-order date defines when the Release can be made available for pre-order, but not fulfilled to the consumer until the Deal start date. A pre-order preview date can also be specified. This defines if and when the preview clips can be made available to the consumer during the pre-order period.

Deals are also used to notify of Takedowns. A takedown is the blanket loss of all rights and can be applied to specific territories or all territories. A takedown implies that all previous deals are cancelled in the specified territories on the takedown deal start date.

The exact fields to to be used in a specific business case (e.g. describing a Ringtone Deal or a Subscription Download) is defined in the relevant Business Profile standard. More details on profiling can be found here.

  • No labels

4 Comments

  1. Anonymous

    All of the DDEX files that I have inspected have no ReleaseDeal for the Album Release R0.  They do include a ReleaseDeal referencing each Track of the Album (R1...Rx).

    Is this typical for the album not to have its own release deal?  In these cases should we use the "ReleaseDate" of the album, or the release date of a track to know when to make it available?

    1. Anonymous

      That depends on the commercial model types & usage types that are applicable between yourself, and who you're receiving DDEX ERN files from. 

      For example, if you are a streaming-only service... and you will be receiving some content providers will include ReleaseDeals for certain tracks... but would not include one for the album, since most people do not stream an entire album as a single unit.

      The idea of playlists and track streaming are... track based.

      You would use the <ValidityPeriod>.<StartDate> in the <Deal> section for each track (R1...Rx) noted in the XML, to know when to make each track available for use in your service.

      If all of the tracks of an album are available to you for use, you would find <DealTerms> that apply to all of the individual tracks.

  2. Anonymous

    Some of our DDEX XMLs have ONLY an R0 (with an embargo date) and no R1 at all. Also these xmls also stated this: <ReleaseType>VideoSingle</ReleaseType> and only had one <video> node listed.

    So is this XML incorrect? Should it have had an R1?

    Thanks

     

     

    1. Yes. ERN Messages must have Track Releases as well as the "album Release".