Editing Workflow:OVP migration flow

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
{{Infobox COW
 
{{Infobox COW
 
|status=Production
 
|status=Production
|tools=python, OVP, API
+
|tools=python, ovp, apis
 
|input=Media assets and descriptive metadata in source OVP.
 
|input=Media assets and descriptive metadata in source OVP.
 
|output=Media assets and descriptive metadata in destination OVP.
 
|output=Media assets and descriptive metadata in destination OVP.
Line 7: Line 7:
 
|organisationurl=https://ladigitalizadora.org/
 
|organisationurl=https://ladigitalizadora.org/
 
}}
 
}}
OVP migration flow - an agnostic blueprint
+
==Workflow Description==
 
 
To initiate the transition from any given Source [https://en.wikipedia.org/wiki/Online_video_platform On-line Video Platform] to a Destination OVP, the first step involves retrieving video information from the OVP Source. You should be able to achieve this by making a GET request to the OVP Source's API authenticating against it, typically using an access token and video ID. This request should typically be directed to a generic API endpoint.
 
 
 
Upon receiving a response, you should have the opportunity to extract valuable video metadata, including details like the title, description, and tags. Additionally, you can identify the download link for the highest quality version available.
 
 
 
This process should result in acquiring a video asset along with its associated metadata, often structured in XML format. Once these initial steps are executed, you may offer the user the choice to remove the video entry from OVP Source.
 
 
 
Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.
 
  
 
<!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below  -->
 
<!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below  -->
Line 23: Line 15:
 
<!-- Describe your workflow here with an overview of the different steps or processes involved-->
 
<!-- Describe your workflow here with an overview of the different steps or processes involved-->
  
Purpose: The purpose of the document is to outline a generic blueprint for the migration of video content from any Source On-line Video Platform (OVP) to a Destination OVP. This blueprint provides a high-level overview of the key steps and considerations involved in such a migration process.
+
==Purpose, Context and Content==
 
 
Context: In the context of digital content migration, this blueprint serves as a guide for initiating the transition from one OVP to another. It emphasizes the importance of retrieving video information from the source platform, including metadata extraction and potential deletion of content. The document sets the stage for a seamless migration process, aligning with the API documentation and specifications of the destination OVP.
 
 
<!-- Describe what your workflow is for - i.e. what it is designed to achieve, what the organisational context of the workflow is, and what content it is designed to work with -->
 
<!-- Describe what your workflow is for - i.e. what it is designed to achieve, what the organisational context of the workflow is, and what content it is designed to work with -->
  
 
+
==Evaluation/Review==
 
<!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate -->
 
<!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate -->
  
Some On-line Video Platforms (OVPs) and the sources of their API documentation:
+
==Further Information==
 
 
YouTube:
 
Source: [https://developers.google.com/youtube/registering_an_application]
 
Documentation URL: YouTube Data API Documentation
 
Description: YouTube provides a Data API that allows developers to access YouTube's features programmatically. It covers functionalities related to video uploads, playlists, video information retrieval, and more.
 
 
 
Vimeo:
 
Source: [https://developer.vimeo.com/api/reference]
 
Documentation URL: Vimeo API Documentation
 
Description: Vimeo's API documentation offers resources for integrating Vimeo's video hosting and sharing capabilities into applications. It provides access to features like video upload, video information retrieval, and advanced privacy controls.
 
 
 
Kaltura:
 
Source: [https://developer.kaltura.com/]
 
Documentation URL: Kaltura Developer Documentation
 
Description: Kaltura's Developer Documentation provides extensive resources for developers to leverage Kaltura's video platform capabilities. It covers video management, publishing, and monetization, as well as features like video uploading, player customization, and analytics.
 
 
 
Brightcove:
 
Source: [https://apis.support.brightcove.com/]
 
Documentation URL: Brightcove API Documentation
 
Description: Brightcove's API documentation provides comprehensive resources for developers to interact with the Brightcove platform programmatically. It includes features related to video publishing, content management, player customization, analytics, and monetization.
 
 
 
 
 
 
 
 
 
 
<!-- Provide any further information or links to additional documentation here -->
 
<!-- Provide any further information or links to additional documentation here -->
  

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: