Dwell Time (Verweildauer) per question

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

It is currently possible to define an individual " working time "/" Bearbeitungsdauer " for each question. However, this function is without any use and has no meaning at all for the test evaluation. Furthermore, this value leads new Ilias users to questions regarding its usefulness and functionality. We would therefore suggest either assigning this value to a statistical analysis or introducing the new value " dwell time "/"Verweildauer". 

2 Conceptual Summary

The tracking of the time is done per participant and question. In the tab "Overview Item Statistic" an average time per question is displayed for the examiner in the format HH:MM:SS. The average value must als be exported for the "Test" and "Question Pool Test". 

If possible, the examiner should also get the raw data as well.  For example : 

Von       | Bis         | Q-ID     |User-ID oder matrikel | Fragen-Titel | Bearbeitet
--------------------------------------------------------------------------------------------------------------
0:00:00 | 0:03:00 | 13510 |rabah                               |MeineFrage1|ja
0:03:00 | 0:08:52 | 87680 |rabah                               |MeineFrage2|nein
0:08:53 | 0:10:00 | 13510 |rabah                               |MeineFrage1|nein

If this is not possible, a saving in the context of this FR  may also be sufficient 

3 User Interface Modifications

3.1 List of Affected Views

The value is to be listed in Test > Statictics > Overview Item Statistic. In order to allow a clear representation, the Average Time should be displayed as : "Ø dwell time"  
The desired value can be added by clicking on "Columns"

3.2 User Interface Details

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: Rabah, Rachid [rabah]
• Maintainer: Heyser, Björn [bheyser]
• 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.

• Universität Bonn

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