5.2 Definition of the Sales/Usage Report structure where release data is available

When sales and/or usage data is to be reported using the Basic Audio Profile for The Mechanical Licensing Collective of the DSR standard, where release data is available to the licensee, the following Records shall be communicated in this order:

1. One HEAD Record.

2. One or more summary Records of type SY01.03 or SY12.01.

Which of these summary Records is used is determined by which commercial model the licensee uses, which type of use and which territory any release contained in the Sales/Usage Report has been traded in. The summary records are described in detail in Part 8 of the DSR standard. It is permissible to communicate different types of summary Records in a single Sales/Usage Report.

It is recommended that the summary Records are provided in a logical order to aid human readability. This would typically mean that summary Records with the sames Record identifier are not mixed up even if the Record identifiers may not appear in their numerical order. For example a sequence of SY01.03 SY01.03 SY12.01 meets this recommendation, whereas SY01.03 SY12.01 SY01.03 does not.

3. One or more Blocks that contain the following Records:

(a) One Record of type RE04.01:

This Record provides data describing a Head Release. If the licensee has received a NewReleaseMessage defined in DDEX’s Electronic Release Notification Message Suite, the Head Release for the purposes of a Sales/Usage Report created in accordance with this profile is the Album Release as defined in the NewReleaseMessage.

(b) One or more Records of type AS06.01.

Each of these Records provide data describing each sound recording, music video or other resource that is contained in the Head Release and basic details about the musical work(s) that are embodied in each such sound recording, music video or other resource.

Only a resource (that is sound recording, music video or other resource) that has been sold or used shall be included in the AS06.01 Record in this section of the Block. For the avoidance of doubt, if a Block is describing a Head Release that has been sold or used, which contains multiple resources, all the resources that embody musical work(s) that are contained in that Head Release need to be included in multiple AS06.01 Records in the Block.

(c) Instead of using an AS06.01 Record the licensee may wish to present the data in two Records. This is achieved as follows:

(i) One or more Records, of type AS05.01.

Each of these Records provide data describing each sound recording, music video or other resource that is contained in the Head Release, but without any details about the musical work(s) embodied in that sound recording, music video or other resource.

Only a resource (that is sound recording, music video or other resource) that has been sold or used shall be included in the AS05.01 Record in this section of the Block.

(ii) None, one or more Records of type MW02.01.

Each of these Records provide data describing the musical work(s) embodied in the sound recording, music video or other resource (as described in each of the AS05.01 Records).

If the Block containing an AS05.01 Record followed by MW02.01 Record(s) is describing a Head Release that has been sold or used, which contains multiple resources, all the resources that embody musical work(s) that are contained in that Head Release need to be included in the Block. This is achieved by stringing together multiple AS05.01 + MW02.01 pairs of Records.

This is shown in Figure 1, where the musical work Records (MW02.01) are interspersed with the resource Records (AS05.01). The MW02.01 Records immediately following an AS05.01 Record describes the musical work(s) described in that resource.

MW02.01 Records may not be used in combination with AS06.01 Records.

AS05.01 + MW02.01 and AS06.01 Records may be used together within a single Block. One example would be where the licensee communicates the writers of ten tracks to the licensor but where the eleventh track is a medley created by the licensee comprising multiple musical works.

(d) None, one or more Records of type RC01:

Each of these Records provide data describing the rights controller of the musical work(s) described in the AS06 or MW02 Records. The RC01 Record shall therefore point to the AS06.01 or MW02.01 Record detailing the musical work(s) for which rights controller data is provided. The data provided in these Records is that which is, to the best of the licensee’s knowledge, applicable at the time the Sales/Usage Report was created.

(e) None, one or more Records of type RE02:

Each of these Records provide data describing Sub-Releases. These Sub-Releases are either single resource Track Releases (as communicated in a NewReleaseMessage) and/or releases that the licensee has generated exclusively from the resources that are used in the Head Release. The Sub-Release Records shall point to the resources they make use of. Only Sub-Releases that have been sold or used shall be included in this section of the Block.

(f) One or more Records of type SU01.03 or SU02.03:

These Records provide data describing sales and/or usage of the Head Release or Sub-Release described in the Block. Which sales and/or usage Record is to be used for a particular Sales/Usage Report is determined by the commercial model and use type the licensee is using. Each SU Record shall point to the Head Release, Sub-Release Record to which the sales and/or usage data relates.

4. One FOOT Record.

Figure 2 – Layout of the Basic Audio Profile for the Mechanical Licensing Collective where release data is available

Figure 2 depicts the layout of this profile where release data is available. In that diagram the illustrative Block contains a Head Release (the RE04.01 Record) with four resources, three of which (the AS06.01 Records) include musical work data in the resource Record. Also, one resource (the AS05.01 Record) is augmented by musical work data in an MW02.01 Record is shown. Sales and/or usage data is then reported for one Sub-Release as well as for the Head Release.

In the diagram the first SU Record provides sales and/or usage data for the Sub-Release, the second SU Records provide sales and/or usage data for an individual resource, such as a sound recording (e.g. for streaming), and the last SU Records provide sales and/or usage data for the Head Release. The first SU Record therefore points to the RE02 Record which, in turn points to multiple AS Records identifying the resources in the Sub-Release. The third SU Record points to the RE04.01 Head Release Record.

The indentation in the figure above is solely for illustration purposes. There is no indentation in the Sales/Usage Report created in accordance with this part of the DSR standard.

The table below provides an overview of the order and cardinality of the Records to be used in this profile where release data is available.