Duke's eLearning Roadmap and the Sakai Transition

transcript

June 10-15, 2012

Growing Community; Growing Possibilities

Duke’s eLearning

Roadmap and the Sakai

Transition Shawn Miller, Duke University

Neal Caidin, Duke UniversityEd Gomes, Duke University

2012 Jasig Sakai Conference 2

Duke’s eLearning Roadmap

Charting Duke’s Academic Technology Landscape

Who◦ Technical Working Group◦ Functional Working Group◦ Faculty, staff, students

The eLearning Roadmap Group

Approach◦ Faculty input – focus groups, teams◦ Identify and create use cases◦ Environmental scan – what are other schools

doing, why?◦ Detailed analysis – functional comparisons;

technical documentation and resource needs; costs

Duke’s strategic priorities◦ Internationalization◦ Knowledge in the Service of Society◦ Interdisciplinarity◦ Collaboration and Connection

Central component – most heavily used system other than email and SISS

Gateway to other systems License with Blackboard coming up for

renewal The one technology that most faculty used

(even for non-teaching related tasks)

Start with the LMS

20121999

Flexibility Options Community Global

Why Sakai?

Migration and Transition

Goals and Phases

Phase 0: Mini-pilot UNC-CH

Phase 1: Fall 2011 limited release

200 faculty700 ‘staff’5000 students

“The schedule is awesome! One of myprofessors just loads everything needed for the day onto the schedule ‐ lecture notes, links to readings, things that are due, etc. It makes the site very user‐friendly.”

– Nicholas School student

23,000 Bb Course Sites migrated by the end of Fall 2011

Phase 2: Spring 2012

Bb Spring 2011 Bb Spring 2012 Sakai Spring 20120

831 845

Active LMS Coursesites (unique) Spring 2011 vs. 2012

Fall 2011 Jan-12 Sp 120

Total Sakai Users

900 active Sakai faculty 11,100 students

Activity StreamsOrganizing a transition effort

Organize teams to address different aspects of the migration

Teams reported to a larger Duke Sakai team comprised of members of all sub-teams

Sponsors: executive group overseeing the project address issues of scope, budget and high level communications

Members of teams comprised of staff from different units

Purpose

Technical & Hosting Strategy Integrations Migration Planning Communications Training & Documentation Support Model Governance

Activity Streams

Activity StreamsTechnical & Hosting Strategy

Hosting and working with vendors

New Partnerships Bring New Opportunities...

…and New Challenges

You still need local staff:◦ Research Sakai community resources (Jira,

Confluence, listservs)◦ Troubleshoot, identify and communicate issues

to vendors◦ Design, test and approve fixes and

developments◦ Define roles and permissions◦ Manage roster and integration issues

Activity StreamsIntegrations

Looking at the integrations more holistically may have been beneficial.

Involving the right business and technical people in integrations

Testing is critical.

Integrations

Kaltura media gallery Bb Parity

◦ Wimba voice tools using Basic LTI◦ Ereserves◦ Respondus LockDownBrowser◦ Export Official Grades to PeopleSoft◦ Eliminated some integrations (Library Guides)

Finding Post’em useful in some cases SISS, Shib, LDAP Toolkits*

Integrations

Tools & Integrations

Activity StreamsMigration Planning

Migration

Last 4 years of Bb content Worked with Longsight to use existing Bb-

Sakai import tool Multiple modifications to import tool code When is the quality of the migrated content

“good enough”? Also employed workarounds (bFree,

WebDav) . Size of archives, a number of sites over a

gig Total # of sites migrated – over 28,000

Migration

Activity StreamsCommunication

Communication

Activity StreamsTraining and Documentation

Training

Introduction to Sakai for Teaching

Sakai: Syllabus and Schedules

Sakai: Discussion Boards, Email and Communication

Sakai:Assignments

Sakai:Tests and Quizzes

Sakai:Providing feedback with the gradebook

Sakai Quick Start

Assignments, Assessments and Gradebook

Bye Bye Blackboard

0% 10% 20% 30% 40% 50% 60%

What workshops did participants attend?

Documentation

Activity StreamsSupport

Model based on Blackboard support Partnership between Duke OIT and CIT Local monitoring in additional to vendor-

provided monitoring Emergency response / vendor vs. local-

hosted differences Instructional Designer specifically hired for

the project.

Support

Activity StreamsGovernance

Project managers brought decisions to Sakai Team and sponsors

Transition Advisory Board Working on permanent governance model –

people shifting out of transition roles Standardizing a process for new

development requests, bug fixes and integrations.

IMPORTANT: open-source means different things to different people. Set expectations.

Governance

FutureJune 30th is coming… then what?

Self-service (course creation)◦ So far, so good◦ Benefits – do not have to wait for administrators,

no middle man; combine sites the way you want (instructors); open up project sites to campus community

◦ Some pushback from professional schools Toolkits

◦ Facilitating some batch creation of courses for professional schools (ex: all Law courses)

Course content linking problem Better streaming/media management Other bugs that need to wait for 2.8/2.9

Challenges…

Partnering with Fuqua School of Business (and other Duke developers)◦ Team assignments◦ Improving the schedule tool

Exploring Sakai Portfolios Sakai 2.8 or 2.9 in 2013 OAE?

Looking ahead…

Questions?

Yvonne BelangerCara BonnettDavid BrackenNeal CaidinDeborah DeyuliaSamantha EarpEd GomesLaurie Harris

Dwayne MarloweMark McCahillChris MeyerShawn MillerElise MuellerLynne O’BrienJosh QuanChristine Vucinich

Duke Sakai Team

Duke's eLearning Roadmap and the Sakai Transition

Education