Chapter 2. The OLAT LMS implementation concepts

Table of Contents

2.1. Interaction design
2.1.1. Overview
2.1.2. Principle
2.1.3. Guidelines for interactive elements
2.2. Navigation and Layout
2.2.1. Layout control
2.2.2. Top navigation sites and dynamic tabs
2.2.3. Menu-content-tool layout
2.2.4. Content menu
2.2.5. Content area
2.2.6. Toolbox actions
2.2.7. Direct jumps and state activation
2.2.8. Context sensitive and comprehensive help
2.2.9. GUI preferences
2.2.10. HTML and CSS
2.2.11. Customizing the layout
2.3. User management
2.3.1. System roles and rights
2.3.2. Authentication providers
2.4. Resources and repository
2.4.1. TODO TODO TODO: add new types: Types and repositoryhandlers
2.4.2. Workflows
2.5. Resource Course
2.5.1. Course structure and course building blocks
2.5.2. Course run, User course session, Course environment
2.5.3. Editor - publish - run
2.5.4. Configuration
2.5.5. Visibility and accessability rules
2.5.6. Assessment and scoring
2.5.7. Groups - areas - roles - rights
2.5.8. Activity logging and tracking
2.6. Resource IMS QTI
2.6.1. Editor
2.6.2. Runtime
2.6.3. Results
2.6.4. Disabling of collaboration tools
2.7. Groups
2.7.1. System roles versus resource owners versus business groups
2.7.2. Generic business group and Grouptypes
2.7.3. Groupcontext
2.7.4. Areas
2.7.5. Rights
2.7.6. Group type based localization
2.7.7. Collaboration tools
2.7.8. IM roster synchronization
2.8. Shibboleth
2.8.1. Registration
2.8.2. Attributes
2.8.3. Home Organisation Preselection
2.9. Home
2.9.1. Settings
2.9.2. Portal and portlets
2.9.3. Personal folder
2.9.4. User visiting card
2.10. Other elements
2.10.1. SCORM 1.2
2.10.2. Folders and WebDAV

Summary

In this chapter you will learn which interaction design concepts have been implemented in OLAT and how the system architecture looks like on the business level. It shall provide guidance to developers of the open source community to ensure a consistent user interface. Code contributions complying with these concepts are more likely to be accepted for official releases. If you are interrested in the technical architecture and the development framework that is used to implement this abstract system architecture, please refer to the chapter Chapter 3, OLAT development framework overview