kaltura 7.x-3.1

This phase is focused on long-term and core module architecture changes that will support all standard Drupal workflows and ensure the compatibility of the Kaltura module with Drupal core and community-modules.

The changes in this phase also lays the foundation for more efficient data-sharing and replication between Kaltura and Drupal, that will in turn power more reliable and complex workflows and applications based on the module.

A major architectural change was made by leveraging the Entity API. This change now allows users and developers to:

• extend Kaltura entities with custom fields
• map and synchronize Kaltura entry metadata with Drupal’s custom fields
• create views and searches based on Kaltura metadata

The module now has an API to allow other modules to hook into it and extend the Kaltura module’s functionality. One of the use cases, for example, is to pull custom Kaltura metadata and update different Drupal entities during the synchronization process.

Other bugfixes, code cleanups and small improvements including:

• one-click entries synchronization between KMC and Drupal
• removed sensitive access credentials from admin UI
• ability to override player settings on a per page basis
• switching the old Kaltura contribution wizard with a newer HTML5 upload library
• cosmetic improvements of admin UI