https://coptr.digipres.org/api.php?action=feedcontributions&feedformat=atom&user=Jose+Velazquez 2026-04-07T05:44:15Z User contributions MediaWiki 1.35.14 https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6272 2024-04-28T08:32:32Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> &lt;img src=&quot;https://media.licdn.com/dms/image/D4E12AQGakJHfY4Vmlw/article-inline_image-shrink_1500_2232/0/1712742432090?e=1718236800&amp;v=beta&amp;t=fv8JNxQgpGJ-Y343AGpNSKFJBCI8SdaYXqRC4VDum0U&quot; alt=&quot;LinkedIn Image&quot;&gt;<br /> <br /> <br /> &lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> Github &amp; Python Implementation Example: https://github.com/josev2046/WatchFolderAutomation<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6271 2024-04-28T08:31:19Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> &lt;img src=&quot;https://media.licdn.com/dms/image/D4E12AQGakJHfY4Vmlw/article-inline_image-shrink_1500_2232/0/1712742432090?e=1718236800&amp;v=beta&amp;t=fv8JNxQgpGJ-Y343AGpNSKFJBCI8SdaYXqRC4VDum0U&quot; alt=&quot;LinkedIn Image&quot;&gt;<br /> <br /> <br /> &lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> Github: https://github.com/josev2046/WatchFolderAutomation<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6270 2024-04-10T11:23:19Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> &lt;img src=&quot;https://media.licdn.com/dms/image/D4E12AQGakJHfY4Vmlw/article-inline_image-shrink_1500_2232/0/1712742432090?e=1718236800&amp;v=beta&amp;t=fv8JNxQgpGJ-Y343AGpNSKFJBCI8SdaYXqRC4VDum0U&quot; alt=&quot;LinkedIn Image&quot;&gt;<br /> <br /> <br /> &lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6269 2024-04-10T11:21:45Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> &lt;img src=&quot;https://media.licdn.com/dms/image/D4E12AQGakJHfY4Vmlw/article-inline_image-shrink_1500_2232/0/1712742432090?e=1718236800&amp;v=beta&amp;t=fv8JNxQgpGJ-Y343AGpNSKFJBCI8SdaYXqRC4VDum0U&quot; alt=&quot;LinkedIn Image&quot;&gt;<br /> <br /> <br /> &lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6268 2024-04-10T11:16:14Z

