xAPI: Configurator for determining Learning Progress

1 Initial Problem

In particular, when using xAPI without further defining specifications/profiles such as CMI-5, the determination of the learning progress can occassionally be difficult.
xAPI itself does not have any mapping preferences on learning progress, but instead gives all the flexibility to content developers. There are already a lot a of scenarios and verbs , that could be used, such as "played", "mastered", "passed", "completed" and so on. With extended requirements there might be also further need to set ILIAS progress based on score or time used. So the overall idea is to give administrators a tool to have a full control on how ILIAS would be interpreting and mapping such data.

2 Conceptual Summary

To give administrators all necessary control we want to take advantage of the good structured statements data design and create some "mapping rules" to evaluate the data. For example, a rule for the ILIAS LP state "Completed" could be as simple as:

verb.id = passed


or as complicated as:

result.success = true AND result.score.scaled >= 0.8 AND result.duration <= PT2H0M0S

(which means learners score needs to be more then 80% and the time used should be below 2 hours).

Similar rules could be created for the state "Failed" (e.g.: verb.id = "failed").

The ILIAS LP states "Not attempted" and "In progress" would not require any custom rules, in our opinion.
The default rule for "Not attempted" would be: "not a single statement for this learner".
The default rule for "In progress" would be:"at least one statement for this learner, but no other custom rules apply".

3 User Interface Modifications

3.1 List of Affected Views

Here are some mockups on the basic idea.

3.2 User Interface Details

3.3 New User Interface Concepts

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: Kohnle, Uwe [ukohnle], Wischniak, Stanislav [wischniak]
• 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}.