radiofreeasia/rfa.kaltura2

Kaltura Integration with Plone 5 and Python 3

rfa.kaltura2

For creating video content in Plone CMS while leveraging the Kaltura Video Platform

Features

• Add and Upload videos through the Plone CMS
• Use Kaltura Players for displaying videos
• Use Kaltura as a Video DAM (Digital Asset Manager)
• Syncronize video metadata between Kaltura KMC and Plone
• Plone 5.2 and Python 3 compatable

Examples

Most video content at www.rfa.org is stored on Kaltura but rendered through Plone CMS. New Videos can be created in Plone and Videos can be treated like any other content type in Plone, yet storage, transcoding, players and delivery are configured in Kaltura.

Documentation

Documentation is lacking. I'm sorry.

Installation

Install rfa.kaltura2 by adding it to your buildout:

[buildout]

...

eggs =
    rfa.kaltura2

and then running bin/buildout

Contribute

• Issue Tracker: https://github.com/RadioFreeAsia/rfa.kaltura2/issues
• Source Code: https://github.com/RadioFreeAsia/rfa.kaltura2
• Documentation: https://docs.plone.org/totallymissinghostingdocsatmsorry

Support

If you are having issues, please let us know through the plone community forums. Tag @flipmcf

License

The project is licensed under the GPLv2. copyright both Radio Free Asia and Michael McFadden (flipmcf)

rfa.kaltura2's Issues

kconnect() is really inefficient:

connect is called all over the place in rfa.kaltura2.
It's designed to return a client (and session key) that can be used to communicate to the API, and it gets that session key through an authentication dance.

Instead of holding onto that session key and re-using it within the plone application (like save the session key it to the registry and re-use it to create more client connections) it asks for a new one on every call to kconnect() and re-does the authentication dance.

To make matters worse, kconnect() tells the kaltura server to keep that session key authorized for 86400 (one day) even though we throw it away and immediately ask for a new one on every call.

This is embarrassing and needs to be fixed.

Playlists Don't work

Playlists are not implemented. They were broken and not used in rfa.kaltura so simply not implemented in rfa.kaltura2

Add Distribution Action

As a Plone Editor (user of content management system)
I want to be able to distribute a video (to youtube) on-demand
So that I don't have to login to the KMC or understand KMC-specific errors

I invision a button on the action bar or within the actions drop-down called "distribute"
This leads the user to a distribution view, which will query the KMC for available distribution channels and allow the user to Fire a distribution request to the KMC for the video in context.

Use Enums for Kaltura publication status

rfa.kaltura2/src/rfa/kaltura2/kutils.py

Line 436 in 3b87589

elif status in (3,1,5):

rfa.kaltura2/src/rfa/kaltura2/kutils.py

Line 215 in 3b87589

kfilter.setModerationStatusIn('2,5,6,1')

Don't use magic numbers 1,2,3,4,5

Replace those with the actual enums defined by the Kaltura API:

for example,

from KalturaClient.Plugins.Core import KalturaEntryModerationStatus

KalturaEntryModerationStatus.PENDING_MODERATION

see events.py - that does it right.

entryID should not be a field on Video Object

The canonical way to get the entry id should be 'object.entryId'

The 'backend' way to get the entry id should be 'object.KalturaObject.getId()' - but this shouldn't be used under normal circumstances.

object.entryId getter (dexterity) needs to be created and used, and should under most circumstances, simply call 'object.KalturaObject.getId()' and handle all exceptions that may occur due to that call.

This was the behavior in rfa.kaltura in Archetypes.
https://github.com/RadioFreeAsia/rfa.kaltura/blob/9eb2a48178280bafbb1c2c665bd74ab14f99ceb6/rfa/kaltura/content/base.py#L12
https://github.com/RadioFreeAsia/rfa.kaltura/blob/9eb2a48178280bafbb1c2c665bd74ab14f99ceb6/rfa/kaltura/content/base.py#L108

This caused a bug that was just fixed by this commit:
3b87589

Deleting Media Entry in KMC - Plone object doesn't react

Somehow, a plone object must know if a media object on Kaltura was deleted, and the URL is no longer valid. Poll the KMC for the media entry (on some specified time) and update the object state in Plone to reflect that it's no longer valid. Probably automatically unpublish the object so the Plone content doesn't show up and break the site.