Use test results as preconditions

1 Initial Problem

In some scenarios a more granular handling of preconditions from test results is needed than the current "passed/failed" solution.
As an example, it can be required to offer learning materials or object access for three (or more) variations like

• Users with a testresult of 0% to 50% can access object A, but not B or C
• Users with h test result of 51% to 75% can access object B, but not A or C
• Users with a test result of 76% or more can access object C, but not A or B

So after finishing a test, Users have access to one of three objects, and don't have access to any of the object before a test result is available

This Entry is related to: Preconditions based on test mark schema

2 Conceptual Summary

When adding preconditions, tests shoud have a new option. In addition to the current optoins (passed/failed, started, finsihed) there should be a new setting "test result from...to" with 2 numeric inputs for %-values as integer numbers. (fractional numbers could be considered, too)

If the testresult for the current user matches the range given (including the values of the numeric fields), access to the object is granted. Input should be validated, so that min <=max is given, and min >=0, max <=100.

This concept could/should be extended to learnig objective results, too. This gives further granularity for didactic designs, since learning objectives use a subset of the testquestions 

3 User Interface Modifications

3.1 List of Affected Views

Input screen for preconditions

• The test precondition requires a new choice "Percentage". If this is activated, we need an input for a minimum and maximum prcentage for this precondition. Min may default to 0%, max may default to 100%

If test results are selected, inputs for minimum and maximum should appear (possably indented)

In the precondition list GUI, the chosen precondition should be listed

For this screens 3-4 language variables will be needed (Selector for precondition, Labels for min/max percentage, optionally text for the list view (if Selector is not used here)

If possible, the screen that is used  to choose objects as preconditions could offer learning objectives, too. the choices for the precondition should be passed/failed/percentage like in tests (finished/not finished/derive from LP con be omitted here)

3.2 User Interface Details

see mockups in 3.1

3.3 New User Interface Concepts

no new UI Concepts

3.4 Accessibility Implications

no A11Y implications forseen

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

as stated by T&A, it is not advised to use direct database reads to gather testresults.

As a suggestion (by a non-maintainer) a starting point to fetch user's test result percentage could be the function ilObjTest::getAllTestResultsfor tests.

If learning objective results should be used as precondition, too, the required data is already caculated and stored separately from the test.

5 Privacy

no privacy implications expected

6 Security

no security implications expected

7 Contact

• Author of the Request: Jackisch, Ingo [jackisch]
  
• Authorities: Meyer, Stefan [smeyer] for Precondition Handling
• Implementation of the feature is done by: Meyer, Stefan [smeyer]

8 Funding

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

• DHBW
• …

9 Discussion

Strassner, Denis [dstrassner], 2024-05-07: We (Ingo Jackisch, Stefan Meyer, Thomans Joussen, Max Becker, Denis Strassner) discussed this Feature Request today and agreed that the idea is charming. As authorities for the test, we defined, that we don't want to add only the percentage value in " ilObjTestAccess" but revise this class to have a state-of-the-art implementation. 
We set the "checked and attendance" setting in the JourFixe Data Collection for the next JourFixe to have a go for the Feature from the JourFixe. 
It is certain that we will need appropriate funding for this feature and the revision of the implementation in Test & Assessment. We intend to ask other stakeholders to join the DHBW to fund the implementation of this feature after the approval of the JourFixe.

JourFixe, ILIAS [jourfixe], 13 MAY 2024: We highly appreciate this suggestion and schedule the feature for ILIAS 10 / trunk. IF sufficient funding is available, the support of learning objectives results could be implemented, too (please indicate in chap. Implementation).

10 Implementation

This feature request tackles the implementation of the Precondition Handling to realise the above mentioned behaviour. Due to the fact that the necessary implementation on the T&A's side couldn't been realised for ILIAS 10, the feature cannot be used with ILIAS 10. The necessary ‘Refactoring of ilObjTestAcces‘ will hopefully be realised with ILIAS 11.

Approval

Approved at 2024-10-17 for the precondition handling but not T&A by Houssi, Dhouha [Houssi] and Jackisch, Ingo [jackisch].