...
If public & external video(Google Drive, Youtube & local etc.,) removed from the source it is getting removed from the content as well. (ECML content is still referring the external source so it is not playable).
Support to add local videos to ECML.
Key Design Problems:
Create a video as an asset
Create a streaming URL for videos
Google drive URL asset when we are creatingvideos asset creation
Backward compatibility
Migration
Design:
...
Create a video as an asset:
To add an image into ECML content we should create an asset of type image (image asset). All the image assets are part of the Sunbird Blob Storage so, they are always available and the Editor enables the creators to reuse existing images.
Similarly, if we should create any public video (local, youtube, google-drive etc,.) as an asset of type video (video asset) and enable the creator to browse and add it to ECML content. With this, all the videos will be available in the Sunbird Blob Storage
...
Below are the two drawbacks by following this approach.
If we create video assets and add them to ECML content, by default the videos are not streamable.
The platform takes a minimum of 1 hour time to generate
streamingUrl.
Option 1: Allow the creator to add videos that are having streamingUrl.
Option 2: Validate streamingUrl of video assets at the time of send for review.
a. Submitting for review should validate all the video assets are having streamingUrl or not. If not, it should show a message to try after some time.
b. There should be a handler to check all the video assets used in the content are having streamingUrl.
Option 3: ECML content streamingUrl generation as an async job.
The platform uses an async job to generate and set streamingUrl for Resource type content which has video as actual data (mimeType: video/*). Likewise, have an async job to set the streamingUrl for ECML content.
Below is the change in ECML to support video as an asset and streamingUrl.
...
| Code Block |
|---|
<stage>
<manifest>
<media assetId="do_31244094803238912023058"/>
</manifest>
<org.ekstep.video asset="do_31244094803238912023058" y="7.9" x="10.97" w="78.4" h="79.51" rotate="0" z-index="0" id="b2600e00-0395-4d63-a3a1-3957db2dec12">
<config>
<![CDATA[{"autoplay":true,"controls":true,"muted":false,"visible":true,"url":"/assets/public/content/do_31244094803238912023058/artifact/testvideo.mp4"}]]>
</config>
</org.ekstep.video>
</stage>
<manifest>
<media id="do_31244094803238912023058" src="/assets/public/content/do_31244094803238912023058/artifact/testvideo.mp4" streamingUrl="" type="video"/>
</manifest> |
Solution 2: Make Consistent behavior on both Mobile & Portal
...
Google drive videos asset creation:
At the time of adding Google drive videos using URL, the platform will download and create an asset for the same in the background. Because the user will give metadata like name, language etc., while adding itself.
Create a streaming URL for videos:
Option 1: Allow the creator to add videos to the content only videos that are having streamingUrl.
Option 2: ECML content streamingUrl generation as an async job.
The platform uses an async job to generate and set streamingUrl for Resource type content which has video as actual data (mimeType: video/*). Likewise, have an async job to set the streamingUrl for ECML content.
Backward compatibility:
If the asset attribute is not present in the video tag, we will look for CDATA's URL attribute.
If the asset attribute is present we will load it from media tag with the corresponding assetId.
Migration:
We need to identify all ECML content which is having Google drive / Youtube URL and Will create assets for those videos and update ECML.