Feature Wiki

Information about planned and released features

Tabs

Interface to get assessment related user data

Page Overview

[Hide]

1 Initial Problem

At the time being, adaptivity in ILIAS is restricted to courses with presentation type 'Learning Objectives-Driven Course'. Users get a recommendation for learning and training material when they do not pass the test related to the defined learning objective. If we use such a course to recap mathematical skills - for example 'fractions' - we can check if a user has the basic knowhow to solve fractions. We assume this knowhow when the user passes the related test for this learning objective with a defined threshold (e.g. 50% of all points). But in this case we cannot provide material in case of a specific lack of knowhow in adding or in multiplying fractions - as long as we do not define these skills again as learning objectives (which would blast the course). Therefore, a more specific way is needed to analyse skills and to recommend learning and training material for every single user.

2 Conceptual Summary

We would like to analyse a user's skills in a first version outside of ILIAS. Once we have elaborated a reliable approach we would suggest such a feature for trunk. In the meantime we only need to get the necessary information about a user's performance in a test from ILIAS. A dedicated interface for this might be a feasible solution for this. Such an interface should provide information such as:
  • User ID
  • Question ID
  • ID of related LOK
  • Related skills / competencies
  • Time stamp
  • Given solution
  • …

3 User Interface Modifications

3.1 List of Affected Views

None

3.2 User Interface Details

No user interface elements shall be modified, added or removed. We do not see the need to configure this interface in the UI of ILIAS.

3.3 New User Interface Concepts

None

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: Gerhard Götz, DHBW Mosbach / optes TP1
  • 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.}

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

Last edited: 31. Mar 2017, 17:43, Undisclosed