DC 5.4 Google Project configuration

Owned by Camilla Voigt Kristiansen
Last updated: Dec 10, 2020 by Gosia Creosteanu (Unlicensed)
5 min read

Before Digizuite are able to configure the YouTube integration, some information are needed:

How to provide the above (3) information to Digizuite?

Project setup

Some preliminary configuration must be done with Google:

  1. Go to https://console.developers.google.com/, and make sure 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.

  2. If you don’t already have a project, create a new project. Ensure that the appropriate project is selected in the top menu.

  3. Enable “YouTube Data API v3” for the project.

    1. Select “Library” in the left menu.

    2. Search for “YouTube Data API v3”.

    3. Select the search result and enable the API.

  4. Setup an OAuth Consent Screen.

    1. In the left menu, select “OAuth Consent Screen”.

    2. Give the application a name.

    3. In “Authorized Domains” enter the domain of the DAM Center installation. Google can figure out the domain part, if you are unsure. Thus, if the DAM Center is installed at e.g. “mm-dam.dev.digizuite.com”, you can enter this.

    4. Save.

  5. Create credentials.

    1. In the left menu, select “Credentials”.

    2. Click “Create Credentials” in the top menu, and choose “OAuth Client ID” (see image below).

    3. Choose “Web application”.

    4. Give the web application a name.

    5. In “Authorized redirect URIs” enter: “<YOUR_DAM>/DigizuiteCore/YoutubeService/api/v1/YoutubeClients/OAuth2Callback”. E.g. if the DAM Center has been installed at “https://mm-dam.dev.digizuite.com”, the entry should be: “https://mm-dam.dev.digizuite.com/DigizuiteCore/YoutubeService/api/v1/YoutubeClients/OAuth2Callback”. NOTE: It is important that the DAM Center installation is the same that was registered in step 4.c.

    6. Create the credentials.

    7. 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.

Please send ClientId and ClientSecret to Digizuite including desired name for the YouTube integration in the Media Manager.

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 videoes “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.

When filling in the form for the compliance audit, the following information will come in handy:

  • Your full legal name

  • Your organization's name

  • Your organization's website

  • Your organization's address.

  • Does your API Client commercialize YouTube Data?

  • Organization contact email address

  • Describe your organization's work as it relates to YouTube

  • Google representative email address

    • Can be skipped.

  • Content Owner ID (if available)

    • Can be skipped.

  • Please list all your API Client(s)

    • The URL of the DAM Center.

  • Please list all the project numbers used for each of your API Client(s)

    • This is VERY important. Go to https://console.developers.google.com/ and ensure that you are logged in with the correct user (top right corner) and that the correct project is chosen (top left corner). Then, in the top right corner, click the burger menu and select “Project settings”. Copy the project number into this entry in the form.

  • Is this a publicly or privately available API Client?

  • Where can we find each API Client(s)?

    • The URL of the DAM Center.

  • If there is a log-in required to access the API client, please provide a demo account and instructions on how to access the API Client

    • Can be skipped.

  • Does your API Client commercialize YouTube Data?

  • Choose the option that best resembles your API Client's use case

    • YouTube video uploads.

  • Specify all YouTube API Services used by this API Client

    • Data API.

  • Select the primary audience for your API Client

    • Creators.

  • Approximately how many users use your API Client?

    • Typically not that many.

  • Explain how your API Client is used by your users

    • Use the description from “Describe your organization's work as it relates to YouTube” above.

  • Does your API Client use multiple projects to access YouTube APIs?

    • No.

  • Does this API Client create, access or use any metrics derived from YouTube data?

    • No.

  • Does this API Client display data from, or provide features or services across, multiple platforms (ex: Facebook, Twitter, etc.)?

  • Do you create/provide any type of reports using YouTube API Data?

  • How long do you store YouTube API Data?

    • <24 hours.

  • How often do you refresh YouTube API Data?

  • Does this API Client allow users to authenticate with their Google credentials

    • No.

  • Screencast of API usage:

If the “Quota Extension Request” type was chosen in the top:

  • Which API Client are you requesting a quota increase for?

    • The URL of the DAM Center.

  • What API project number are you requesting increased quota for?

  • Use the project number found above.

  • Which YouTube API Service(s) are you requesting a quota increase for?

    • Data API.

  • How much "Additional Quota" are you requesting?

    • 500.000 should do.

  • Justification for requesting additional quota?

    • A larger daily quota is needed to be able to test our YouTube integration properly. With the current quota, we are not able to test it thoroughly, since we reach the daily limitation after a few uploads. This requires us to distribute the testing over multiple days.

  • Explain in detail how you use YouTube API Services today

    • Use the description from “Describe your organization's work as it relates to YouTube” above.

  • What functionality would your API client be lacking without more quota?

    • Use the description from “Justification for requesting additional quota?” above.

  • What potential workarounds would you use to compensate for less quota? (ex. decreased feature set, estimations, smaller sampling)

    • Use the description from “Justification for requesting additional quota?” above.

Expect the compliance audit process to take at least a few days.