Kaltura is a web-based video management platform that allows for the upload, editing, managing and sharing of videos and other media. Kaltura can be accessed from bCourses (Canvas).
Be prepared for some minor changes to the Kaltura integration with bCourses as we have upgraded, largely for security reasons. More specifically, we have upgraded from LTI 1.1 to 1.3. To learn more, see "Why Platforms and Tools Should Adopt LTI 1.3".
While the security improvements that come with the upgrade may not be obvious, the upgrade has led to one user interface change that will likely impact your use of Kaltura: thelocation of My Media ...
Join Digital Learning Services for an introductory workshop about Kaltura, a web-based video management platform that allows UC Berkeley instructors, students, and staff to upload, edit, manage and share videos and other media.
Please note: the change that this article describes has been rolled back as of 11/26/23. The current behavior is that Zoom alternative hosts do NOT become Kaltura co-hosts or co-collaborators.
An update to the Zoom to Kaltura integration made by Kaltura in early October benefits many Zoom users who have wanted colleagues (co-instructors, GSI’s,staff, etc) to be able to manage the recording files copied to Kaltura via the integration....
Starting January 6, 2021, at 8 am, whenever any campus member uses their UC Berkeley Zoom account to host a meeting that is recorded to the Zoom Cloud, the resulting recording will be automatically copied to UC Berkeley’s campus video management system, Kaltura. One of two things will happen:
If the Zoom account owner has no Kaltura account, the recording will be deleted from Kaltura within 24 hours (this does not affect the Zoom Cloud recording, which will still be available in Zoom for 30 days). It will never be shared with anybody else.
The Asset Library and Engagement Index tools are being rebuilt, and new versions will be available in the fall, while Whiteboards and Impact Studio are being retired.
Background:
The SuiteC tool set was developed as part of a grant-funded project and first piloted in 2015. Over time, technologies have modernized, class sizes have increased, and the performance of SuiteC has fallen behind, ultimately leading to the need to retire the current toolset.