Search
Clear search
Close search
Google apps
Main menu

Resource List

The features described in this article are available only to partners who use YouTube's Content Manager to manage their copyrighted content.

The <ResourceList> contains the details about the primary resources (sound recordings or videos) and secondary resources (associated artwork) that make up the delivery. On a 10-track Audio Album for example, resource references A1 through A10 are the sound recordings and A11 is the album artwork. YouTube uses the album artwork as a key visual element in the generated Art Tracks for recordings from this album. Single Resource Release feeds should not contain any artwork, in accordance with the DDEX profile.

YouTube does not support per-territory metadata in the <ResourceList>. If the message includes multiple versions of the metadata for a track, YouTube uses only the version that appears first in the message.

Sound Recording Resources

Sound Recording IDs

YouTube requires every <SoundRecording> element to include a valid ISRC code. If you also track recordings using a proprietary ID code, you can include the <ProprietaryId> element as a sibling to the <ISRC> element inside the <SoundRecordingId>. The format of the <ProprietaryId> element is:

<SoundRecordingId>
      <ISRC>USRE10400888</ISRC>
      <ProprietaryId Namespace="DPID:your_DPid">custom_id_1234</ProprietaryId>
</SoundRecordingId>

Both your DDEX Party ID (Namespace) and the proprietary ID for the track are required. YouTube stores the proprietary ID value in the custom_id field of the sound recording asset (for Content ID deliveries) and the Art Track asset (for YouTube Red deliveries). For example, the XML above results in an asset with ISRC USRE10400888 and a  custom_id value of custom_id_1234.

To add different custom_id values to the Sound Recording and Art Track asset, you can use the dedicated "YOUTUBE:SR_CUSTOM_ID" and "YOUTUBE:AT_CUSTOM_ID" namespaces:

<SoundRecordingId>
      <ISRC>USRE10400888</ISRC>
      <!--- Sets the custom ID on the Sound Recording asset -->
      <ProprietaryId
      Namespace="YOUTUBE:SR_CUSTOM_ID">sound_recording_id_1234</ProprietaryId>
      <!--- Sets the custom ID on the Art Track asset -->
      <ProprietaryId
      Namespace="YOUTUBE:AT_CUSTOM_ID">art_track_id_1234</ProprietaryId>
</SoundRecordingId>

To add asset labels to the Sound Recording and Art Track assets, you can use the dedicated ”YOUTUBE:SR_ASSET_LABEL” and ”YOUTUBE:AT_ASSET_LABEL” namespaces:

<SoundRecordingId>
      <ISRC>USRE10400888</ISRC>
      <!--- Adds two asset labels to the Sound Recording asset -->
      <ProprietaryId
      Namespace="YOUTUBE:SR_ASSET_LABEL">sr_asset_label1</ProprietaryId>
      <ProprietaryId
      Namespace="YOUTUBE:SR_ASSET_LABEL">sr_asset_label2</ProprietaryId>
      <!--- Adds one asset label to the Art Track asset -->
      <ProprietaryId
      Namespace="YOUTUBE:AT_ASSET_LABEL">at_asset_label</ProprietaryId>
</SoundRecordingId>

Sound Recording Metadata

For guidelines on how to populate the Sound Recording metadata, please refer to the Music Metadata Style Guide from the Music Business Association. The metadata from the <SoundRecording> tag is used for:

  • Content ID deliveries: metadata stored on the Sound Recording asset.
  • YouTube Red deliveries: Art Track creation and metadata stored on the Art Track asset.
     

Sound Recording Ownership

To add ownership to a SoundRecording asset, you must send either a Single Resource Release feed, or an Audio Album feed that has YouTube_ContentID as a MessageRecipient.

Sound Recording ownership is applied using the <RightsController> tag under the <SoundRecording> element. The <PartyId> must match that of the <MessageSender> tag (or the <SentOnBehalfOf> tag, if provided).

The XML example below specifies that ABC Label owns the Sound Recording in South Africa:

<ResourceList>
    <SoundRecording>
        [...]
        <ResourceReference>A1</ResourceReference>
        [...]
        <SoundRecordingDetailsByTerritory>
            <!--Specifies the territory/territories in which ownership should be
            applied. -->
            <TerritoryCode>ZA</TerritoryCode>
            [...]
            <!-- This section sets the ownership of the Sound Recording. -->
            <RightsController>
                <PartyId>PADPIDAZZZZXXXXXXU</PartyId>
                <PartyName>
                    <FullName>ABC  Label</FullName>
                </PartyName>
                <RightsControllerRole>RightsController</RightsControllerRole>
                <RightSharePercentage>100.00</RightSharePercentage>
            </RightsController>
        [...]
        </SoundRecordingDetailsByTerritory>
    [...]
    </SoundRecording>
</ResourceList>

Art Track Ownership


Art Track asset ownership is inferred from the <Release>, not the <SoundRecording>. Review the Release List article for more details about art track ownership.

 

Video Resources

Video IDs

