Sakai History Courseware Management System Started in 2004 Michigan, Indiana, Stanford, MIT and Berkeley Mellon Foundation Grant Release 2.5 this month 15% of Research Universities in US use Sakai
Why Start Sakai? 5 Schools with Homegrown LMS Inefficient to build 5 systems Wanted to maintain control Experts in teaching and learning Desire to work together and share knowledge
Sakai Vision By working together we can get more (for less?)
Why Sakai? Stanford wrote about 20% of the original code in Sakai. What we have received in return is five times what we have put in, a tremendous return on investment. The value of community source is very real to us. Lois Brooks Director of Academic Computing Stanford University Lois Brooks Director of Academic Computing Stanford University Coursework, Stanford University
Defining Sakai: Product Vision COURSE MANAGEMENT — all the tools of a modern course management system. RESEARCH & COLLABORATION — project sites for research and work group collaboration. SAKAIBRARY — Library-led component to add citations directly into Sakai. PORTFOLIOS — Open Source Portfolio (OSP) is a core part of Sakai. Course Management Portfolios Sakaibrary Research & Collaboration
Sakai software Sakai JSR-168 portlet Sakai as a Mac desktop app.
Defining Sakai: Community COMPOSITION — educational institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives. GOALS — work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration in education. VALUES — knowledge sharing, information transparency, meritocracy. Educational Institutions Commercial Affiliates Open Source Standards Bodies Standards Bodies
Sakai on the ground 200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users
Sakai on the ground UsersInstitutions 130,000+Indiana, UNISA 60,000+Michigan 11,000 - 50,000 Berkeley, Cape Town, Etudes Consortium, New England (AU), Valencia, Virginia Tech, Yale 1,000 - 10,000 Cambridge, Cerritos, Charles Sturt, Fernando Pessoa, Lleida, Mount Holyoke, North-West, Rice, Roskilde, Rutgers, Saginaw Valley, UC Merced, Whitman, Arteveldehogeschool CTOOLS, University of Michigan First production Sakai deployment, 2004
Defining Sakai: Code FOSS — open-source software free to acquire, use, modify & distribute; no fees or royalties; Apache-style license encourages wide range of use including commercial applications. SOA — an extensible, service- oriented architecture & set of tools & services with clear abstraction boundaries. Sakai's CLE offers interoperability, reliability, extensibility & scalability. Java 1.5 Oracle 9i/10g MySQL 4.1/5.x DB2 Oracle 9i/10g MySQL 4.1/5.x DB2 SpringHibernateTomcat 5.5.xJSF/JSP/RSFSakai 2.x Apache HTTP Server SSL mod_jk WEBISO Virtual hosting Sakai consists of technologies common to Java enterprise environments
Sakai Community Source OPEN LICENSING — Sakai’s software is made available under the terms of the ECL, a variant of the Apache license. The ECL encourages a wide range of use including the production of derivative work in the commercial space. NO FEES OR ROYALTIES — Sakai is free to acquire, use, copy, modify, merge, publish, redistribute & sublicense for any purpose provided our copyright notice & disclaimer are included in all copies of the original or derivative work(s). NO “COPYLEFT” RESTRICTIONS — unlike GPL redistributed derivative works are neither required to adopt the Sakai license nor publish the source code as open-source. EDUCATIONAL COMMUNITY LICENSE (ECL)
Sakai Developers June 2007 Nov 2006 http://www.ohloh.net/projects/3551 33.62% increase
Defining Sakai: Foundation MISSION — manage & protect intellectual property; provide basic infrastructure & small staff; help coordinate design, development, testing & distribution of software; champion open source & open standards. GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations. PARTNERS — over 100 member organizations contribute $10K per year ($5K for smaller institutions). BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.
Sakai & Moodle Sakai Java More than teaching Community development Apache license Enterprise application Moodle PHP Teaching focused Centralized development GPL license Ease of installation
Why Choose Sakai? Reduced cost, Improved Service No License Fees Support separate from license Control Long-term risk management Platform for innovation Respond to local needs Common direction Solve issues with peer institutions Find new uses from far afield Extremely flexible Course Management System Collaboration and research uses Always customizable Contribute to the community Consistent with mission But get back more than you give
Why Sakai? UCT decided to move to open source in 2004, migrating from WebCT & a home-grown system. Open source offers the advantages of flexibility & avoids the risks of vendor lock- in & escalating license costs. We were attracted to Sakai by the size & expertise of the community around it. Stephen Marquard, Learning Technologies Coordinator, University of Cape Town
Cape Town Declaration We are on the cusp of a global revolution in teaching and learning. Educators worldwide are developing a vast pool of educational resources on the Internet, open and free for all to use. These educators are creating a world where each and every person on earth can access and contribute to the sum of all human knowledge. They are also planting the seeds of a new pedagogy where educators and learners create, shape and evolve knowledge together, deepening their skills and understanding as they go. This emerging open education movement combines the established tradition of sharing good ideas with fellow educators and the collaborative, interactive culture of the Internet. It is built on the belief that everyone should have the freedom to use, customize, improve and redistribute educational resources without constraint. Educators, learners and others who share this belief are gathering together as part of a worldwide effort to make education both more accessible and more effective.
Values in Education Open and free access Knowledge sharing Quality, regardless of wealth Meritocracy. The best students advance. These are the values of open source
Proprietary Vendors Who doesn’t get the “Unlimited Edition” Learning Technology?
Teaching & Learning are Special Financial software is not the same Teaching & Learning (and libraries!) are the core mission of the university, not an administrative function Open source should be the default for Teaching & Learning It has to do the job well, of course (and it does!) We are the experts! What path do you want to take?
Sakai Foundation Goals Provide Flexibility Facilitate Innovation Reduce Total Cost Increase User Satisfaction Promote Openness for education by community members not just eliminate license fees users, developers, admins in software, content, standards
2008 Foundation Focus Create the highest quality core software as a base for community innovation by focusing resources on the fundamentals Engage new members of the community contributors & adopters & content providers by communicating our successes and directions
What Adoption Numbers? Moodle statistics are often referenced These aren’t right for us. As of Nov 2007 Number of Courses/Installation = approx 40 Number of Users/Installation = approx 400 (They aren’t wrong for Moodle.)
Sakai Adoption Metrics Total enrollment of Higher Ed institutions that have adopted Sakai as their primary CLE
Some US Adoption Numbers R1 (RU/VH) institutions who have adopted Sakai as their primary CMS account for 13+% of total enrollments. 318,000 Enrollments
Some US Adoption Numbers Overall institutions who have adopted Sakai account for approximately 4.3% of US enrollments Approx. 750K of 16M
Adoption Goal Double # of enrollments using Sakai in US From 750 thousand to 1.5 million by Fall ‘09 A more substantial increase internationally Metrics to follow
SF 2008 Priorities Reliability & Scalability Usability & Accessibility Project Planning & Roadmap Collaboration & Portfolio use cases Lower Barriers to Contribution
Converged Campus Infrastructure Librar y Finan ce Stude nt Resea rch Teach ing
database Sakai Converged Technology Research Data Sources Publishing Activities Library Assets Course Management Collaboration Sites database
Sakai Converged Technology Research Data Sources Institutional Content Repository Publishing Activities Library Assets Course Management Collaboration Sites
Benefits Content can be available to multiple systems User satisfaction! Faculty, especially, don’t want to learn multiple systems Centralized storage Less expensive and more reliable Long term data preservation options Applications benefit from enhanced functionality Example: Version control
Sakai Support for JCR JCR: Java Content Repositories A set of standards for content repositories Current standard is JSR-170 Sakai 2.5 has JSR 170 Support (off by default) Content can be stored in any JSR 170 data store Jackrabbit is incorporated into Sakai 2.5
Simplifying Sakai Development IMS Tool Interoperability Web services connection between LMS and external application Allows app to appear seamlessly in LMS One promising path at Cambridge University: Java-based services providing JSON data Interfaces rendered completely in AJAX No java presentation technologies involved