Multiple consecutive deals

Record companies sometimes require that a DSP makes available a release under terms and conditions that may change over time. For example, the recommended retail price may change before, during, or after a specific event (Christmas, a sports event, etc).

The examples on this page use the syntax of ERN-3. The only difference for ERN-4 would be the order of the subelements of DealTerms.

In such circumstances the DealList section needs to contain several deals the dates for which are consecutive without any gaps, i.e. as soon as one deal ends the other deal starts. This can be effected with both dates and date-times. If two subsequent periods form a continuum (i.e. with no break in-between) there are two ways to express this:

  • if using dates, the EndDate of the first ValidityPeriod must be one day before the StartDate of the second ValidityPeriod; and

  • if using datetimes, the EndDateTime of the first ValidityPeriod must be the same string as the StartDateTime of the second ValidityPeriod.

In both examples, below, the price of the release increases from 500 Islandic Króna to 1,000 Islandic Króna at midnight between 31st January and 1st February 2018: 

 Consecutive Deals with Dates
<DealList>
    <ReleaseDeal>
        <DealReleaseReference>R1</DealReleaseReference>
        <Deal>
            <DealTerms>
                <Usage>
                    <UseType>Download</UseType>
                </Usage>
                <TerritoryCode>IS</TerritoryCode>
                <PriceInformation>
                    <SuggestedRetailPrice CurrencyCode="ISK">500</SuggestedRetailPrice>
                </PriceInformation>
                <ValidityPeriod>
                    <StartDate>2018-01-01</StartDate>
                    <EndDate>2018-01-31</EndDate>
                </ValidityPeriod>
            </DealTerms>
        </Deal>
        <Deal>
            <DealTerms>
                <Usage>
                    <UseType>Download</UseType>
                </Usage>
                <TerritoryCode>IS</TerritoryCode>
                <PriceInformation>
                    <SuggestedRetailPrice CurrencyCode="ISK">1000</SuggestedRetailPrice>
                </PriceInformation>
                <ValidityPeriod>
                    <StartDate>2018-02-01</StartDate>
                </ValidityPeriod>
            </DealTerms>
        </Deal>
    </ReleaseDeal>
</DealList>
 Consecutive Deals with datetimes
 <DealList>
    <ReleaseDeal>
        <DealReleaseReference>R1</DealReleaseReference>
        <Deal>
            <DealTerms>
                <Usage>
                    <UseType>Download</UseType>
                </Usage>
                <TerritoryCode>IS</TerritoryCode>
                <PriceInformation>
                    <SuggestedRetailPrice CurrencyCode="ISK">500</SuggestedRetailPrice>
                </PriceInformation>
                <ValidityPeriod>
                    <StartDateTime>2018-01-01T00:00:00Z</StartDateTime>
                    <EndDateTime>2018-02-01T00:00:00Z</EndDateTime>
                </ValidityPeriod>
            </DealTerms>
        </Deal>
        <Deal>
            <DealTerms>
                <Usage>
                    <UseType>Download</UseType>
                </Usage>
                <TerritoryCode>IS</TerritoryCode>
                <PriceInformation>
                    <SuggestedRetailPrice CurrencyCode="ISK">1000</SuggestedRetailPrice>
                </PriceInformation>
                <ValidityPeriod>
                    <StartDateTime>2018-02-01T00:00:00Z</StartDateTime>
                </ValidityPeriod>
            </DealTerms>
        </Deal>
    </ReleaseDeal>
</DealList>

Note that it is not recommended to use 2017-01-31T24:00:00Z and 2018-02-01T00:00:00Z as the end of the first ReleaseDeal and the start of the second ReleaseDeal even if they denote the same moment in time. Instead, the same string should be used for both datetimes.

Search