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, | + | |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 | + | To initiate the transition from an 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. |
− | + | 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. | |
− | + | 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 | ||
Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications. | Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications. | ||
Line 23: | Line 21: | ||
<!-- 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 | + | ==Purpose, Context and Content== |
− | |||
− | Context | ||
<!-- 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 --> | ||
− | + | ==Further Information== | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<!-- Provide any further information or links to additional documentation here --> | <!-- Provide any further information or links to additional documentation here --> | ||