Sakai (software)

From Wikipedia, the free encyclopedia
  (Redirected from Sakai Project)
Jump to: navigation, search
Sakai
Stable release
11.4 / June 2, 2017 (2017-06-02) [1]
Written in Java
Operating system Cross-platform
Available in 19 languages (ar, ca, de, en, es, eu, fr, it, ja, ko, mn, nl, pl, pt, ru, sv, tr, vi, zh),[2][3]
Type Course Management System
License Educational Community License
Website www.sakaiproject.org

Sakai is a free, community source, educational software platform designed to support teaching, research and collaboration. Systems of this type are also known as Course Management Systems (CMS), Learning Management Systems (LMS), or Virtual Learning Environments (VLE). Sakai is developed by a community of academic institutions, commercial organizations and individuals. It is distributed under the Educational Community License (a type of open source license).

Version 1.0 was released in March 2005.

Sakai is used by hundreds of institutions, mainly in the US, but also in Europe, Asia, Africa and Australia.[4] [5] Sakai was designed to be scalable, reliable, interoperable and extensible. Its largest installations handle over 100,000 users.[6] [7]

Organization[edit]

Sakai is developed as open source software as a community effort, stewarded by the Apereo Foundation, a member-based, non-profit corporation. The Foundation fosters use and development of Sakai in the same open, community-based fashion in which it was created. It encourages community building between individuals, academic institutions, non-profits and commercial organizations and provides its members with an institutional framework for their projects. It works to promote the wider adoption of community-source and open standards approaches to software solutions within the education and research communities. It organizes the yearly Open Apereo Conference.[8] Additional, regional conferences have taken place in China, Japan, Australia, Europe and South Africa, and there is an annual Sakai Virtual Conference.[9] Members include universities, colleges, other institutions and commercial affiliates that provide support. While members take care of most of the development and support in practice, joining the Foundation is not required to use the software or participate in the community.

History[edit]

The development of Sakai was originally funded by a grant from the Mellon Foundation as the Sakai Project. The early versions were based on existing tools created by the founding institutions, with the largest piece coming from the University of Michigan's CHEF course management system. Sakai is a play on the word chef and refers to Iron Chef Hiroyuki Sakai.[10]

The original institutions started meeting in February 2004. Each institution had built a custom course management system:

Sakai 1.0 was released in 2005, and it was adopted by all participating universities. For instance, Indiana University moved all of its legacy systems to Sakai.

With the Sakai Project concluding, the Sakai Foundation was set up to oversee the continued work on Sakai. Sakai's chief architect, Dr. Charles Severance, was its first Executive Director.

Several large US universities joined, as well as universities, colleges, other institutions and commercial affiliates on all continents.

One of the partners, the University of Cambridge, started work on a more student-centric system in an attempt to provide a better fit with their own educational model. Several partners joined this effort, seeing this as an opportunity to do away with some of Sakai's known limitations; for a while, the effort was named Sakai 3,[11] but it was far from being a feature complete replacement and it was built from scratch on different technology.

This seriously hampered progress on the existing Sakai. After about two years, it turned out the new software would never replace the existing Sakai, and it was renamed to Sakai OAE (today: Apereo OAE), while the existing Sakai was renamed to Sakai CLE.

After this, Sakai CLE development slowly picked up speed again. A major advance was a WYSIWYG content editing tool, the Lessons tool, contributed by Rutgers University in version 2.9.3.

In 2012, University of Michigan and Indiana University, two of Sakai's founders, left the Sakai foundation. In the following 2 years many of the existing users also retired Sakai and moved to other software. During this period new users were rare. Meanwhile, Sakai development continued to pick up speed.

In December 2012, the Sakai Foundation merged with Jasig to form the Apereo Foundation, which took over stewardship of Sakai development.[12]

Sakai collaboration and learning environment - software features[edit]

The Sakai software includes many of the features common to course management systems, including document distribution, a gradebook, discussion, live chat, assignment uploads, and online testing.

