Improve Export of Test and Item Statistics

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

Currently, the test and item statics can only be exported individually and across multiple screens. The offered exports are also very technical and do not allow the examiner to make a quick and reliable decision. We therefore suggest an improvement of the export by providing a visually appealing and centralized view for the examiner.

2 Conceptual Summary

This concept is based on the fantastic and valuable work of Fred Neumann. 

The export is offered to the examiner in two file formats (.csv and .xlsx).
The Excel Workbook provides the author with graphically prepared and summarizing statistics. It extends over several pages.  The The first page offers the "Overview" of the test and acts as cover page. The second page holds the "Aggregated Test Results" and the third page shows the "Aggregated Question Results". In order to make it easier for the examiner to understand, a "Key Figure Explenation" can be inserted as the last page.

3 User Interface Modifications

3.1 List of Affected Views

newly to introduced selection point: "Create Test Statistics File"

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: Rabah, Rachid [rabah]
• 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.

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