Better configuration options for Learning Sequences on the Dashboard

1 Initial Problem

Learning Sequences are container objects such as courses and groups which should always be easily findable for learning sequence administrators and learning sequence members. This is currently the case because learning sequences are simply put on the Dashboard. That means no matter how many learning sequence you have joined, all of them are shown on your Dashboard which increases the loading time of the Dashboard significantly and easily becomes confusing due to too many different objects on the Dashboard.

2 Conceptual Summary

We are currently debating which way is the best to deal with this issue. There are probably a couple of options to deal with this:

1. Make learning sequences better configurable by introducing a sorting option as suggested in: https://docu.ilias.de/goto_docu_wiki_wpage_6411_1357.html
2. Find another place for the learning sequences, e.g. a new sub entry which only lists learning sequences like the sub entry "My Courses and Groups"
3. Find another place for the learning sequences, e.g. a new sub entry which only lists learning sequences like the sub entry "My Courses and Groups" AND make them configurable on the Dashboard the same way "Favorites" and "My Courses and Groups" are configurable on the Dashboard
4. ...?

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

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

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