Introduce Mark Schemas in Individual Assessment

This article belongs to the project Gradebook and builds on the concept of Centrally Administrating Mark Schemas.

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.

2 Conceptual Summary

This article aims at introducing mark schemas within the Individual Assessment. These mark schemas can either be globally created or locally.

The Individual Assessment will introduce the functionality of mark schemas (use/don't use) within the settings tab and then allow instructors to mark individual users according to the chosen mark schema.

3 User Interface Modifications

3.1 List of Affected Views

• Individual Assessment -> Settings
• Individual Assessment -> Participants

3.2 User Interface Details

{{Put in here Screen 1: Settings}}

Screen 1: Still missing.

Screen 2: Mark Schema within the Individual Assessment.

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.

• bwILIAS/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}.