6.2.3 Rules for update CatalogTransferMessages

In order for the acquiring record company to determine whether to send an update CatalogTransferMessage or to start a new catalogue transfer process, the acquiring record company shall take into consideration the information being communicated to it, by virtue of the ProposedActionType flag in any CatalogTransferConfirmation received from the DSP.

When sending an update CatalogTransferMessage, the acquiring record company shall also:

  1. Ensure that the CatalogTransferId is the same as that used in any CatalogTransferMessage(s) that are to be updated;

  2. Ensure that the IsUpdated flag in Figure 3 is set to true for all releases for which updated metadata is being provided;

  3. Ensure all releases for which no updated metadata is being provided are listed in the CatalogTransferMessage, with the IsUpdated flag omitted or set to false;

  4. Ensure that all identifiers provided for all elements of the releases are the ones currently used by the DSP;

  5. Ensure that no new identifiers for all elements of the releases are contained in the message;

  6. Ensure that, if required for the identification of the release, a ContainedPrimaryResource for each sound recording or video included in the release is included;

  7. Ensure, if a release contains multiple editions, for example, a stereo edition and an immersive edition, that have different metadata, for example, a different ISRC, that each edition is included in a separate ContainedPrimaryResource composite;

  8. Ensure that for each release there is at least one Deal in the message unless the acquiring record company wishes the existing deals, as previously communicated by the relinquishing record company to the DSP, to continue to apply; and

  9. Use the file naming convention defined in Clause 7.

The above rules, with the exception of rule 6.2.3(6), also apply to the update CatalogTransferMessage sent from the DSP to the relinquishing record company.