Show Advanced KnowledgeHide Advanced Knowledge

Preconditions based on test mark schema

1 Initial Problem

It is currently not possible to setup preconditions that react on how well a student has performed in a test.

2 Conceptual Summary

It should be possible to set up preconditions based on data that mirrors a qualitiative dimension and goes beyond the learning progress states (passed, failed, finished, not started) of a test. 

When a test is selected as a predondition object, ILIAS should offer two different modi:

• Standard (default) use Learning Progress status
• Based on mark schema

Precondition mode "Based on mark schema":

• Label "Mark schema level"
• operator dropdown: {<, <=, =, >=, >}
• a dropdown should show the currenly available mark schema levels (an thir labels) in ascending order of percentages

Challenge: How should chnaged mark schemas be handled by the precondition system?

• Option 1 "Automatic Fallback": if the preset mark schema level for the precondition is not available anymore another one is used (logical choice depending on the operator)
• Option  2 "Inform User": when a user changes the mark schema of a test, the test checks on saving if its mark schema ist used somewhere as a predcondition. if this is the case, an information box (blue) is shown that tell the user
  
  "The mark schema of this test is used as a precondition for some objects. Please check the precondition setting of these objects to adapt them to possible changes:
  * bullet-point-list of affected objects"

Mark schema dependent preconditions sould be combinable with the existing preconditions.

• Fall-downs from one level of accomplishment to a lower level should be possible: if a file has been made available, because a user has been passed test A with 70%, the file should be made unavailable when the user retakes the test (voluntary or involutary) and achieves only 50%, the file whould be made unavailable again  (of course this is only possible when, for example, the test is configured to take the result of the last and NOT the best test run)

{Please add a brief summary on how you would like the problem to be solved.}

This Entry is related to Use test results as preconditions

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

• Author of the Request: {Please add your name.}
• 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.}

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