Configure Secondary Panel in Courses and Categories

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

The settings for the secondary panel of categories and courses are scattered across different locations. To improve usability, it would be much more convenient to bundle all settings ragarding the secondary panel in one "place".

2 Conceptual Summary

A newly introduced sub-tab "secondary panel" of the setting tab in course- and category-objects will inheritage all "display-options" of the secondary panel (see screenshot). Therefor the additional features "news" and "calender" will migrate to the new sub-tab "secondary panel". Addition to that the potencial new features "local search" and "tutorial support" will expand that list.

3 User Interface Modifications

3.1 List of Affected Views

• Course-Objects-Settings
• Category-Objects-Settings
• Course-Objects-Settings-Secondary Panel
• Category-Objects-Settings-Secondary Panel

3.2 User Interface Details

Course-Objects-Settings-Secondary Panel

Category-Objects-Settings-Secondary Panel

3.3 New User Interface Concepts

All added elements are existing KS components.

3.4 Accessibility Implications

There should not be any new accessibility implications, since only existing views / KS elements are being used.

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Spirou, Ilias [ispirou]
• Maintainer: Killing, Alexander [alex]
• 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.

• …

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}.