KS Presentation Table in SCORM Tracking Data By User

1 Initial Problem

The Scorm Tracking Data can contain a large amount of data that is currently accessible via many columns. This can quickly lead to a confusing table, since the table is too small for certain screens and must be scrolled within the table. Columns can be hidden, but then the information is not accessible.

If you want to view additional information for individual users (which is currently hidden in the column), you have to work your way back through the entire table to this user after displaying the column.

The information should be prioritized so that important information is quickly accessible, but further information can also be viewed without great effort.

Problematic Screenshot

2 Conceptual Summary

We aim to use the new Presentation Table and Pagination controls for this view.

3 User Interface Modifications

3.1 List of Affected Views

• Learning Module Scorm > (Settings) > Tracking Data > By User

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

The following UI-Components will be used:

• Presentation Table

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 Contact

• Author of the Request: Seiler, Yvonne [yvseiler], Universität Bern
• Maintainer: Kohnle, Uwe [ukohnle]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

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