In addition to the course management features, Sakai is intended as a collaborative tool for research and group projects. To support this function, Sakai includes the ability to change the settings of all the tools based on roles, changing what the system permits different users to do with each tool. It also includes a wiki, mailing list distribution and archiving, and an RSS reader. The core tools can be augmented with tools designed for a particular application of Sakai. Examples might include sites for collaborative projects, teaching and portfolios.

In Sakai, the content and tools used in courses or projects is organized into sites. Typically, a site corresponds to a course or a project. Each site has its own content, tools, users and access rights for users, search tool, usage statistics, etcetera. In principle, everything in Sakai is done per site. This is what allows Sakai to scale to hundreds of thousands of users.

Sakai is extensible in several ways:

  • it is a platform for integrating loosely coupled tools, which provide the actual functionality; in addition to the core tools distributed with Sakai, several important third-party tools are available, and web developers can write their own additional tools in a language of their own choice;
  • third-party tools are available for playing SCORM packages;
  • external web applications can be integrated using LTI

Architecture and technical details[edit]

Sakai is a set of web applications written in Java-based, loosely coupled in a service-oriented architecture. The supported web server is Tomcat; the databases supported for data storage are Oracle and MySQL.

Sakai has a layered architecture:

  • The Sakai kernel provides a common infrastructure and exposes it in the form of web services.
  • All of the sub-applications, known as tools in Sakai, depend on these services for things like user management and site management. Nearly all functionality is implemented in the form of tools.
  • Tools have a business logic implementation part and a user interface part, implemented using various Java technologies.
  • These interfaces are combined by so-called aggregators.

Each layer is extensible: new services, tools, and aggregators are easy to add. Owing to the services, tools and user interfaces can be written in other languages than Java, but this does not happen in practice.

Up to and including Sakai 10, the code base for Sakai and its contributed tools were maintained in publicly accessible Subversion repositories. With Sakai 11, this was changed to Git and GitHub.

Releases[edit]

Sakai is mainly in use at universities. Major releases tend to be in spring or early summer, in order to allow institutions to upgrade before the new academic year, and many of them do.

Branch Original
release date
Version Version
release date
Support Model Release notes
Old version, no longer supported: 1.0.x 19 January 2004 1.0.0 27 October 2004 EOL (Maintained from XX to XX ?) URL
Old version, no longer supported: 1.5.x 4 March 2005 1.5.1 27 May 2005 EOL (Maintained from XX to XX ?) URL
Old version, no longer supported: 2.0.x 15 June 2005 2.0.1 15 August 2005 EOL (Maintained from XX to XX ?) URL
Old version, no longer supported: 2.1.x 30 November 2005 2.1.2 12 April 2006 EOL (Maintained from November 2005 to November 2006 ?) URL
Old version, no longer supported: 2.2.x 19 July 2006 2.2.3 12 February 2007 EOL (Maintained from July 2006 to May 2007 ?) URL
Old version, no longer supported: 2.3.x 3 November 2006 2.3.2 21 May 2007 EOL (Maintained from November 2006 to March 2008 ?) URL
Old version, no longer supported: 2.4.x 21 May 2007 2.4.1 21 September 2007 EOL (Maintained from May 2007 to July 2009) URL
Old version, no longer supported: 2.5.x 20 March 2008 2.5.6 28 January 2010 EOL (Maintained from March 2008 to June 2010) URL
Old version, no longer supported: 2.6.x 22 July 2009 2.6.3 26 August 2010 EOL (Maintained from July 2009 to April 2011) URL
Old version, no longer supported: 2.7.x 11 June 2010 2.7.2 10 September 2011 EOL (Maintained from June 2010 to November 2012) URL
Old version, no longer supported: 2.8.x 18 April 2011 2.8.3 15 February 2013 EOL (Maintained from April 2011 to June 2014) URL
Old version, no longer supported: 2.9.x 9 November 2012 2.9.3 19 August 2013 EOL (Maintained from November 2012 to July 2016) URL
Older version, yet still supported: 10.x 30 June 2014 10.7 19 April 2015 Active (Maintained from June 2014 to ?) URL
Current stable version: 11.x 23 July 2016 11.4 2 June 2017 Active (Maintained from July 2016 to ?) URL
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

See also[edit]

References[edit]

Bibliography[edit]

External links[edit]