xAPI: Support of multiple Assignable Units

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ.

1 Initial Problem

Until now ILIAS supports cmi5 with only one Assignable Unit. However, multiple Assignable Units are rare.

2 Conceptual Summary

In addition to xAPI there is an official specification regarding packaging, launching and communication with xAPI-based content launched from LMS. The new spec is called cmi5 Specification Profile for xAPI (short: cmi5). Basic information is on the main page of the project while the detailed spec is in the github repository.

The goal of the implementation is to completely support this fundamental profile.

This includes support for multiple resources (analogous to multi-SCO in SCORM) with variable learning progress settings.

{Please add a brief summary on how you would like the problem to be solved.}

3 User Interface Modifications

3.1 List of Affected Views

{Please list 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.}

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: Wischniak, Stanislav [wischniak], Kohnle, Uwe [ukohnle]
• Maintainer: Kohnle, Uwe [ukohnle]
• Implementation of the feature is done by: Kohnle, Uwe [ukohnle]

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