...
Some preliminary configuration must be done with Google:
Part 1
Go to https://console.developers.google.com/, and
...
ensure that you are logged in with the Google account that videos should be uploaded with. Thus, if you are setting this up for a customer, it should be the Google account they use for YouTube.
Part 2
If you don’t already have a project, create a new project. Ensure that the appropriate project is selected in the top menu.
Part 3
Enable “YouTube Data API v3” for the project.
Select “Library” in the left menu.
Search for “YouTube Data API v3”.
Select the search result and enable the API.
...
Part 4
Set up an OAuth Consent Screen.
In the left menu, select “OAuth Consent Screen”.
Give the application a name.
In “Authorized Domains” enter the
...
“top domain” of the DAM Center installation.
...
For customer sites maintained by Digizuite, this will always be “digizuite.app“
For development sites, “digizuite.dev“
If you manage the site yourself, if you, e.g., have a site named “dam.mydomain.com“, “mydomain.com“ will be the URL to insert.
Save.
Part 5
Create credentials.
In the left menu, select “Credentials”.
Click “Create Credentials” in the top menu, and choose “OAuth Client ID” (see image below).
Choose “Web application”.
Give the web application a name.
In “Authorized redirect URIs” enter
...
: “https://api-[GUID].digizuite.app/DigizuiteCore/YoutubeService/api/v1/YoutubeClients/OAuth2Callback”.
...
For example, if the DAM Center has been installed at “https://
...
api-1cd509e4-ae20-47c9-a692-35bc6b7b3b58.digizuite.app”, the entry should be: “https://
...
api-1cd509e4-ae20-47c9-a692-35bc6b7b3b58.digizuite.
...
app/DigizuiteCore/YoutubeService/api/v1/YoutubeClients/OAuth2Callback”.
NOTE: It is important that the DAM Center installation is the same that was registered in
...
Part 4, step 3.
Create the credentials.
You have now obtained a ClientId and a ClientSecret. If they aren’t immediately visible, they can be found by clicking the newly created entry in “OAuth 2.0 Client IDs” in the “Credentials” section. These will be needed later.
...
Project compliance audit
YouTube has three privacy categories for uploaded videos: “private”, “unlisted”, and “public” (see https://support.google.com/youtube/answer/157177?co=GENIE.Platform%3DDesktop&hl=en for more information).
All projects created after July 28, 2020 must undergo a compliance audit to be able to make uploaded videos “unlisted” or “public”. If this is not done, videos will be forced to be “private” when uploaded with the YouTube service. The compliance audit process can be initiated from https://support.google.com/youtube/contact/yt_api_form. Consider choosing the “Quota Extension Request” reason, to also increase the quota limit. See the “Important knowledge” section below for more information a bout about this. It might be a good idea to actually reach the daily limit before applying for an increased quota. Thus, you can skip this step initially, and then return once you have validated that you are able to upload videos.
...
A specific channel for videos should be created in the DAM Center. If you already have the ChannelId of the channel to use, you can skip this step.
Go to the DAM Center used in the configuration above.
In “Channels”, create a new folder by right-clicking the channels area.
Give the channel a name. E.g. “YouTube”.
The ChannelId will be needed in a moment. This can be found by right-clicking the created channel, and selecting “Edit folder rights” (see image below).
...
YouTube client creation
A YouTube client can now be created in MM5.
...
At the top center of the screen in green letters, click on Create a new YouTube client. The ClientID, ClientSecret, and ChannelId from the configuration above will be needed here. There are two parameters with default values:
Search Name. The name of the search used to fetch the title and description of an asset. By default, the “GetYoutubeInformation” search is used, which fetches the standard asset title and description. A custom search can be created and used, or the “GetYoutubeInformation” search can be customized. See below for more information.
Default Privacy Status. The default privacy status to use when uploading videos to YouTube. By default, this is set to “private”. Other possible values are “public” and “unlisted”. See https://support.google.com/youtube/answer/157177?co=GENIE.Platform%3DDesktop&hl=en for more information. Please be aware of the potentially required compliance audit, described above, when configuring this.
Once a YouTube client has been created, it needs to be authorized. This can be done via the UI in the settings section in MM5. After successful authorization, videos will automatically be uploaded to YouTube, when they are published to the created YouTube channel. A video, which has been published to the YouTube channel in the DAM Center and has been successfully uploaded, will be deleted from YouTube if it is either deleted from the DAM Center or unpublished.
...
It is possible to also fetch the privacy status when uploading an asset. This will override the default privacy status on the assets where it is set. This can be done with the following steps:
In the DAM Center, find the “GetYoutubeInformation” search for the DAM Center in the ConfigManager.
Add an output field with id “privacyStatus”. The field could for instance be a ComboValue with the options “private”, “unlisted”, and “public”. Be aware that the privacy status from the search is ignored if it is invalid. The default privacy status is used as a fallback.
Save the search.
It is now possible to set the privacy status for each asset.
...
The “GetYoutubeInformation” search can be freely configured. However, the search must include at least two output fields with ids:
“title”
“description”
Limitations
The YouTube Service has the following limitations:
...