„Error Text“ - Restrict Maximum Markable Options

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

1 Initial Problem

With the current implementation of the error text question a configuration using negative points is required, to avoid particpants from beeing scored with maximum points by simply marking all available options ( a.k.a „Error Data“ or „Errors“). For getting rid of the obligation to use negative points the following feature is proposed.

This FR is based on the already Implemented Restriction for Multiple Choice question type (see: Source)

2 Conceptual Summary

An optional restriction for the maximum amount of markable options is required. This restriction has to affect while presenting the question in the test object as well as in the learning module. The question previews has to be considered too.

A numeric setting "Answering Limitation" has to be added to the configuration screen of the „error text“ question. Valid values for this field are the integers between 1 and the amount of available options. To keep the currently valid behaviour available this field can simply be left empty, no restriction will affect the participant when marking answer options in this case. QTI Export and Import are to be completed with this new setting.

When a restriction of markable options is active a corresponding hint is shown to the participant while answering the question (e.g. "Please Mark 3 Answers"). The marking of more than the allowed amount of options is avoided by using javascript. When the maximum amount of options is selected, no futher marking (> allowed options) can be made. When one of the marked options gets deselected, the marking of „errors“ get enabled again. Because of this mechanism can be bypassed , there should be a serverside validation of the amount of marked answer options. In case of an invalid answer, the answer is not stored and the question is shown to the participant again involving a corresponding failure message. The submitted and invalid marking is reset in full.

Within the correction mode the new setting won't be adjustable, since in-or decreasing this value does not make sense in any kind.

Existing questions will not be migrated in any kind, the new setting will just be left empty, so the cuurently known behaviour won't be changed for this questions.

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: Rachid Rabah
• Maintainer: Studer, Martin [mstuder]
• Implementation of the feature is done by: 

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