Uploading videos in DIVA

Introduction

The DIVA Video entity lets editors ‌upload mp4 video files into DIVA.

When uploading videos through the FORGE Back Office, the ingestion into DIVA is fully automated. The next paragraphs explain step-by-step how it works.

Before starting

When using FORGE as a video Content Management System (CMS) based on DIVA, make sure that:

• The DIVA workflow is up and running in your environment. Your video engineering team may help you with this.

• The DIVA video custom entity has been set up in FORGE. Your FORGE admins may help you check this.

Creating a new video entity

1. In the left menu, choose the video entity icon.
   The icon and tooltip can look different in your environment because the video entity type is a custom type and can be changed.
    

2. In the video entity list page, select the plus NEW button in the top-right:
    

3. On the new video detail page, start by writing the video entity title. This automatically calculates the slug and creates the video entity.
    

Uploading a video

1. Select the CHOOSE FILE button, to select the file you want to upload:
    

2. Once the file is selected (alpha video signal test.mp4 in the screenshot below), choose the upload configuration your project requires:
    

3. Select UPLOAD to start ingesting the selected file:
    

4. The video file transcoding starts. Once completed, the video preview displays:
      

   Note: In case of transcoding failure, find error details in the DIVA Back Office workflow monitor page.

5. Optionally, select Click here to go to the Video Editor to check or edit the video asset in DIVA Back Office:
    

Setting the video entity fields

Note: As the video entity is a custom one, there may be additional fields beyond those that come out-of-the-box.

Set the following fields to instruct the front-end on how the video entity must display:

• Description: The editorial description of the video content.

• Short Title: The video's short title.

• Short Description: The short editorial description of the video content.

• Video Status: Automatically filled during the ingestion. The status can be either:

  • Scheduled

  • Ondemand

  • Live

  • Planned

  • Error — This is the status when the transcoding fails.

• Video Workflow: Automatically filled during the ingestion. The status can be either:

  • LIVE

  • VOD

• Video Duration: Automatically filled during the ingestion. It's the actual video duration.

• Extended Video Duration: Automatically filled during the ingestion. It's the video duration before any trim.

• Has Data: Toggle that declares whether the video has synchronized data.