External Applications (AKA Applications Interoperability) is a feature-set focused on providing workflows between different Kaltura MediaSpace (KMS) and/or KAF-based applications under the same Kaltura account. These workflows provide users an option to see, share, and receive information about content in one app while working in another app.
Below are examples of existing workflows and components that are shared between applications:
A user’s media collection is content that they uploaded, or content that was shared with them as collaborators. Each user's media collection is displayed under the “My Media” section in KMS or KAF-based applications. The My Media option is shared across applications, as long as the user ID on the entry is connected to the same Kaltura account. The user ID should be set either as an owner of the media or as a collaborator.
For users to view their My Media content in all applications that are connected to the same Kaltura account, the admin should check that the user ID passed to the application is the same. In KMS, the user ID is set via the auth module, while selecting the authentication method/s. In KAF instances, the user ID configuration is done via the hosted module during setup of the KAF application.
This feature will enable users to see where their My Media content is published in the current application, and also in any other application deployed under the same partner ID.
To turn the feature on in your application, follow the next steps:
- Choose a destination application where users will see the content from the source application. For example, if users in KMS should also see information about entries published in a KAF-based application.
- Navigate to the destination application admin page (e.g https://1234.mediaspace.kaltura.com/admin)
- Locate the Categories tab on the left or navigate to it directly. (e.g https://1234.mediaspace.kaltura.com/admin/config/tab/categories)
- Locate the “showExternalPublish” and set it to “Yes”.
- Click the “Add externalApplications" button.
- Fill in the relevant items:“applicationName” – This is the name users will see in My media representing the source application.
- “applicationRootCategory“ – Select the root category of the source application you want to connect to this destination.
- “type” – What type application is the source application: MediaSpace, KAF, or Other. (Other can be just a KMC category).
- Optional: Repeat 5,6 to connect more applications.
The above steps will enable the feature on the destination application handled only. If you wish to enable the feature on other applications, repeat the steps above for each application.
In the example below, the user is looking at My Media in MediaSpace and can see that content is also published in the Learning Site (LMS).
Lecture Capture Scheduling
The recording schedule module in Kaltura enables admin to automatically schedule recordings using Kaltura Classroom or any other device that supports Kaltura's scheduling capabilities. Recordings can be automatically published to a course media gallery or to a channel. The schedule is shared across applications. To enable publishing scheduled recordings from KMS to other KAF-based applications, the admin must enable those root categories as described in the Kaltura Scheduling Administrators Guide.
Note: In the LMS extensions, when using the BSE embed media feature, the embed itself will still be available on the page and users will see a player on that page. The only way to completely remove the embed is to enter the page on the LMS and remove it manually.
(Footnote 1) Also, in the LMSs we automatically add items that were added via the BSE to the in-context category for the following 2 actions:
- The owner embeds the media using the BSE.
- Any user watches the media.
To stop this from happening, set “autoRepublish” field to No.
If ‘autoRepublish’ is set to Yes, media that was made private might be added to a category again when a permitted user plays it.