Video migrations from Dreambroker and Ubicast to Icareus Video Cloud

Migrations from other video cloud services

Introduction

This article describes how migrations from other video cloud services are handled when importing content into Icareus Video Cloud.

Dreambroker

Before migration

Because importer fetches data from Dreambroker channels, every video that needs to be imported must be included in a channel.

The importer fetches video data from their web pages, which is why the relevant channels and videos must be public during the import. 

The time required to import each channel depends on the number of videos in that channel.

During migration

The importer creates a folder for each Dreambroker channel. Every video in that channel is added to the corresponding folder in Icareus Video Cloud.

If the Dreambroker channel has categories, the importer creates the same category structure as subfolders under the channel folder in Icareus Video Cloud. Videos are placed in the matching subfolders.

The importer also tries to import the following metadata and related assets, if they exist:
  1. subtitles
  2. chapters
  3. thumbnail
  4. publishing times
  5. the video’s unique Dreambroker ID
The Dreambroker video ID can later be used to find the same video in Icareus Video Cloud.

The importer does not create a master video file. Instead, it imports the video qualities provided by Dreambroker as presets in Icareus Video Cloud. As a result, the video should have the same number of presets in Icareus Video Cloud as it had available qualities in Dreambroker.

After migration

After the migration, you can review the imported videos in Media Library of the admin interface. The videos are grouped into folders based on their original Dreambroker channels.

Ubicast

Before migration

Ubicast migrations use the Ubicast API. This means that an API key is required. A new API key can be created in the Ubicast admin interface.

All data to be imported must be available through the API key, including subtitles and other related assets.

The importer only imports videos stored in Ubicast. Ubicast can also contain videos where the source is hosted outside Ubicast, for example on YouTube. These external videos are ignored during the migration.

The importer does not import users or user groups into Icareus Video Cloud. It fetches this information and stores it in local files, but currently this information is not used during the import.

During migration

The importer tries to import all following data:
  1. video files
  2. subtitles
  3. thumbnails
  4. categories

The importer also preserves the category tree structure as folders and subfolders.

The importer does not create master video files. Instead, it imports the quality files provided by Ubicast and saves them as presets in Icareus Video Cloud.

After all qualities have been imported, the importer automatically creates a new SMIL file. This allows the videos to work with dynamic players immediately.

After migration

After the migration, you can review the imported videos in the Media Library of the admin interface. The videos are grouped according to the imported Ubicast category structure.

YuJa

Before migration

YuJa migrations use the YuJa API. This means that an API key is required.

The name of the YuJa API server is also required. It is typically in the following format: https://<organization>.yuja.com

Because YuJa allows different permissions for each API key, the API key must have access to at least the following API fronts:
  1. Services/users/
  2. Services/videos/user/
  3. Services/media/video/
  4. Services/media/videos/
  5. Services/media/folders/
  6. Services/media/retrievefolderassets/

During migration

The importer tries to import the following data:
  1. users, including creators and admins
  2. videos
  3. subtitles
  4. thumbnails
  5. folders
  6. indexes

YuJa indexes are saved as chapters in Icareus Video Cloud.

Videos are imported to the user who created the video in YuJa. Each user gets their own folder in Icareus Video Cloud, and the videos are saved under the same folder structure as they were in YuJa.

If subtitles are provided as SRT files, they are converted to VTT files before they are saved in Icareus Video Cloud.

After migration

After the migration, you can review the imported videos in the Media Library of the admin interface. No additional YuJa-specific actions are required after the import.

Additional

Subtitles

Icareus currently supports VTT subtitle files. If your source service uses SRT files or another subtitle format, please mention this before the migration.
SRT files can be converted to VTT, but this must be handled separately in the importer.


Embed video URLs

After migration, imported videos can be embedded with the normal Icareus player embed URL:
  1. https://players.icareus.com/<language-code>/<account-name>/embed/vod/<video-id>
For migrated videos, <video-id> can be either the Icareus asset ID or the original video ID from the source service, such as Dreambroker or Ubicast.

For more information about embed URL parameters, see this article: Embedding Audio and Video: URL Structure and Parameters
    • Related Articles

    • Embed a video player

      Introduction Embedding a video player to your web site (e.g. implemented with WordPress) is straighforward via iframe or using our javascript embed option. Iframe Embed Iframe embed is the most common way to embed content to a web site from 3rd party ...
    • Managing Categories / Folders

      Introduction Categories or folders are used for two different purposes: 1. To organize your video content on Icareus Video Cloud and 2. If you have public Video portal or Video pages, to manage video categories and video visibility there Managing ...
    • Managing Categories/Folders

      Introduction Categories or folders are used for two different purposes: 1. To organize your video content on Icareus Video Cloud and 2. If you have a public video portal or video pages, to manage the visibility and order of their video categories ...
    • Migration of older Playout versions to Playout 6

      Introduction Icareus Playout 4 runs on the CentOS 6 operating system, which reached end of life on November 30th, 2020. Because of this, Icareus developed Playout 5 which runs on CentOS 7 and Playout 6 which runs on CentOS 7 and on Rocky 8. It's ...
    • As Online Video Platform

      FOR MEDIA COMPANIES, ENTERPRISES AND SPORTS -  Cloud Solution for Your Online Video Services Icareus Online Video Platform customers are media companies, large corporations, SMEs, sports clubs, non-profit organizations and anything in between those ...