(De)Activation of Chapters in ILIAS-LM

1 Initial Problem

Authors of ILIAS learning-modules are allowed to (De-)Activate each page of a learning-module.

There are three reasons, why we should allow this also for chapters and sub-chapters:

1. It saves clicks, when you can (de-)activate a whole (sub)chapter
2. Didactical approach: Teachers can activate some solution-areas on the chapter-level. 
3. Under-construction area: This new feature allows teachers to set a Learning-Module online, although some chapters are still under construction.

2 Conceptual Summary

In the ILIAS learning module, in the content (Editing-view), users with edit-rights are allowed to activate or deactivate chapters and/or sub-chapters.

View 1: chapters

• In this view, the button "(De-)Activate" occurs
• Users can now activate or deactive one ore multiple chapters. They choose the chapter(s) and click the button.
• ILIAS immediately change the behavior of the chapter: The whole chapter (with all subchapters and pages) is activated or deactivated.

• In this view, the button "(De-)Activate" already exists
• ILIAS should now allow, that users can (de-)activate one or more (sub)-chapter, or subchapters and pages, in one go.

• When a user deactivates chapters AND subchapters, and then he activates the main-chapter: then the sub-chapters and pages are still deactivated.
• In the editor view, the icon indicates whether a chapter or subchapter is visible or not (analogous to the deactivated page).

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

View 1

View 2

3.3 New User Interface Concepts

No new UI concepts

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

No personal data stored.

6 Security Implications

No security implications.

7 Contact

• Author of the Request: Lauener, Hansjörg [lauener]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Universität Bern

9 Discussion

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.