This workshop goes over integrating your laptop/mobile device in a variety of Berkeley classrooms. We will also explore how to implement Zoom features in any classroom.
Join us for an overview of the bCourses learning management system (LMS) and its native (built-in) features, and gain familiarity with basic site setup and navigation.
Include Beginning of the Course and Mid-Semester Surveys
One way to learn more about your students and their experience in your course is to conduct surveys at the beginning and mid-semester points. A survey at the beginning of the course will allow you to get a better understanding of the challenges students may face in a remote instruction course, as well as provides an opportunity to learn more about each student on an individual basis. A mid-semester survey provides an opportunity to find out what’s working and what’s not in your course, and then make adjustments where needed. It...
Canvas Commons is a repository of digital resources that allows users to share and import content into a course site. The DLS Core Template is available in Canvas Commons to UC Berkeley users in the Instructor, TA, or Designer roles.
Follow the steps below to import the template to your new course site.
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.