Navigation of Item Groups

1 Initial Problem

Users cannot navigate through item groups whose content is presented in the tile view, as they are used to on streaming platforms and the like.

2 Conceptual Summary

It should be possible to navigate through Item Groups whose content is presented in the tile view, as it is commonly done on other platforms. On the one hand, this would make it possible to work in a space-saving manner and, on the other hand, it would offer further design options. 

Item Groups should get "Netflix"-esque "Next" and "Back"-Glyphs like in the allready existing KS Element Lightbox modal.  A user should be able to browse through objects one by one inside an Item Group by using those Glyphs. If there are four or fewer Objects inside an Item Group (depending on the Tile Size), these Glyphs should be unavailable.

3 User Interface Modifications

3.1 List of Affected Views

• Item Group

3.2 User Interface Details

Example: Clicking on the Next Glyph rotates the Objects to the left.

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: {Please add your name.}
• 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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.