Book Image

Sakai CLE Courseware Management: The Official Guide

Book Image

Sakai CLE Courseware Management: The Official Guide

Overview of this book

Sakai is a Collaboration and Learning environment that provides the means to manage users, courses, instructors, and facilities, as well as a spectrum of tools including assessment, grading, and messaging. Sakai is loaded with many handy features and tools, which make it uniquely the Learning system of the present as well as the future.This book is the officially endorsed Sakai guide and is an update to the previous book, Sakai Courseware Management: The Official Guide. From setting up and running Sakai for the first time to creatively using its tools and features, this book delivers everything you need to know.Written by Alan Berg, a Sakai fellow and former Quality Assurance Director of the Sakai Foundation and Ian Dolphin the Executive Director of the Sakai Foundation with significant contributions from the Sakai community, Sakai CLE Courseware Management: The Official Guide is a comprehensive study of how Sakai CLE should be used, managed, and maintained, with real world examples and practical explanations.The book opens with an overview of Sakai, its history and how to set up a demonstration version. Next, the underlying structures and tools are described. In using Sakai for Teaching and Collaboration, there is a detailed discussion of how to structure online courses for teaching and collaboration between groups of students, from creating course sites to understanding their use in different organizations around the world.
Table of Contents (27 chapters)
Sakai CLE Courseware Management
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Terminology
Index

Sakai at UvA


There are a number of practical differences between community source and closed source at UvA. You should consider these as strong selling points for your own management. These include:

  • More influence: There is great opportunity for future collaboration between different organizations within the community, whereas with commercial software, you have an asymmetrical relationship where you have very little influence on the product's roadmap.

  • Empowerment: Traditionally, management at UvA arranged the responsibility for the IC along three tiers: 1, hardware and software; 2, at the applications level; and 3, defining the functionality. The sources for these three tiers are the IC, supplier, and the user. This shows the checks and balances the three-tier division is building into the traditional management style. Hardware maintenance and software distribution are available in-house, while the software suppliers are accountable for the applications. The users will make a complaint...