RDR-N: SoundRecording DetailsByTerritory (version 1.3)
Each SoundRecording
node must include one or more SoundRecordingDetailsByTerritory
nodes. The first SoundRecordingDetailsByTerritory
node includes data which would apply for this SoundRecording
in all territories as a default, unless specifically overridden by further information provided in subsequent SoundRecordingDetailsByTerritory
nodes. Most implementers of the RDR-R message currently specify that only one SoundRecordingDetailsByTerritory
node should be supplied per SoundRecording
. (This does not preclude the delivery of multi-territory rights ownership information.)
<SoundRecordingDetailsByTerritory> <TerritoryCode>FR</TerritoryCode> <Title TitleType="DisplayTitle"> <TitleText>100 VIP</TitleText> </Title> <DisplayArtist SequenceNumber="0"> <PartyName> <FullName>KATERINE</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">6687769</ProprietaryId> </PartyId> <ArtistRole>MainArtist</ArtistRole> </DisplayArtist> <DisplayComposer SequenceNumber="0"> <PartyName> <FullName>BONDU PIERRE</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">71166</ProprietaryId> </PartyId> </DisplayComposer> <InitialProducer> <PartyName> <FullName>UNIVERSAL MUSIC FRANCE</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">1</ProprietaryId> </PartyId> <TerritoryCode>FR</TerritoryCode> </InitialProducer> <RightsController SequenceNumber="0"> <PartyName> <FullName>UNIVERSAL MUSIC FRANCE</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">1</ProprietaryId> </PartyId> <RightsControllerRole>RightsController</RightsControllerRole> <RightSharePercentage>100.0</RightSharePercentage> <DelegatedUsageRights> <UseType>Broadcast</UseType> <UseType>Simulcast</UseType> <UseType>PerformInPublic</UseType> <PeriodOfRightsDelegation> <StartDate>2008-09-26</StartDate> </PeriodOfRightsDelegation> <TerritoryOfRightsDelegation>FR</TerritoryOfRightsDelegation> </DelegatedUsageRights> <IsPayingOutRoyalties>false</IsPayingOutRoyalties> </RightsController> <OriginalResourceReleaseDate>2008-09-26</OriginalResourceReleaseDate> <PLine PLineType="OriginalPLine"> <Year>2008</Year> <PLineCompany>UNIVERSAL MUSIC FRANCE</PLineCompany> <PLineText /> </PLine> <HostSoundCarrier> <ReleaseId> <ISRC>FRUM70701194</ISRC> <ICPN>0042288237846</ICPN> <CatalogNumber Namespace="PADPIDA2007061301U">0042288237846</CatalogNumber> <ProprietaryId Namespace="PADPIDA2007061301U">5993921</ProprietaryId> </ReleaseId> <Title TitleType="DisplayTitle"> <TitleText>STUDIOLIVE</TitleText> </Title> <DisplayArtist SequenceNumber="0"> <PartyName> <FullName>KATERINE</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">6687769 </ProprietaryId> </PartyId> <ArtistRole>MainArtist</ArtistRole> </DisplayArtist> <TrackNumber>8</TrackNumber> <SideNumber>1</SideNumber> <CarrierType>CD</CarrierType> <NumberOfSoundRecordingsClaimedInCarrier>15 </NumberOfSoundRecordingsClaimedInCarrier> <CompilationType>NotCompiled</CompilationType> <IsPhysicalDistribution>true</IsPhysicalDistribution> <IsHiddenResource>false</IsHiddenResource> <IsBonusResource>false</IsBonusResource> <IsInternalCompilation>false</IsInternalCompilation> </HostSoundCarrier> (Multiple further HostSoundCarrier nodes corresponding to all the releases of this SoundRecording) <Genre LanguageAndScriptCode="fr-FR"> <GenreText>CHANSONS FRANCAISES</GenreText> </Genre> </SoundRecordingDetailsByTerritory> |
Mandatory Fields
DetailsByTerritory Fields for a SoundRecording Within ResourceList | Recommended Profile | Core Data Profile |
---|---|---|
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory for classical | Mandatory for classical |
| Mandatory |
|
| Mandatory | Mandatory |
| Mandatory if available | Mandatory if available |
| Mandatory | Mandatory |
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory |
|
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory |
|
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Optional | Optional |
| One ID is Mandatory | One ID is Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory | Mandatory |
| Mandatory if 'Classical' | Mandatory if 'Classical' |
Implementation Notes
TerritoryCode
– This defines the territory or territories covered by this node. ‘Worldwide
’ is defined as an allowed value. When listing an exception (i.e. toWorldwide
) anExcludedTerritoryCode
should be used.
Title
– InSoundRecordingDetailsByTerritory
’ this tag can be used to express the title in another language, or an alternative title applicable in a given territory. This is in accordance with ERN-3 profile rules. See also: TitleLanguageAndScriptCode
/TitleText
/SubTitle
.
Example of Title
<Title LanguageAndScriptCode="en" TitleType="DisplayTitle"> <TitleText>My Song</TitleText> <SubTitle>Album Version</SubTitle> </Title> |
DisplayArtist
– This is the artist name as associated with the recording. (See also the HostSoundCarrier node for artist name as associated with a given release on which the sound recording appears). The “artist name” element is solely descriptive information (i.e. does not convey or necessarily imply information about rights, performances or contributions.) MLCs use this for matching to usage.Example of a band name
DisplayArtist
: “The Weeknd”Example of several artists as
DisplayArtist
: “The Beatles & Tony Sheridan”Example of a ‘virtual’ band
DisplayArtist
: “Gorillaz”.
When the
DisplayArtist
is provided, the following are mandatory:FullName
RoleCode
MainArtist
is aRoleCode
and only applies toDisplayArtist
.MainArtist
is the principal credited artist associated with a resource.
Note that theDisplayArtist
composite may occur several times with the tagSequenceNumber
set to different integer values. TheSequenceNumber
value is used as part of the enumeration of the artists to whom the recording is associated.
Example of DisplayArtist
<DisplayArtist SequenceNumber="0"> <PartyName LanguageAndScriptCode="en"> <FullName>The Weeknd</FullName> </PartyName> <PartyId> <ProprietaryId Namespace="PADPIDA2007061301U">1234567 </ProprietaryId> </PartyId> <ArtistRole>MainArtist</ArtistRole> </DisplayArtist> |
DisplayComposer
is mandatory when theGenre
is ‘Classical
’.(IndirectResourceContributor
could also be used in MLC 1.3.1, but it is to be removed in MLC 1.4). For classical recordings, this is needed (along with the work title) in order to disambiguate the recording and to match usage.
When the DisplayComposer is provided, the following are mandatory:FullName
RoleCode
FeaturedArtist
– Some MLCs need data about the contributors to a recording and the nature of their contributions, so that contributors that are eligible and qualifying for equitable remuneration can be paid. The ‘contribution category’ of a contributor can be ‘featured’ or ‘non-featured’. MLCs use the contribution category along with the role and/or roles in determining remuneration.
AFeaturedArtist
is either an individual person or a collective (such as an orchestra), referred to by their name and/or the identifier used to designate them within systems such as SCAPR’s IPD. AFeaturedArtist
is a performer who is prominently featured in relation to the release (as opposed to a session musician, who would be aNonFeaturedArtist).
There
will often be multiple FeaturedArtists, enumerated using theSequenceNumber
attribute. For eachFeaturedArtist,
the following are mandatory:Name/FullName
PartyId/IPN
(if available)PartyId/ProprietaryId
with sender’s proprietary IDInstrumentType
DateAndPlaceOfBirth
(if available, place is optional)Performance
Territory
Within the DDEX RDR-R message it is also possible to carry the information about performative roles within the
‘ResourceContributor’
composite. Under present usage however, the principal way of conveying data aboutFeaturedArtist
andNonFeaturedArtist
is within the dedicated composites –ResourceContributor
should be used for non-performing roles, such as certain studio roles.
Example: FeaturedArtist
<FeaturedArtist SequenceNumber="0"> <InstrumentType>VOC</InstrumentType> <Sex>Female</Sex> <DateAndPlaceOfBirth TerritoryCode="GB">1986-08-02 </DateAndPlaceOfBirth> <TerritoryOfResidency>GB</TerritoryOfResidency> <PartyId Namespace="IPN">12345678</PartyId> <PartyId Namespace="LocalPerformerId">12345678</PartyId> <PartyName> <FullName>Jane Doe</FullName> <NamesBeforeKeyName>Jane</NamesBeforeKeyName> <KeyName>Doe</KeyName> </PartyName> <ArtistRole Namespace="SDEGRoleCode" UserDefinedValue="MU"> UserDefined</ArtistRole> <TerritoryOfPerformance>GB</TerritoryOfPerformance> <PerformanceDate>2014-06-10</PerformanceDate> </FeaturedArtist> |
FeaturedNonContractedArtist
is a further contribution category used only by some MLCs, which refers to a contribution by an artist who appears prominently in relation to the release but who is not signed to the label (appearing under a ‘sideman’ contract for example).
For eachFeaturedNonContractedArtist,
the same information is mandatory as withFeaturedArtist
above.
A
NonFeaturedArtist
always an individual person, referred to by their name and identifier, who has contributed to the recording but is not featured prominently in relation to the release, e.g. a session musician.
For eachNonFeaturedArtist,
the same information is mandatory as withFeaturedArtist
andFeaturedNonContractedArtist
above.
Example: NonFeatureadArtist
<NonFeaturedArtist SequenceNumber="0"> <InstrumentType>DRU</InstrumentType> <InstrumentType>GTR</InstrumentType> <Sex>Male</Sex> <DateAndPlaceOfBirth TerritoryCode="US">1990-01-18 </DateAndPlaceOfBirth> <TerritoryOfResidency>FR</TerritoryOfResidency> <PartyId Namespace="LocalPerformerId">SX1234567</PartyId> <PartyName> <FullName>John Smith</FullName> <NamesBeforeKeyName>John</NamesBeforeKeyName> <KeyName>Smith</KeyName> </PartyName> <ArtistRole Namespace="SDEGRoleCode" UserDefinedValue="MU"> UserDefined</ArtistRole> <TerritoryOfPerformance>GB</TerritoryOfPerformance> <PerformanceDate>2014-06-10</PerformanceDate> </NonFeaturedArtist> |
Roles
– Within theFeaturedArtist, FeaturedNonContractedArtist
andNonFeaturedArtist
contribution categories theArtistRole
node expresses onePrimaryRole
and optionally furtherAdditionalRoles
in which the performer has contributed to the recording.Roles
such as soloist, musician, conductor, and so on can be expressed using DDEX role codes or if appropriate using SCAPR SDEG role codes.InstrumentType
details can also be provided.
ResourceContributor
– Contributions to the recording that are not performance based should be carried in theResourceContributor
node, annotated by details of the role(s) such asDirector
etc.
Example: to show that a role of video director is displayed on a product, use:Video\VideoDetailsByTerritory\ResourceContributor
and usePartyName\FullName
for the director, also using theArtistRole
with a role code for ‘director’.
Note: The definition of this field is different between the RDR and ERN standards.
InitialProducer
– DDEX defines the termInitialProducer
as being a party that initiates the creation of theSoundRecording.
This is the legal entity responsible for the creation of the recording. This term relates to a definition “producer of phonograms” in the WIPO Performances and Phonograms Treaty, being “the person, or the legal entity, who or which takes the initiative and has the responsibility for the first fixation of the sounds of a performance or other sounds, or the representations of sounds.” MLCs sometimes term this party ‘commissioning producer’.
RightsController
- This is mandatory along with the following fieldsPartyName/FullName
PartyId/ProprietaryId
with sender’s proprietary ID. Local producer ID is always used by MLCs.PartyId/ProprietaryId
with recipient’s proprietary IDRightsControllerType
– This is mandatory for PPL. Type of rights holder can be OriginalCopyrightOwner, SuccessorInTitle, or ExclusiveLicensee as defined by the DDEX AVS.RightSharePercentage.
The percentage of rights owned between the start and end dates of ownership. (12.5 = 12.5%).DelegatedUsageRights
UsageType.
The type of use for which the recording may be licensed. This takes a value from the DDEX AVS.PeriodOfRightsDelegation/StartDate
TerritoryOfRightsDelegation
expressed as ISO 3166-1 alpha-2 codes or Worldwide.
OriginalResourceReleaseDate
can be to the nearest year and is used by MLCs in assessing whether the copyright term has expired or not. The TerritoryCode conveys the country(ies) of (simultaneous) first publication, which is a 'point of attachment' determining eligibility under the treaties.
Example: OriginalResourceReleaseDate
<OriginalResourceReleaseDate TerritoryCode="US">2011-01-02 </OriginalResourceReleaseDate> <OriginalResourceReleaseDate TerritoryCode="GB">2012-01-02 </OriginalResourceReleaseDate> |
The
PLine
states the rightsholder detail at the time the time when the recording was published, and is not necessarily the same as theInitialProducer.
It is the nationality of theInitialProducer
that is one of the 'points of attachment' determining eligibility under the treaties. The mandatory fields forPLIne
are:Year
PlineText
Since
PLineText
will be deprecated by DDEX in future versions of the standard but remains mandatory for the time being, it may be left blank.
HostSoundCarrier’s
ReleaseId - at least one of the following sub elements is mandatory:ICPN
CatalogNumber
CatalogNumber
ProprietaryId
HostSoundCarrier/Title
is the title of the sound carrier / album that contains the track.
HostSoundCarrier/DisplayArtist
is theName/FullName
of theMainArtist
of the sound/carrier on which the track is featured.
HostSoundCarrier/LabelName
is used for matching. It is safer to include label information at theHostSoundCarrier
node for a release than in theSoundRecordingDetailsByTerritory
.
HostSoundCarrier/NumberOfSoundRecordingsClaimedInCarrier
helps to avoid double claims in compilations, and helps to avoid omitting relevant recordings
Genre
There are hundreds of genres and they correspond more to how an artist wants to be perceived or placed than to any objective criteria.
MLCs use Genre only for classical music as a trigger for special processing, such as to ensure composer information is present, and to apply matching rules better suited to classical metadata. In future DDEX may replace this within the RDR-R message using a flagisClassical.
Example for Additional Performer Data in the SoundRecording Composite
<NumberOfFeaturedArtists>4</NumberOfFeaturedArtists> <NumberOfNonFeaturedArtists>2</NumberOfNonFeaturedArtists> <LineupComplete>false</LineupComplete> |