Set Recommended Content to Tile View

1 Initial Problem

For the 'Favorites' and 'My Courses and Groups'-panels, the Tile view can be activated in Administration. This option does not exist for the panel 'Recommended Content'.

This feature request is to introduce the tile view for Recommended Content.

Needs to be discussed:

It should be considered how the behavior of the views on the roof board should be handled? 

Should the view be set per panel or should the whole dashboard be changed to tile view, for example.

2 Conceptual Summary

If the Tile View has been enabled in the administration for the 'Recommended Content' panel, the recommended learning content will be displayed as a card.

Individual panels can be activated in the Dashboard Administration. In order to make the administration interface uniform, this option should also be introduced for the 'Recommended Content'.

Needs to be discussed
However, the 'Recommended Content' panel is only displayed if learning content has been assigned to a role. Deactivating the panel is therefore only conditionally necessary.

The 'Recommended Content' panel does not yet know sorting options. If you call the subtab 'Section 'Recommended Content'', you should only be able to adjust the presentation of the objects.

3 User Interface Modifications

3.1 List of Affected Views

• Dashboard
• Administration » Personal Workspace » Dashboard

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: Zenzen, Enrico [ezenzen]
• 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.

• BGHW

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