Based on needs of the MLCs participating in the SCAPR VRDB project the following additions have been made to the Standard:
AssociatedSoundRecordingId added into SoundRecording
VRDB enables the identification of cases in which multiple ISRCs have been erroneously assigned to a given sound recording. This element allows VRDB societies to take into account ISRCs that have been erroneously assigned to a recording, without ignoring the ISRC properly assigned to uniquely identify a sound recording. This is done using an AssociatedSoundRecordingId composite alongside the SoundRecordingId, having the same structure as the SoundRecordingId. (The use of this element is not mandatory).
RecordLastUpdatedDate added into SoundRecording
Societies have to decide when they download the record if they need to update their local system data. By including a RecordLastUpdatedDate into the SoundRecording, the source of data can specify the last time a record was changed, which can be compared with the date on the target system. (The use of this element is not mandatory).
VRDB2RepertoireManagerCode added into SoundRecording
VRDB has business rules that codify which MLC is principally responsible within the VRDB system for dealing with metadata about a given recording. In essence VRDB delegates the data management to the society which is best placed to interact with the rights owner(s) for the specific recording. The VRDB2RepertoireManagerCode identifies the society that is repertoire manager of the metadata for a given SoundRecording within VRDB. (The use of this element is not mandatory).
Booleans added at the SoundRecording level
- In order to flag a recording for which metadata is not agreed or is under review, the flag IsSoundRecordingMetadataUnderReview can be attached at the SoundRecording level, taking TRUE/FALSE values.
- In order to flag a recording with limited access to some metadata the flag IsSoundRecordingMetadataAccessRestricted can be attached at the SoundRecording level, taking TRUE/FALSE values. This might be used in case the relevant societies do not have a reciprocal agreement in place between them to cover inter alia data sharing.
The use of these flags is optional.
Other changes implemented in v1.3 are:
- PartyID becomes a top-level composite with sub-element that indicate the type of identifiers.
- ICPN no longer has the IsEAN attribute, since it doesn’t matter whether UPC or EAN is used.