Adaptive Learning Paths: Player Redesign

1 Initial Problem

The previous Player of a Learning Sequence was designed for largely linear navigation. Adaptive Learning Paths, however, require more situations: a next object can be blocked, there can be several permitted next objects, a path can lead to a dead end, or navigation can be supported by a map.

The Player must present these situations understandably and guide learners safely through adaptive paths.

2 Conceptual Summary

The Player was extended for Adaptive Mode. It detects different adaptive situations:

For branches, a dedicated selection page is built. It shows the possible next objects as cards with icon or tile image, title, description and start action. This separates object selection from the actual learning object and presents it as a clear intermediate page.

For Dead Ends, there is a dedicated Dead End page with explanatory text and illustration. Blocked situations are explained with an info message.

The Learning Map is available in the Player and supports orientation within the adaptive path. It makes visible where learners are located in the path and which structures exist.

The Learning Map is integrated into the Player as an orientation aid. It shows the learning path structure and supports switching or understanding the current position.

Straight

Upon clicking the "Next" button, the user is taken directly to the next learning content.

Branch

If the Player detects a branch, a selection page is displayed. This page contains a friendly heading, a short explanation and a card display of the selectable objects.

Blocked

If an object is blocked, an information message is displayed. It explains that a condition must be fulfilled before the next object can be started.

Dead End

If the path leads to a dead end, a Dead End page is displayed. This separates the dead-end information from the normal object content and makes it clearer that no suitable continuation is available.

end

The End object of the LSO has a Finish Button which closes the Player and the user gets directed to the Exit Page.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

The Player introduces several adaptive intermediate situations as dedicated displays:

The selection page uses Kitchen Sink cards and buttons. The content of the cards is built from the Learning Sequence objects, including title, description, icon and optional tile image.

3.3 New User Interface Concepts

The Main Menu of the Player includes the Learning Map which is a new concept described in Adaptive Learning Paths: Learning Map.

3.4 Accessibility Implications

Cards need meaningful titles, descriptions and buttons. Tile images must not carry the object information on their own; title and start action must be available textually.

For Dead Ends and blocked objects, it is important that the cause is explained clearly in text. The Learning Map must not convey status information exclusively through color.

4 Additional Information

4.1 Involved Authorities

4.2 Technical Aspects

In Adaptive Mode, the Player uses position and navigation logic. Methods for determining the current position, moving forward/backward, jumping directly and detecting the situation encapsulate adaptive navigation.

Situation detection classifies the current state as end, blocked, deadend, branch or straight. Branch selection and Dead End hints are no longer appended directly to the object content, but rendered through dedicated intermediate pages.

The selection page is created through a reusable builder. It renders a card with object information and start button for each selectable successor. The Dead End page uses dedicated Player texts and an illustration.

4.3 Privacy

The Player processes learner-specific navigation and learning progress data to determine adaptive situations. No new categories of personal data are introduced.

4.4 Security

No special security-relevant changes. Access to objects remains bound to the existing Learning Sequence and ILIAS permission checks.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Auerbach, Jeanine [jeanine.auerbach], Clausen, Keven [keven.clausen]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

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

6.4 Approval

Approved at {date} by {user}.