ERN 3 structure

NewReleaseMessage

The NewReleaseMessage includes complete data about releases and all resources contained within those releases. In addition, it includes deals that describe when, where and how the release can be made available.

The NewReleaseMessage consists of seven individual sections of message and data elements that are interrelated. In the diagram above the four most important sections are shown and these perform exactly the same function in ERN 3 as they do in ERN 4. Explanations of these can be found here.

The remaining sections of the NewReleaseMessage are:

  • WorkList

    • This can be used to provide any information the record company or distributor may have about the musical works embodied on the sound recordings or music videos that make up the releases described in the message.

  • CueSheetList

    • This can be used to provide details of any cue sheets contained in the release described in the message.

  • CollectionList

    • This can be used to provide details of any collections of resources contained in the release described in the message.

A NewReleaseMessage should only contain the details of an individual release (e.g. album, single, bundle) and each of its components (e.g. tracks). The message should not contain data about multiple releases whether they are related or not.

CatalogueListMessage

This message enables record companies and distributors to communicate to a DSP information about a catalogue (of resources or releases) it is (or may be) making available. The message can be used to communicate information about catalogues to any other business partner. The message consists of a MessageHeader and a CatalogItem list which consists of data items such as ReleaseId, Title, Territory, ReleaseDate and Genre.

PurgeReleaseMessage

This message is used when a record company or distributor becomes aware that there is a corrupt release in the systems of a DSP and communicates the requirement for the relevant release to be taken down. The message is used when the take down cannot be communicated using the NewReleaseMessage. The message consiste of a MessageHeader and PurgedRelease section, the latter of which describes the release that is to be taken down.

Search