The document discusses enterprise integration options in Sakai 2.4, including using providers or bulk loading to populate users, groups, and courses from an external system. It focuses on the new CourseManagementService, which models institutional structures and replaces the legacy CourseManagementProvider. It provides details on implementing the UserDirectoryProvider, GroupProvider, SectionFieldManager, and a CourseManagementService to integrate Sakai with an external user directory, groups, courses and sections.
The document discusses Sakai, an open source course management system started in 2004 by 5 universities. It was created to be more efficient than each university building their own system, while maintaining control. Sakai is defined as having tools for course management, research/collaboration, a library component, and portfolios. It has a large community of over 200 production deployments and is developed through an open governance model and Apache-style licensing. The Sakai Foundation coordinates development and promotes open source and open standards in education.
- Yale chose the open source Sakai software to replace its aging homegrown course management system and create a next-generation collaborative learning environment (CLE).
- Yale deployed Sakai in phases, starting with a small pilot and gradually expanding usage. By 2006, over 60% of courses were using Sakai and it became the main CLE.
- Yale customized Sakai to integrate with other campus systems and resources. Faculty support was a top priority during the multi-year deployment process.
The document discusses existing models for personal learning environments (PLEs) and identifies common features and patterns among various systems that could comprise a PLE. It analyzes tools for activities like email, chat, calendaring, news aggregation, blogging, and social software. The patterns are organized into categories and can be used to design PLE applications and services. Key recurring services identified include activity management, workflow, syndication/posting, rating/annotation, and personal profiles.
The MIT Course Management System is called Stellar, which was originally developed to provide online support for existing MIT classes. In 2004, MIT became a founding partner of the Sakai project and later integrated Stellar with Sakai tools. This allows MIT classes on Stellar to take advantage of the many tools developed for Sakai. The integration was achieved by creating a "LaunchPortal" that maintains the Sakai user session and forwards requests to the appropriate Sakai tools while preserving the user experience. User and group integration was implemented, though authorization remains a challenge requiring custom extensions.
The document compares different display technologies that can be used in Sakai and provides recommendations. Java Server Faces (JSF) is currently most used but has many weaknesses. Java Server Pages (JSP) are okay for small projects but have poor separation of code and UI. Velocity is discouraged. Plain Java servlets are not recommended. Reasonable Server Faces (RSF) is a Spring-based framework that provides clean separation of code and UI and is recommended for new Sakai applications.
Sakai is an open source learning management system that was formed in January 2008 by merging the Oncourse and Sakai projects. It discusses Sakai's architecture including its use of Spring, Tomcat, and Java classloaders. It also outlines Sakai's services and components and how new components can be added. The document provides information on getting involved in the Sakai community through development, QA, or requirements work.
The document summarizes the Sakai project, an open source collaboration between several universities to develop a collaborative learning environment (CLE). Key points:
- Sakai is a joint project between University of Michigan, Indiana University, MIT, Stanford, OKI, and uPortal to integrate their educational software into a pre-integrated collection of open source tools.
- The project aims to create a full-featured CLE to replace existing systems, with a framework for new portable tools.
- An initial release (Sakai 1.0) was made available in October 2004, with further development and adoption at the core universities through 2005.
SCORM is a reference model that aims to foster reusable e-learning content. It describes guidelines and specifications for computer-based and web-based learning based on the work of several standards bodies. SCORM seeks to make content sharable, accessible, durable, reusable, and interoperable across different learning management systems and platforms. It focuses on the interface between learning content and LMS environments to allow for interoperability while giving LMS vendors flexibility.
This document provides an overview of the SCORM 2004 3rd Edition Sequencing and Navigation specification, which defines how content is sequenced and navigated within a learning management system. The document covers key concepts like activity trees, sequencing control modes, and status tracking. It is intended to help instructional designers and developers understand and apply the SCORM SN model.
This document provides an overview of the SCORM Content Aggregation Model (CAM) and describes its components and relationships. The CAM defines how content is organized, packaged and described using metadata. It includes the SCORM content model which defines components like assets, SCOs and activities. It also describes content packaging which involves organizing content into packages with a manifest file. The manifest describes the content using metadata based on the LOM standard. The CAM allows content to be shared and used across different LMSs using interoperable specifications.
The SCORM 2004 3rd Edition includes several changes to the SCORM Run-Time Environment that may impact conformance for content packages and learning management systems. Key changes include general updates to improve consistency, updates to the Application Programming Interface to address issues, and changes to the Run-Time Environment data model. Substantive changes were made to the sequencing and navigation aspects.
The document discusses the structure of web applications in Sakai, including:
1) Sakai uses a 3-tier architecture with presentation, business logic, and data access layers. Each tier should be independent and not expose dependencies.
2) Sakai applications are split across shared, components, and webapp deployment areas which map to but do not strictly define the tiers.
3) The standard file structure for a Sakai application includes api, logic, model, public, impl, tests, and tool directories. Packages generally begin with org.sakaiproject and are organized by feature.
Sakai is an open source learning management system that was formed in January 2008 from the merger of the Sakai and Oncourse projects. It discusses the history and development of Sakai and Oncourse. Key components of Sakai include its use of Spring for dependency injection, Tomcat as the application server, and services/tools that are implemented. Contact information and ways to get involved in the Sakai community are also provided.
Eeveloping Interactive Logbook A Personal Learning Environmentjiali zhang
?
The document describes the development of an Interactive Logbook (IL) which is a personal learning environment designed to address limitations of traditional virtual learning environments. The IL allows students to manage learning activities from both formal educational settings and informal settings. It provides tools for note-taking, knowledge sharing, learning management and personal development planning that can be accessed on both desktop and mobile devices. The IL was developed according to specific criteria including supporting lifelong learning, interoperability with other tools, and being owned by the student. It provides an integrated interface for accessing documents, email, web content and allows logging of learning activities.
This document describes the SCORM 2004 3rd Edition Run-Time Environment (RTE) Version 1.0. It provides an overview of the SCORM RTE and covers managing the runtime environment, the application programming interface (API), and the SCORM RTE data model. The API allows communication between content and an LMS during runtime. The data model defines elements for storing learner progress and results.
This document provides a quick reference and tutorial for using Vensim PLE. It describes the main toolbar buttons, sketch tools, analysis tools, status bar buttons, and highlights some useful menu options and hints. The document contains information on creating and editing variables, equations, arrows, boxes, comments and more within the Vensim modeling environment.
Form Learning Over E Learning To My Learningjiali zhang
?
The document discusses the transition from traditional learning to e-learning and personalized learning (MyLearning). It argues that universities need to support lifelong learning by providing open and flexible learning systems that allow individual learning pathways. It describes how e-learning expanded opportunities for learning anywhere and anytime through virtual learning environments. However, e-learning is now being challenged by personal learning environments and open educational resources that give more control to individual learners. The concept of MyLearning represents a shift to learner-centered models where individuals can manage their own learning across institutions.
1) A personal learning environment (PLE) describes the tools, communities, and services that make up an individual's educational platform for directing their own learning goals. It contrasts with a learning management system in being learner-centric rather than course-centric.
2) Universities like the University of Bolton have developed platforms like PLEX to provide students tools to access networks of people and resources. Students at other universities use blogs and publishing platforms to present work and collaborate.
3) On campuses that support PLEs, instructors provide a framework and links to resources for students to add their own networks and collections to draw from external resources and get feedback to expand their learning.
Sakai is an open source learning management system that was formed in January 2008 from the merger of the Sakai and Oncourse projects. It discusses the history and development of Sakai and Oncourse. Key components of Sakai include its use of Spring for dependency injection, Tomcat as the application server, and services/components that provide core functionality through APIs. The document provides an overview of how Sakai is structured and implemented.
Sakai tools are software units that generate user interfaces, usually in HTML. They are used by Sakai's navigation systems and can also act as helpers for other tools. Tools are registered automatically when their web application starts up, allowing Sakai to invoke them behind the scenes. Tools have access to session and configuration information and follow Sakai's URL standards. Helper tools handle common interface tasks for other tools.
The MIT Course Management System is called Stellar, which was originally developed to provide online support for existing MIT classes. In 2004, MIT became a founding partner of the Sakai project and later integrated Stellar with Sakai tools. This allows MIT classes on Stellar to take advantage of the many tools developed for Sakai. A LaunchPortal was created to maintain Sakai user sessions and forward requests to the appropriate Sakai tools while preserving the look and feel of the Stellar interface. User and group integration was implemented, though authorization remains a challenge requiring custom extensions. Further work is needed to fully support all Sakai tools within Stellar.
The document discusses collaboration tools developed at the University of Michigan, including the CHEF and Sakai projects. It provides an overview of the CHEF technology, features, and implementations. It then outlines the formation of the Sakai organization, which involved several universities working together on their course management systems using a shared codebase. The goal was to develop portable tools and services through an open source and standards-based collaboration between the participating universities and projects.
The document summarizes a meeting between representatives from Sakai Foundation and Beijing University of Posts & Telecommunications (BUPT) to discuss localization and use of the Sakai learning management system in China. It outlines the agenda which included introductions, presentations on the current and future of Sakai, and how BUPT is using Sakai. It also discusses BUPT's similar education technology products and possibilities for cooperation between BUPT and Sakai.
The document compares different display technologies that can be used in Sakai and provides recommendations. Java Server Faces (JSF) is currently most used but has many weaknesses. Java Server Pages (JSP) are okay for small projects but have poor separation of code and UI. Velocity is discouraged. Plain Java servlets are not recommended. Reasonable Server Faces (RSF) is a Spring-based framework that provides clean separation of code and UI and is recommended for new Sakai applications.
Sakai is an open source learning management system that was formed in January 2008 by merging the Oncourse and Sakai projects. It discusses Sakai's architecture including its use of Spring, Tomcat, and Java classloaders. It also outlines Sakai's services and components and how new components can be added. The document provides information on getting involved in the Sakai community through development, QA, or requirements work.
The document summarizes the Sakai project, an open source collaboration between several universities to develop a collaborative learning environment (CLE). Key points:
- Sakai is a joint project between University of Michigan, Indiana University, MIT, Stanford, OKI, and uPortal to integrate their educational software into a pre-integrated collection of open source tools.
- The project aims to create a full-featured CLE to replace existing systems, with a framework for new portable tools.
- An initial release (Sakai 1.0) was made available in October 2004, with further development and adoption at the core universities through 2005.
SCORM is a reference model that aims to foster reusable e-learning content. It describes guidelines and specifications for computer-based and web-based learning based on the work of several standards bodies. SCORM seeks to make content sharable, accessible, durable, reusable, and interoperable across different learning management systems and platforms. It focuses on the interface between learning content and LMS environments to allow for interoperability while giving LMS vendors flexibility.
This document provides an overview of the SCORM 2004 3rd Edition Sequencing and Navigation specification, which defines how content is sequenced and navigated within a learning management system. The document covers key concepts like activity trees, sequencing control modes, and status tracking. It is intended to help instructional designers and developers understand and apply the SCORM SN model.
This document provides an overview of the SCORM Content Aggregation Model (CAM) and describes its components and relationships. The CAM defines how content is organized, packaged and described using metadata. It includes the SCORM content model which defines components like assets, SCOs and activities. It also describes content packaging which involves organizing content into packages with a manifest file. The manifest describes the content using metadata based on the LOM standard. The CAM allows content to be shared and used across different LMSs using interoperable specifications.
The SCORM 2004 3rd Edition includes several changes to the SCORM Run-Time Environment that may impact conformance for content packages and learning management systems. Key changes include general updates to improve consistency, updates to the Application Programming Interface to address issues, and changes to the Run-Time Environment data model. Substantive changes were made to the sequencing and navigation aspects.
The document discusses the structure of web applications in Sakai, including:
1) Sakai uses a 3-tier architecture with presentation, business logic, and data access layers. Each tier should be independent and not expose dependencies.
2) Sakai applications are split across shared, components, and webapp deployment areas which map to but do not strictly define the tiers.
3) The standard file structure for a Sakai application includes api, logic, model, public, impl, tests, and tool directories. Packages generally begin with org.sakaiproject and are organized by feature.
Sakai is an open source learning management system that was formed in January 2008 from the merger of the Sakai and Oncourse projects. It discusses the history and development of Sakai and Oncourse. Key components of Sakai include its use of Spring for dependency injection, Tomcat as the application server, and services/tools that are implemented. Contact information and ways to get involved in the Sakai community are also provided.
Eeveloping Interactive Logbook A Personal Learning Environmentjiali zhang
?
The document describes the development of an Interactive Logbook (IL) which is a personal learning environment designed to address limitations of traditional virtual learning environments. The IL allows students to manage learning activities from both formal educational settings and informal settings. It provides tools for note-taking, knowledge sharing, learning management and personal development planning that can be accessed on both desktop and mobile devices. The IL was developed according to specific criteria including supporting lifelong learning, interoperability with other tools, and being owned by the student. It provides an integrated interface for accessing documents, email, web content and allows logging of learning activities.
This document describes the SCORM 2004 3rd Edition Run-Time Environment (RTE) Version 1.0. It provides an overview of the SCORM RTE and covers managing the runtime environment, the application programming interface (API), and the SCORM RTE data model. The API allows communication between content and an LMS during runtime. The data model defines elements for storing learner progress and results.
This document provides a quick reference and tutorial for using Vensim PLE. It describes the main toolbar buttons, sketch tools, analysis tools, status bar buttons, and highlights some useful menu options and hints. The document contains information on creating and editing variables, equations, arrows, boxes, comments and more within the Vensim modeling environment.
Form Learning Over E Learning To My Learningjiali zhang
?
The document discusses the transition from traditional learning to e-learning and personalized learning (MyLearning). It argues that universities need to support lifelong learning by providing open and flexible learning systems that allow individual learning pathways. It describes how e-learning expanded opportunities for learning anywhere and anytime through virtual learning environments. However, e-learning is now being challenged by personal learning environments and open educational resources that give more control to individual learners. The concept of MyLearning represents a shift to learner-centered models where individuals can manage their own learning across institutions.
1) A personal learning environment (PLE) describes the tools, communities, and services that make up an individual's educational platform for directing their own learning goals. It contrasts with a learning management system in being learner-centric rather than course-centric.
2) Universities like the University of Bolton have developed platforms like PLEX to provide students tools to access networks of people and resources. Students at other universities use blogs and publishing platforms to present work and collaborate.
3) On campuses that support PLEs, instructors provide a framework and links to resources for students to add their own networks and collections to draw from external resources and get feedback to expand their learning.
Sakai is an open source learning management system that was formed in January 2008 from the merger of the Sakai and Oncourse projects. It discusses the history and development of Sakai and Oncourse. Key components of Sakai include its use of Spring for dependency injection, Tomcat as the application server, and services/components that provide core functionality through APIs. The document provides an overview of how Sakai is structured and implemented.
Sakai tools are software units that generate user interfaces, usually in HTML. They are used by Sakai's navigation systems and can also act as helpers for other tools. Tools are registered automatically when their web application starts up, allowing Sakai to invoke them behind the scenes. Tools have access to session and configuration information and follow Sakai's URL standards. Helper tools handle common interface tasks for other tools.
The MIT Course Management System is called Stellar, which was originally developed to provide online support for existing MIT classes. In 2004, MIT became a founding partner of the Sakai project and later integrated Stellar with Sakai tools. This allows MIT classes on Stellar to take advantage of the many tools developed for Sakai. A LaunchPortal was created to maintain Sakai user sessions and forward requests to the appropriate Sakai tools while preserving the look and feel of the Stellar interface. User and group integration was implemented, though authorization remains a challenge requiring custom extensions. Further work is needed to fully support all Sakai tools within Stellar.
The document discusses collaboration tools developed at the University of Michigan, including the CHEF and Sakai projects. It provides an overview of the CHEF technology, features, and implementations. It then outlines the formation of the Sakai organization, which involved several universities working together on their course management systems using a shared codebase. The goal was to develop portable tools and services through an open source and standards-based collaboration between the participating universities and projects.
The document summarizes a meeting between representatives from Sakai Foundation and Beijing University of Posts & Telecommunications (BUPT) to discuss localization and use of the Sakai learning management system in China. It outlines the agenda which included introductions, presentations on the current and future of Sakai, and how BUPT is using Sakai. It also discusses BUPT's similar education technology products and possibilities for cooperation between BUPT and Sakai.
1. The document discusses redesigning and integrating Sakai tools at Beijing University of Posts and Telecommunications' online education school.
2. It outlines three design principles: offering time and task management, using online courses as the basic material, and analyzing learner data to provide customized support.
3. Melete will be modified based on the first two principles and a new tool will be developed for learner data analysis and support.
This document proposes a next generation of the Sakai collaboration and learning environment called Sakai 3. It outlines ambitions to create a more flexible system that provides greater user control and incorporates modern technologies like social networking. The proposal recognizes limitations in the current Sakai platform and seeks to address these by developing a new architectural core, improved user experience, and enhanced capabilities for social networking, content creation and organization.
This document summarizes new features of the Sakai JSR-168 portlet including a gallery view, tree view, and proxy portlets. It discusses using web services to retrieve Sakai site data and login information. Authentication and authorization between the portal and Sakai is identified as an area needing further work. The document outlines plans to improve placement of tools using roles and to make the portlet preferences more configurable.
39. 第四个问题: Sakai 与 SOA Sakai 目前有支持 Web Service 的模块, Sakai 的内核也是基于服务的方式构建。 但是针对 Sakai 系统级和工具级与 SOA ,特别是基于 SOA 的互操作方面缺乏强有力的内核和工具支持 在 Sakai 社区中,有关 Sakai 与 SOA 的讨论也甚少,这方面资料也不多。 4.1 技术层面(续)
40. 第五个问题: Sakai 系统的未来演化 从目前来看, Sakai 系统已经针对 E-Learning 开发并配置了大量工具,拥有丰富的在线教、学功能。 从长远的角度来看,我们考虑是否可以基于 Sakai 来研发出一种专门针对 E-Learning 的 WEB OS ,将其发展成为一种普适的、功能强大的在线学习平台。 如果可以如此定位, Sakai 就有可能成为 E-Learning 领域的 Linux ,那么除了要关注应用服务器的问题,我们还要重新回头来看 Sakai 内核是否能够胜任此项重用,我们还需要哪些基本的服务和核心的工具,以及如何做。 4.1 技术层面(续)