5.1 Introduction
This Part 3 of the ECM standard describes the choreography of the communication of duplicate ISRC cluster data, using two messages defined in Clause 6:
The
DuplicateIsrcClusterNotification; and
The
DuplicateIsrcClusterRequest.
In addition to these, Part 3 of the ECM standard makes use of two messages specified in Part 1, ECM Communication Protocol (ECM-C), namely:
A
Manifestthat may be used to communicate the messages defined in this Part 3 of the ECM message in batches; and
An
Acknowledgmentthat may be used to acknowledge the receipt of a message.
This Part 3 of the standard does not define the underlying transport, network, or messaging technology used to convey these messages. This is also specified in Part 1 of the ECM standard.
Figure 1 – Choreography for the DuplicateIsrcClusterNotification
The message exchange defined herein occurs between one sender and one recipient. The DuplicateIsrcClusterNotification message structure may be used for both the initial message and the response message (see Figure 1), ensuring a consistent and complete representation of the cluster at the two different times of exchange.
The DuplicateIsrcClusterRequest (Figure 2) is optional and may be used in specific workflows where the sender seeks to request the creation or specification of a Duplicate ISRC Cluster by specifying at least one member Resource that it anticipates will form part of a Duplicate ISRC Cluster subsequently created by the message recipient. The specified Resource may ultimately be determined to be the ClusterRoot or merely a ClusterMember.
For each Resource included in the request, the sender of the message shall provide sufficient information to enable identification of the Resource.
The response to a DuplicateIsrcClusterRequest shall be a DuplicateIsrcClusterNotification, which communicates the resulting cluster data to the requesting party.
Figure 2 – Choreography for the DuplicateIsrcClusterRequest
Table 1 below summarises the data exchange choreography and the points at which the messages defined in this part of the standard are sent.
Message Name | Initiating Event | Sender | Recipient | |
|---|---|---|---|---|
1 |
| A party, has identified a Duplicate ISRC Cluster and wishes to share the data with a business partner | Party wishing to send data about a Duplicate ISRC Cluster | Party wishing to receive data about a Duplicate ISRC Cluster |
2 |
| A party has received a | Recipient of a | Sender of the original |
3 |
| A party is requesting data about an ISRC and, potentially, its duplicates. The request can be sent at any point independently of a previous exchange of a | Party wishing to receive data about a Duplicate ISRC Cluster. | Party that may have data about a Duplicate ISRC Cluster. |
4 |
| A party has received a | Recipient of a | Sender of the |
Table 1 – Messages defined in Part 3 of the ECM standard

