»or« Taxonomy in Question Pools

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

Within a test, use cases A, B and C should be covered. For each of the use cases, a separate taxonomy node has been created in a question pool from which questions should be picked.

It is currently possible to select taxonomy nodes by means of an "and" link. The result is a mixture of questions from A, B and C, which leads to a mixture of use cases.

If you want to specify that only one of the taxonomy nodes should be selected per learner, is this particular setting at the moment not possible.

2 Conceptual Summary

It should be possible to predefine (by e.g. a checkbox) that only one taxonomy node per learner is to be selected and that no mixing takes place.

After the question amount and the nodes have been defined, ILIAS checks in the background whether the corresponding number of questions is available in all nodes. If its not the case, an error appears.

-> "Please check whether the required number of questions has been stored in the selected nodes".

In step 3, a new checkbox appears that asks whether only one node should be used after a randomised assignment. The checkbox is not set by default.

A common recording of learning progress should still be possible after this setting.

3 User Interface Modifications

3.1 List of Affected Views

• Test Administration View

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: Detemple, Konstanze [kdetemple]
• 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.

• …

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