Page Comparison

...

After more than a year of field testing this for (1) new courses and (2) reruns of pipelined courses, we have encountered various issues with the pipeline and its required workflow. 

Overview

• Current video pipeline is an inefficient, manual process. Process promotes waste, non-valued work, and ineffective employee/partner communications.
• Process relies on risky, ever-changing third-party hosting from YouTube that is not supported by a SLA.
• Process was created in early days of edX when org had < 5 partners. Given significant increase in partners, the current YouTube workflow is not sustainable or scalable.
• Current video process is fragile and produces ongoing fails for partners and learners.

Burden on edX Video Team

Some of which have been a time-consuming burden on the video team who have manually worked around the issues. For example:

• TBDCreating YouTube CMS Content Owner (CO) accounts per partner
• Numerous handoffs between media team and partners to create YouTube channels in CMS for each course
• Manually enabling every course for video upload by adding HEX ID to studio
• Resolving frequent YouTube errors due to YT backend changes

Errors experienced by Mobile Learners

...

1. Deleting unneeded videos from the library (

   Jira Legacy
   server JIRA (openedx.atlassian.net) serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key MA-326

   )
2. Better error states (

   Jira Legacy
   server JIRA (openedx.atlassian.net) serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key MA-769

   ,

   Jira Legacy
   server JIRA (openedx.atlassian.net) serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key MA-242

   )
3. Warning message when upload will be interrupted (

   Jira Legacy
   server JIRA (openedx.atlassian.net) serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key MA-333

   )

...

Transferring a Course from Edge to Prod Workflow:

...