YouTube requires every <Video> element to include a valid ISRC code. This ISRC code must be different from the one used for the sound recording as per IFPI guidelines. If you also track video resources using a proprietary ID code, you can include the <ProprietaryId> element as a sibling to the <ISRC> element inside the <VideoId>. The format of the <ProprietaryId> element is:

<VideoId>
      <ISRC>USRE10400889</ISRC>
      <ProprietaryId Namespace="DPID:your_DPid">custom_id_1234</ProprietaryId>
</VideoId>

YouTube stores the proprietary ID value in the custom_id field of the music video asset (for Content ID deliveries). For example, the XML above results an asset with ISRC USRE10400889 and a custom_id value of custom_id_1234.

To add asset labels to the Music Video asset, you can use the dedicated "YOUTUBE:MV_ASSET_LABEL" namespace:

<VideoId>
      <ISRC>USRE10400889</ISRC>
      <!--- Adds two asset labels to the Music Video asset →
      <ProprietaryId  Namespace="YOUTUBE:MV_ASSET_LABEL">mv_asset_label1</ProprietaryId>
      <ProprietaryId  Namespace="YOUTUBE:MV_ASSET_LABEL">mv_asset_label2</ProprietaryId>
</VideoId>

To specify the channel into which the video should be uploaded, you can use the dedicated "YOUTUBE:CHANNEL_ID" namespace:

<VideoId>
     <ISRC>USRE10400889</ISRC>
     <!-- Specifies the channel to upload the video in  -->
     <ProprietaryId Namespace="YOUTUBE:CHANNEL_ID">MyChannel</ProprietaryId>
</VideoId>

If no channel is specified in the feed, then the video will be uploaded in the default channel configured in your uploader account.

To update a previously uploaded video, you can use the dedicated "YOUTUBE:VIDEO_ID" namespace:

<VideoId>
      <ISRC>USRE10400889</ISRC>
      <ProprietaryId  Namespace="YOUTUBE:VIDEO_ID">9bZkp7q19f0</ProprietaryId>
</VideoId>

 

Music Video Metadata

For guidelines on how to populate the metadata in DDEX, please refer to the Music Metadata Style Guide from the Music Business Association. The following elements from the <Video> tag are used to populate video and metadata on YouTube:

Video: Title <VideoDetailsByTerritory>
    [...]
    <Title TitleType="DisplayTitle">
        <TitleText>A little bit of Foo</TitleText>
    </Title>
    [...]
</VideoDetailsByTerritory>
Video: Tags/Keywords <VideoDetailsByTerritory>
    [...]
    <Keywords>Keyword1</Keywords>
    <Keywords>Keyword2</Keywords>
    [...]
</VideoDetailsByTerritory>
Asset: Song <Video>
   [...]
    <ReferenceTitle>
        <TitleText>A little bit of Foo</TitleText>
    </ReferenceTitle>
   [...]
</Video>

 
Asset: Label Name <VideoDetailsByTerritory>
    [...]
    <LabelName>Test Label</LabelName>
    [...]
</VideoDetailsByTerritory>
Asset: Artists

<VideoDetailsByTerritory>
    [...]
   <DisplayArtist SequenceNumber="1">
        <PartyName>
            <FullName>Jonny and the Føøbars</FullName>
        </PartyName>
        <ArtistRole>MainArtist</ArtistRole>
    </DisplayArtist>

    <DisplayArtist SequenceNumber="2">
        <PartyName>
            <FullName>Some Other Artist</FullName>
        </PartyName>
        <ArtistRole>MainArtist</ArtistRole>
    </DisplayArtist>
    [...]
</VideoDetailsByTerritory>

Asset: Genre <VideoDetailsByTerritory>
    [...]
    <Genre>
        <GenreText>Hip Hop</GenreText>
    </Genre>
    [...]
</VideoDetailsByTerritory>

 

The video description is populated from the <Release>, not the <Video>. See the Release List section for more information.

 

Music Video Ownership

Music Video ownership is applied using the <RightsController> tag under the <Video> element. The <PartyId> must match that of the <MessageSender> tag (or the <SentOnBehalfOf> tag, if provided).

The XML example below specifies that ABC Label owns the Music Video in South Africa:

<ResourceList>
    <Video>
        [...]
        <ResourceReference>A1</ResourceReference>
        [...]
        <VideoDetailsByTerritory>
            <!--Specifies the territory/territories in which ownership should be applied. -->
            <TerritoryCode>ZA</TerritoryCode>
            [...]
            <!-- This section sets the ownership of the Music Video. -->
            <RightsController>
                <PartyId>PADPIDAZZZZXXXXXXU</PartyId>
                <PartyName>
                    <FullName>ABC  Label</FullName>
                </PartyName>
                <RightsControllerRole>RightsController</RightsControllerRole>
                <RightSharePercentage>100.00</RightSharePercentage>
            </RightsController>
        [...]
        </VideoDetailsByTerritory>
    [...]
    </Video>
</ResourceList>

 

Was this article helpful?
How can we improve it?
Resources for Creators

Check out the creator resources available to help you build your channel and connect with the community.