Workflow:OVP migration flow - Revision history

172.104.134.96 at 21:18, 16 October 2023

2023-10-16T21:18:29Z

Jose Velazquez: /* Evaluation/Review */

2023-10-16T20:58:41Z

Evaluation/Review

Jose Velazquez at 20:04, 16 October 2023

2023-10-16T20:04:31Z

Jose Velazquez at 20:02, 16 October 2023

2023-10-16T20:02:35Z

Jose Velazquez: /* Further Information */

2023-10-16T19:59:59Z

Further Information

Jose Velazquez: /* Purpose, Context and Content */

2023-10-16T19:48:23Z

Purpose, Context and Content

Jose Velazquez at 19:44, 16 October 2023

2023-10-16T19:44:51Z

Jose Velazquez at 18:40, 16 October 2023

2023-10-16T18:40:24Z

Jose Velazquez at 18:38, 16 October 2023

2023-10-16T18:38:58Z

Jose Velazquez at 18:34, 16 October 2023

2023-10-16T18:34:29Z

@@ Line 9: / Line 9: @@
 OVP migration flow - an agnostic blueprint
-To initiate the transition from any given Source 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.
+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.

@@ Line 28: / Line 28: @@
 <!-- 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 -->

@@ Line 34: / Line 34: @@
 YouTube:
 Source: [https://developers.google.com/youtube/registering_an_application]
 Documentation URL: YouTube Data API Documentation
@@ Line 40: / Line 39: @@
 Vimeo:
 Source: [https://developer.vimeo.com/api/reference]
 Documentation URL: Vimeo API Documentation

@@ Line 35: / Line 35: @@
 YouTube:
-Source: [https://support.brightcove.com/developer YouTube Data API Documentation]
+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.
@@ Line 41: / Line 41: @@
 Vimeo:
-Source: [https://developer.vimeo.com/api/reference Vimeo API Documentation]
+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/ Kaltura Developer Documentation]
+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/ Brightcove API Documentation]
+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.

@@ Line 31: / Line 31: @@
 <!-- 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 -->
-==Further Information==
+Some On-line Video Platforms (OVPs) and the sources of their API documentation:
 <!-- Provide any further information or links to additional documentation here -->

@@ Line 23: / Line 23: @@
 <!-- Describe your workflow here with an overview of the different steps or processes involved-->
-==Purpose, Context and Content==
+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.
 <!-- 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 -->

@@ Line 1: / Line 1: @@
 {{Infobox COW
 |status=Production
-|tools=python, ovp, apis
+|tools=python, OVP, API
 |input=Media assets and descriptive metadata in source OVP.
 |output=Media assets and descriptive metadata in destination OVP.

@@ Line 7: / Line 7: @@
 |organisationurl=https://ladigitalizadora.org/
 }}
-OVP migration flow Blueprint
+OVP migration flow - an agnostic blueprint
 To initiate the transition from any given Source 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.

@@ Line 9: / Line 9: @@
 OVP migration flow Blueprint
-To initiate the transition from any given Source On-line Video Platform Source to a Destination OVP, the first step involves retrieving video information from the OVP Source. You can achieve this by making a GET request to the OVP Source's API authenticating against it, typically using your provided access token and video ID. This request would typically be directed to a generic API endpoint.
+To initiate the transition from any given Source 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 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.
+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 can offer the user the choice to remove the video entry from OVP Source.
+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.