Apply test defaults every time

1 Description

The option to apply a default onto a test is really great! At the moment, the following sentence will displayed, when you would apply a default setting onto a test, which contains already questions:

ILIAS could not apply the selected test defaults to this test! Maybe this test already contains questions and/or participant datasets.

But it would be nicer, if you can change the default settings also when you have filled up the test with questions already.
Could this be possible? This would have the advantage that default settings could be applied, on tests, which were already made. What you think about this?

2 Status

3 Additional Information

4 Discussion

JF 3 May 2010: We guess this is the case because settings like "random selection of questions" may interfere with the defaults feature. But we agree that this could be improved. The "defaults" feature should not change settings when a test contains already participant datasets. But as long as no user has run the test, settings may be changed also by assigning a "default" setting set. In case of changing a setting for questions from pool to random (or vice versa) the same warning message should be shown to the author as it is already done when changing settings manually.

Jour Fixe, 01 August 2011: There was no decision about this feature at the Jour Fixe yet. There are still conceptual issues with this feature. Therefore we will not make it part of 4.2. We will schedule this feature for 4.3.

JF 23 July 2012: Björn, please get in contact with us and/or put this on the JF agenda. We need to discuss how and if this feature will make it in 4.3.

BH 20 August 2012: The feature is allready developed in the elba branch. When applying defaults to a test that already contains questions, but no test results, the same behaviour gets in due to the problematically settings like random/fixed question selction as when changing these settings manually. Also the same implicit setting changes on saving like resetting the online status are involved including the subsequent notice for the user.

JF 20 Aug 2012: If settings templates result in any conflicts and user warning need to be displayed, this should be done in the same way as if the settings have been changed manually.

5 Implementation

BH, 12. Nov 2012: The feature has been merged into trunk for 4.3