Introduce Mark Schemas in Test

1 Initial Problem

Currently, ILIAS offers many components that might be part of exams such as the test, the exercise or the individual assessment. There is, however, no opportunity to aggregate the results of these components in a final mark (e.g. A-F). This could be corrected by introducing the grading service within the mentioned components and their respective containers.

The test is especially tricky since this object already allows a kind of grading within the sub tab "Mark Schema". Thus, more concept work will be needed than for the individual assessment or the exercise.

2 Conceptual Summary

This article aims at introducing the global Marking Schemas within the test or at streamlining the current mark schema functionality of the test in accordance with the grading service/Centrally Administrating Marking Schemas.

Our final goal is to be able to summarize the results (Marking Schemas) of different objects in an overall grade. In order to achieve this every object that can be part of the final grade needs to adapt a marking schema.

3 User Interface Modifications

3.1 List of Affected Views

This is still preliminary:

• Test --> Settings
• Test --> Mark Schema

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

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: Falkenstein, Rob [rob]
• 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.}

8 Funding

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

• Uni Freiburg

9 Discussion

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