Show Advanced KnowledgeHide Advanced Knowledge

Manual synchronisation of questions in tests after editing in pool

1 Initial Problem

By now you can synchronize a test with a random set of questions from a questionpool.

If you use a questionpool and test with a fixed set of questions, you dont have this function. That means: if you're editing a question in a questionpool that is used in various tests, you have to open every single test, remove the outdated question and have to add it again. 

2 Conceptual Summary

You edit a question in a pool. After saving you can choose if the changes should be adopted to tests that uses this question, on condition that:

• the tests are set as tests with a fixed set of questions
• there are no data sets in the tests
• you have the permission "edit settings" in the tests

The already existing feature of synchronizing changes from test to pool should be adapted to this new feature (text, button, ...).

This feature should'nt contradict any future ideas on versioning questions.

You have to enable this feature in the administration first (standard: disabled).

3 User Interface Modifications

3.1 List of Affected Views

• question pool » questions » edit question » save (if question is used in tests and user has "edit settings"-permission to them)
• test » questions » edit question » save (if question belongs to a pool and user has "edit settings"-permission to it)
• administration » repository and objects » Test and Assessment

3.2 User Interface Details

After saving changes in a pool question, you'll see the following page: 

Precondition: you have "edit settings"-permission to the tests, where the questions are used.
If there are data sets, the tests will be listed but cannot be chosen.
If you don't have "edit settings"-permission to the tests, these ones won't be listed.

If you leave this page (choose another tab, close browser,...) it behaves like button "don't adopt changes": no other questions will be updated.

3.3 New User Interface Concepts

no new user interface elements needed

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: Seibt, Alina [alina.seibt]
• Maintainer: Strassner, Denis [dstrassner] & Becker, Maximilian [mbecker]
• 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

Seibt, Alina [alina.seibt], Feb 14, 2022: Summary of workshop discussion: 
general:

• operating errors: what if users change tests of others without permission because this function enables it when they have enough rights? 
• therefore the feature HAS TO BE enabled in administration first; standard: disabled
• versioning of questions would be helpful for this feature as well, because you directly can see if the question has been changed or not
• the feature shouldn't contradict any future ideas on versioning questions in tests & pools
• impact on statistics & if-loops not yet certain

discussion on implementation as interruptive modal:

• arguments from UI point of view: better without modal
• interruptive modal is used when there is an essential decision to take - this case is not essential, because you can skip the step (dont adopt any changes to tests)
• after clicking "save and return" a modal doesn't make any sense, because you still can see the same page while modal is open and return to another page (list overview) after closing the modal
• users won't expect a modal, it could confuse them » when it opens in a new page it'll seem more like "the next step" and will make more sense

, Apr. 20, 2022:

We just discussed this feature request and the following questions came up :

1. Is it possible to refresh the test listing page [F5] after deleting the test results ?
2. On which tab of the test do you land when you click on the link to the test ?
3. Wouldn't it be better if all tests were shown which use the edited question (i.e. those tests without "Edit-Permission" too) ?Currently, the test shows for each question from which question pool it came from.Scenario : the question pool creator wants to notify all question pool users that he found an error in one of his questions. If not all tests are displayed, he cannot notify accordingly.
4. Are offline tests listed too ?Currently, the test can be used to modify questions in offline question pools.
5. General question : Wouldn't it be better if only question pools were allowed to change questions within tests.Tests, however, should not in principle be allowed to modify questions in question pools.(see Biba model for data integrity).

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