<p>Jose Velazquez: /* Workflow Description */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> &lt;br&gt;<br /> <br /> ┌──────┐ ┌──────┐ ┌───┐ <br /> │Script│ │Folder│ │OVP│ <br /> └──┬───┘ └──┬───┘ └─┬─┘ <br /> ┌┴┐ Start monitoring folder │ │ <br /> │ │ ──────────────────────────────────────────────────&gt;│ │ <br /> │ │ │ │ <br /> │ │ │ │ <br /> ╔═══════╤═════════════╪═╪════════════════════════════════════════════════════╪════════════════╪═════════════════════╗<br /> ║ LOOP │ Check for new files │ │ ║<br /> ╟───────┘ │ │ │ │ ║<br /> ║ │ │ New file detected │ │ ║<br /> ║ │ │ &lt;──────────────────────────────────────────────────│ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ ╔══════╤════╪═╪════════════════════════════════════════════════════╪═════════════╗ │ ║<br /> ║ ║ ALT │ File is MP4 video │ ║ │ ║<br /> ║ ╟──────┘ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Check for corresponding XML file │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │ XML file found │ ║ │ ║<br /> ║ ║ │ │ &lt;──────────────────────────────────────────────────│ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Extract metadata (title, description, tags) │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ╠═══════════╪═╪════════════════════════════════════════════════════╪═════════════╣ │ ║<br /> ║ ║ [File is XML] │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Check for corresponding MP4 file │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │ MP4 file found │ ║ │ ║<br /> ║ ║ │ │ &lt;──────────────────────────────────────────────────│ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Associate metadata (title, description, tags) │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ╚═══════════╪═╪════════════════════════════════════════════════════╪═════════════╝ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │────┐ │ │ ║<br /> ║ │ │ │ Check if file pair has already been processed │ │ ║<br /> ║ │ │&lt;───┘ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ ╔══════╤════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╗ ║<br /> ║ ║ ALT │ File pair not processed │ │ ║ ║<br /> ║ ╟──────┘ │ │ │ │ ║ ║<br /> ║ ║ │ │ Upload video to OVP with metadata │ │ ║ ║<br /> ║ ║ │ │ ───────────────────────────────────────────────────────────────────&gt;│ ║ ║<br /> ║ ║ │ │ │ │ ║ ║<br /> ║ ║ │ │ Upload successful │ │ ║ ║<br /> ║ ║ │ │ &lt;─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─│ ║ ║<br /> ║ ║ │ │ │ │ ║ ║<br /> ║ ║ │ │────┐ │ │ ║ ║<br /> ║ ║ │ │ │ Add file pair to processed list │ │ ║ ║<br /> ║ ║ │ │&lt;───┘ │ │ ║ ║<br /> ║ ╠═══════════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╣ ║<br /> ║ ║ [File pair already processed] │ │ ║ ║<br /> ║ ║ │ │────┐ │ │ ║ ║<br /> ║ ║ │ │ │ Skip processing │ │ ║ ║<br /> ║ ║ │ │&lt;───┘ │ │ ║ ║<br /> ║ ╚═══════════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╝ ║<br /> ╚═════════════════════╪═╪════════════════════════════════════════════════════╪════════════════╪═════════════════════╝<br /> ┌─└┬┘──┐ ┌──┴───┐ ┌─┴─┐ <br /> │Script│ │Folder│ │OVP│ <br /> └──────┘ └──────┘ └───┘ <br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6267 2024-04-10T11:11:25Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:Watch Folder Sequence Diagram UML.png|Watch Folder Sequence Diagram UML<br /> ]]&lt;br&gt;<br /> <br /> ┌──────┐ ┌──────┐ ┌───┐ <br /> │Script│ │Folder│ │OVP│ <br /> └──┬───┘ └──┬───┘ └─┬─┘ <br /> ┌┴┐ Start monitoring folder │ │ <br /> │ │ ──────────────────────────────────────────────────&gt;│ │ <br /> │ │ │ │ <br /> │ │ │ │ <br /> ╔═══════╤═════════════╪═╪════════════════════════════════════════════════════╪════════════════╪═════════════════════╗<br /> ║ LOOP │ Check for new files │ │ ║<br /> ╟───────┘ │ │ │ │ ║<br /> ║ │ │ New file detected │ │ ║<br /> ║ │ │ &lt;──────────────────────────────────────────────────│ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ ╔══════╤════╪═╪════════════════════════════════════════════════════╪═════════════╗ │ ║<br /> ║ ║ ALT │ File is MP4 video │ ║ │ ║<br /> ║ ╟──────┘ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Check for corresponding XML file │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │ XML file found │ ║ │ ║<br /> ║ ║ │ │ &lt;──────────────────────────────────────────────────│ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Extract metadata (title, description, tags) │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ╠═══════════╪═╪════════════════════════════════════════════════════╪═════════════╣ │ ║<br /> ║ ║ [File is XML] │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Check for corresponding MP4 file │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │ MP4 file found │ ║ │ ║<br /> ║ ║ │ │ &lt;──────────────────────────────────────────────────│ ║ │ ║<br /> ║ ║ │ │ │ ║ │ ║<br /> ║ ║ │ │────┐ │ ║ │ ║<br /> ║ ║ │ │ │ Associate metadata (title, description, tags) │ ║ │ ║<br /> ║ ║ │ │&lt;───┘ │ ║ │ ║<br /> ║ ╚═══════════╪═╪════════════════════════════════════════════════════╪═════════════╝ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │────┐ │ │ ║<br /> ║ │ │ │ Check if file pair has already been processed │ │ ║<br /> ║ │ │&lt;───┘ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ │ │ │ │ ║<br /> ║ ╔══════╤════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╗ ║<br /> ║ ║ ALT │ File pair not processed │ │ ║ ║<br /> ║ ╟──────┘ │ │ │ │ ║ ║<br /> ║ ║ │ │ Upload video to OVP with metadata │ │ ║ ║<br /> ║ ║ │ │ ───────────────────────────────────────────────────────────────────&gt;│ ║ ║<br /> ║ ║ │ │ │ │ ║ ║<br /> ║ ║ │ │ Upload successful │ │ ║ ║<br /> ║ ║ │ │ &lt;─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─│ ║ ║<br /> ║ ║ │ │ │ │ ║ ║<br /> ║ ║ │ │────┐ │ │ ║ ║<br /> ║ ║ │ │ │ Add file pair to processed list │ │ ║ ║<br /> ║ ║ │ │&lt;───┘ │ │ ║ ║<br /> ║ ╠═══════════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╣ ║<br /> ║ ║ [File pair already processed] │ │ ║ ║<br /> ║ ║ │ │────┐ │ │ ║ ║<br /> ║ ║ │ │ │ Skip processing │ │ ║ ║<br /> ║ ║ │ │&lt;───┘ │ │ ║ ║<br /> ║ ╚═══════════╪═╪════════════════════════════════════════════════════╪════════════════╪═══════════╝ ║<br /> ╚═════════════════════╪═╪════════════════════════════════════════════════════╪════════════════╪═════════════════════╝<br /> ┌─└┬┘──┐ ┌──┴───┐ ┌─┴─┐ <br /> │Script│ │Folder│ │OVP│ <br /> └──────┘ └──────┘ └───┘ <br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6266 2024-04-10T11:10:33Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:Watch Folder Sequence Diagram UML.png|Watch Folder Sequence Diagram UML<br /> ]]&lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:Watch_Folder_Ingest&diff=6265 2024-04-10T10:45:43Z

