Feature Wiki
Tabs
Randomly Seeded Shuffling of Answer Options for Formative Assessments
Page Overview
[Hide]1 Initial Problem
A fully dynamic shuffling was once the regular behavior. It did shuffle with a fully random seed each time any shuffling happened. This old behavior was not sufficient for exam scenarios. Therefore the so called seeded shuffling was introduced as a bugfix accepted by the JourFixe. But for formative assessment scenarios the former behavior could bring a didactical benefit.
2 Conceptual Summary
Another setting for the test is to be introduced: Answer Option Shuffling Behaviour
This setting comes as a radio group with the following options:
- Shuffle Only Once per User and Question
- Shuffle on each Presentation of the Question
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
Strassner, Denis [dstrassner]: 2022-02-10: The Taskforce EA Bugfixing talked about this FR, and we are sure that, it is outdated. We propose another solution for open Cloze Gap Question Mantis Reports. - (Seed with Index of Gap / Seed + x).
6 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
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}.
Last edited: 10. Feb 2022, 09:56, Strassner, Denis [dstrassner]