Make detail level of My Courses and Groups on Dashboard configurable

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 Dashboard allows to show both "My Courses and Groups" and "Favorites". We do currently experience the problem that the option "My Courses and Groups" produces very long loading times for the dashboard if you are member of many courses and/or groups. The reason for these long loading times is the plurality of information you get for every course and group such as "Registration Status", "Availability", "Status", etc.. This produces a lot of queries and should be configurable by the administrator.

2 Conceptual Summary

We would like to introduce some checkboxes in the "My Courses and Groups" menu (Administration -> Dashboard -> Section 'My Courses and Groups') which allow to show only part of the information you currently get on the Dashboard. Then you can e.g. activate the information about "Status", "Availability", "Registration" in this menu for all users on the platform or no one.

3 User Interface Modifications

3.1 List of Affected Views

• Dashboard
• Administration->Dashboard->Section 'My Courses and Groups'

3.2 User Interface Details

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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: Falkenstein, Rob [rob]
• 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.

• …

9 Discussion

Tödt, Alexandra [atoedt] 2022-05-06: A considerable amount of effort was spent to declutter the Dashboard and get rid of options. 
Please think about improving the performance of the Dashboard instead of configuring the pain away. 

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