5.2.2 Step 2

Once the DSP has confirmed the details of the catalogue transfer with the relinquishing record company (see Clause 5.2), the DSP shall (i) update its internal systems to effect the catalogue transfer on the effective date and (ii) confirm that status to the acquiring record company.

This confirmation, depicted as step (2a) in Figure 1, is communicated by the DSP to the acquiring record company using the CatalogTransferConfirmation. The CatalogTransferConfirmation shall contain metadata about the same list of releases as appeared in the CatalogTransferMessage originally received by the DSP from the acquiring record company, with each of those releases assigned to one of the following categories:

  1. All releases of the relinquishing record company, as identified by the acquiring record company in the CatalogTransferMessage, where the DSP has confirmed that the catalogue transfer of those releases can be enacted by a reassignment of rights controller information;

  2. All releases of the relinquishing record company, as identified by the acquiring record company in the CatalogTransferMessage, where the DSP has rejected, at least initially, that the catalogue transfer of those releases can be enacted by a reassignment of rights controller information. It may be possible that the processing of those rejected releases can take place using DDEX’s 2021 Catalogue Best Practices; and

  3. All releases of the relinquishing record company, as identified by the acquiring record company in the CatalogTransferMessage, where the DSP has been unable to determine whether or not the catalogue transfer can be enacted by a reassignment of rights controller information and those release are therefore listed as pending.

All releases listed in the CatalogTransferMessage as received by the DSP shall be listed in the CatalogTransferConfirmation and shall appear in either the ConfirmedReleaseList ((1) above), or the RejectedReleaseList ((2) above) or the PendingReleaseList ((3) above).

The DSP may use the CatalogTransferStatus tag (see Figure 4) of the CatalogTransferConfirmation to mark the entire catalogue of releases that is the subject of the catalogue transfer as Confirmed, Rejected or Pending. If the DSP sets the CatalogTransferStatus tag to either Confirmed or Rejected, it shall ensure that all releases listed in the CatalogTransferConfirmation are either in the ConfirmedReleaseList or the RejectedReleaseList as the case may be. If there is a conflict between the value in the CatalogTransferStatus tag and the various release lists, the latter shall take precedent.

The DSP is expected, subject to bilateral agreements, to keep sending updated CatalogTransferConfirmations until no releases are in the PendingReleaseListdepicted as step 4(a) in Figure 1. In those updates, releases that have previously been communicated in the RejectedReleaseList may be moved to the ConfirmedReleaseList. However, once a release has been communicated in the ConfirmedReleaseList, it cannot be subsequently communicated in the PendingReleaseList or as not being part of the catalogue transfer.

Details of the data to be provided in the CatalogTransferConfirmation are defined in Clause 5.3.

Search