<p>Jose Velazquez: A simple approach to bulk media and metadata ingests</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=Python, OVP, MAM, DAM, API, OTT<br /> |input=Media assets and descriptive metadata in Watch Folder.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:Watch Folder Sequence Diagram UM.png|Watch Folder Sequence Diagram UML<br /> ]]&lt;br&gt;<br /> <br /> I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.<br /> <br /> ==Purpose, Context and Content==<br /> Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.<br /> <br /> Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6149 2023-10-16T20:58:41Z

<p>Jose Velazquez: /* Evaluation/Review */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> 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.<br /> <br /> 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.<br /> &lt;!-- 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 --&gt;<br /> <br /> <br /> &lt;!-- 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 --&gt;<br /> <br /> Some On-line Video Platforms (OVPs) and the sources of their API documentation:<br /> <br /> YouTube:<br /> Source: [https://developers.google.com/youtube/registering_an_application]<br /> Documentation URL: YouTube Data API Documentation<br /> 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.<br /> <br /> Vimeo:<br /> Source: [https://developer.vimeo.com/api/reference]<br /> Documentation URL: Vimeo API Documentation<br /> 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.<br /> <br /> Kaltura:<br /> Source: [https://developer.kaltura.com/]<br /> Documentation URL: Kaltura Developer Documentation<br /> 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.<br /> <br /> Brightcove:<br /> Source: [https://apis.support.brightcove.com/]<br /> Documentation URL: Brightcove API Documentation<br /> 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.<br /> <br /> <br /> <br /> <br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6148 2023-10-16T20:04:31Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> 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.<br /> <br /> 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.<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> Some On-line Video Platforms (OVPs) and the sources of their API documentation:<br /> <br /> YouTube:<br /> Source: [https://developers.google.com/youtube/registering_an_application]<br /> Documentation URL: YouTube Data API Documentation<br /> 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.<br /> <br /> Vimeo:<br /> Source: [https://developer.vimeo.com/api/reference]<br /> Documentation URL: Vimeo API Documentation<br /> 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.<br /> <br /> Kaltura:<br /> Source: [https://developer.kaltura.com/]<br /> Documentation URL: Kaltura Developer Documentation<br /> 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.<br /> <br /> Brightcove:<br /> Source: [https://apis.support.brightcove.com/]<br /> Documentation URL: Brightcove API Documentation<br /> 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.<br /> <br /> <br /> <br /> <br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6147 2023-10-16T20:02:35Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> 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.<br /> <br /> 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.<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> Some On-line Video Platforms (OVPs) and the sources of their API documentation:<br /> <br /> YouTube:<br /> <br /> Source: [https://developers.google.com/youtube/registering_an_application]<br /> Documentation URL: YouTube Data API Documentation<br /> 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.<br /> <br /> Vimeo:<br /> <br /> Source: [https://developer.vimeo.com/api/reference]<br /> Documentation URL: Vimeo API Documentation<br /> 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.<br /> <br /> Kaltura:<br /> Source: [https://developer.kaltura.com/]<br /> Documentation URL: Kaltura Developer Documentation<br /> 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.<br /> <br /> Brightcove:<br /> Source: [https://apis.support.brightcove.com/]<br /> Documentation URL: Brightcove API Documentation<br /> 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.<br /> <br /> <br /> <br /> <br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6146 2023-10-16T19:59:59Z

<p>Jose Velazquez: /* Further Information */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> 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.<br /> <br /> 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.<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> Some On-line Video Platforms (OVPs) and the sources of their API documentation:<br /> <br /> YouTube:<br /> <br /> Source: [https://support.brightcove.com/developer YouTube Data API Documentation]<br /> Documentation URL: YouTube Data API Documentation<br /> 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.<br /> <br /> Vimeo:<br /> <br /> Source: [https://developer.vimeo.com/api/reference Vimeo API Documentation]<br /> Documentation URL: Vimeo API Documentation<br /> 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.<br /> <br /> Kaltura:<br /> Source: [https://developer.kaltura.com/ Kaltura Developer Documentation]<br /> Documentation URL: Kaltura Developer Documentation<br /> 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.<br /> <br /> Brightcove:<br /> Source: [https://apis.support.brightcove.com/ Brightcove API Documentation]<br /> Documentation URL: Brightcove API Documentation<br /> 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.<br /> <br /> <br /> <br /> <br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6145 2023-10-16T19:48:23Z

<p>Jose Velazquez: /* Purpose, Context and Content */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> 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.<br /> <br /> 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.<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6144 2023-10-16T19:44:51Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, OVP, API<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=User:Jose_Velazquez&diff=6143 2023-10-16T19:42:56Z

<p>Jose Velazquez: Created page with &quot;José Velázquez has been involved in and around the world of digital video acquisition, compression and delivery since its coming of age in the early 90s. Trained at the BBC...&quot;</p> <hr /> <div>José Velázquez has been involved in and around the world of digital video acquisition, compression and delivery since its coming of age in the early 90s. Trained at the BBC in broadcast operations and TV production, he also holds an MA in Documentary Research for Film and TV (London College of Communication, UAL) Since 2016, José teaches as associate lecturer in the interdisciplinary programme for the Masters Degree in Digital Humanities at Univesity Pablo de Olavide, Seville, focusing on the digitisation, indexing and cognitive analysis of audiovisual archives.<br /> <br /> José helps major broadcasters deploy AI-infused solutions that deliver deeper understanding and insights from their existing media collections, and has led the inception of groundbreaking AI projects at renowned networks such as the BBC, CannesLions and MediaPro. In 2019 José was presented with an IBM Recognition Award for the innovative use of Natural Language Processing technologies in media archives (Watson Media). He remains passionate about #Accessibility, #Preservation and #AI Ethics, and is actively engaged in technology that is more human, empathetic and adaptive to everyone.<br /> <br /> His project, DOKUMENTA.VIDEO: #BLACKLIVES, in collaboration with Dr David Dunkley-Gyimah, Senior Lecturer at Cardiff School of Journalism, was selected in 2020 by the FIAT/IFTA Save Your Archive Program. He is also an active member of La Digitalizadora de la Memoria Colectiva, a network of media professionals and activists set out to safeguard the audiovisual legacy of Spanish grassroots movements during the last third of the 20th century, supporting its preservation and dissemination through collective action.<br /> <br /> https://dokumenta.video<br /> <br /> https://www.linkedin.com/in/jvelazquez/</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6142 2023-10-16T18:40:24Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow - an agnostic blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6141 2023-10-16T18:38:58Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow Blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6140 2023-10-16T18:34:29Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> OVP migration flow Blueprint<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6139 2023-10-16T18:29:38Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Following this, the natural progression leads into the OVP Destination ingest process, aligning with their API documentation and specifications.<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6138 2023-10-16T18:23:03Z

<p>Jose Velazquez: </p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6137 2023-10-16T18:19:38Z

<p>Jose Velazquez: /* Workflow Description */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[AVmigrationflow.png|OVP migration flow UML]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6136 2023-10-16T18:17:41Z

<p>Jose Velazquez: /* Workflow Description */</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[AVmigrationflow.png|Textual description]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=Workflow:OVP_migration_flow&diff=6135 2023-10-16T18:13:22Z

<p>Jose Velazquez: Created page with &quot;{{Infobox COW |status=Production |tools=python, ovp, apis |input=Media assets and descriptive metadata in source OVP. |output=Media assets and descriptive metadata in destinat...&quot;</p> <hr /> <div>{{Infobox COW<br /> |status=Production<br /> |tools=python, ovp, apis<br /> |input=Media assets and descriptive metadata in source OVP.<br /> |output=Media assets and descriptive metadata in destination OVP.<br /> |organisation=La Digitalizadora de la Memoria Colectiva<br /> |organisationurl=https://ladigitalizadora.org/<br /> }}<br /> ==Workflow Description==<br /> <br /> &lt;!-- To add an image of your workflow, open the &quot;Upload File&quot; 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 &quot;workflow.png&quot; with the name of your file. Replace the text &quot;Textual description&quot; 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 --&gt;<br /> <br /> [[File:workflow.png|Textual description]]&lt;br&gt;<br /> <br /> &lt;!-- Describe your workflow here with an overview of the different steps or processes involved--&gt;<br /> <br /> ==Purpose, Context and Content==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Evaluation/Review==<br /> &lt;!-- 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 --&gt;<br /> <br /> ==Further Information==<br /> &lt;!-- Provide any further information or links to additional documentation here --&gt;<br /> <br /> &lt;!-- Add four tildes below (&quot;~~~~&quot;) to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --&gt;<br /> <br /> &lt;!-- Note that your workflow will be marked with a CC3.0 licence --&gt;</div>

Jose Velazquez https://coptr.digipres.org/index.php?title=File:AVmigrationflow.png&diff=6134 2023-10-16T18:07:04Z

<p>Jose Velazquez: Audiovisual Asset Transfer Sequence Diagram with Ingestion UML</p> <hr /> <div>== Summary ==<br /> Audiovisual Asset Transfer Sequence Diagram with Ingestion UML</div>

Jose Velazquez