Grading, Marking and Evaluating in Tests

1 Initial Problem

In Test we find in the Participant tab no information on Grades

• After clicking on "Show Test Results"-Action we get a table displaying Points, Percent Solved, Date and "Detailed Results"-Action, but still no Mark or Grade or Passed Status.

2 Conceptual Summary

Basic Concept is layed out in Streamlining Grading, Marking and Commenting

3 User Interface Modifications

3.1 List of Affected Views

• Test > "Results & Grades"

3.2 User Interface Details

3.2.1 Test

• Tests already feature mark schemas (will be Grade Schema) in their settings-tab. These ideosyncratic schemas must not be thrown away automatically, since it poses a legal risk to temper with test results. 
• New test objects get options to select a centrally prepared mark schema (will be Grade Schema) . 
• Heritage tests keep their original one. It becomes a "blind scheme", that is shown nowhere but in the consuming test. In the test the scheme can be scheme to a new central one manually. After this is done there is no way back. The blind scheme cannot be called back once it was removed. Blind scheme are never offered for selection.

3.2.2 Test > Results and Grades

• "Last Access"-column dies here, it is still available in the Learning Progress
• "Test Started"-column dies here, it ist still available in Participants-tab if the test has fixed partcipants, if a test does not have fixed participants the mere exisitence of a user in this table implies that the very person started the test. 
• "Graded On"-Column is not avialable here since the date stamp produced will be highly confusing for a human
• "Evaluation Statement"-coumn and "Evaluation On" are not available here the evaluation is only provided in the manual scoring tab. There it should be re-labled. Evaluation is sent by mail. 
• Grading and Marking are read-only since they are computed by ILIAS.

Please check Extract Test Results from the Participant tab and make a separate Tab of it

3.3 New User Interface Concepts

None.

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