Sakai

Sakai is Duke’s learning management system managed, through a collaboration between CIT and Duke Office of Information Technology (OIT). CIT provides system administration, strategic guidance, evaluation and implementation of new tools and upgrades and pedagogical support and training.

2016–17 Summary Of Duke Sakai Usage

  • 4,408 course sites and 421 project sites published 
  • 25,089 unique users 
  • 6,261 average unique users per day 
  • 1.97 average logins per person per day

Upgrading Sakai

In August of 2016, we conducted a major upgrade of Sakai to version 11. We also adopted a new rapid upgrade schedule that reflects our Sakai team’s new strategy for maintaining currency with the broader Sakai community.

  • August 16, 2016 – Sakai was upgraded from version 9.4 (2.9) to version 11.0
  • January 9, 2017  upgrade to version 11.2
  • March 12, 2017 upgraded to version 11.3

For more info on the major 2016 Sakai upgrade, read our detailed report.

Support

CIT handled 314 Sakai support requests in 2016–17. Other units at the university handled an additional 1,184 Sakai support requests during this timeframe. In 2016–17, significant impacts to CIT Sakai support came from:

  • Continuing to automate the manual course site creation process in Sakai, allowing more users to create their own sites without having to submit a Service Desk ticket, significantly reducing the overall number of tickets.
  • Upgrading to Sakai 11.0 close after the initial release, increasing the number of tickets resulting from bugs in the software

CIT also maintains Duke’s Sakai support site as an additional resource for Duke faculty and staff working with Sakai.

Attendance Tool

We evaluated and added the new Sakai Attendance tool (developed at the University of Dayton) as a response to faculty requests in the languages and other departments across campus.

User Interface Inventory Project

CIT and OIT’s Duke Web Services began a partnership with the Sakai Community to develop an updated style guide for Sakai to create consistency in the user interface across the platform.