Revision of Settings in ILIAS Test

1 Initial Problem

The settings in the Settings Tabs of the ILIAS Test Object are not up to date anymore (last big revision was in 2015) and a lot has changed since then.

This means that some settings should be removed when no longer or hardly in use, should be restructured according to interdependencies, logic etc.

They should be re-labelled and also phrased in a gender-neutral way:
we want the complex and enormous scope of the Test Object and its settings to be as easy and clear as they can possibly be at the moment.
Of course this has to be consistent with other settings in ILIAS.

The Setting-Tabs-Cleaners-Group has started working on this together with the maintainer and suggests the following.

2 Conceptual Summary

2.1 Create new test

2.2 Settings: General

2.3 Settings: Mark Schema

2.4 Settings: Scoring and Results

• Remove 'Multiple Choice Questions with Empty Answer'
  This setting is not applicable to new tests and hardly used at all, see Mantis Issue 0032387

• Abandon Setting 'Scored Answers of Participant'
  See FR Abandon Setting Scored Answers on single pages

• Restructuring and re-labelling options to show users their results
  See FR Change Setting to show users their results in ILIAS Test

• Abandon 'Feedback' setting
  Feedback should only be displayed during the execution, not in the result view.
  See FR Abandon Feedback in Test Results

• Abandon option 'Item Analysis Export for Pure Single Choice Tests'
  Setting has become superfluous.
  See FR Abandon Item Analysis Export for Pure Single Choice Tests

3 User Interface Modifications

3.1 List of Affected Views

• Settings --> General
• Settings --> Scoring and Results

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

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Grotz, Kendra [kgrotz], Strassner, Denis [dstrassner]
• 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.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …
• ILIAS.nrw

9 Discussion

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