Introduce the Grading Service within Courses

1 Initial Problem

Courses do not aggregate Marks from enclosed objects. 

2 Conceptual Summary

The Grades-tab features the following sub-tabs

• Members to view results of individual users
• Settings to add weights and create optional batches
• Mark Schema to select a centrally administered Mark Schema 

Members

• Only marks are aggregated to a mark and have a weight. 
• If objects are merely graded they are considered "required" while not have a weight assigned to them.  Since the weight would not be reasonable to compute from it. 
• If optional marked items are completed above requirement, the best marked is considered in aggregation of a mark.

Settings sub-tabs

The Settings sub-tab features the following columns: 

• Batches of optional material can be created: Complete 3 of 5 
  • Items of a batch have to be all graded and thus will be aggregated without an assigned weight OR 
  • Items of a batch have to be all marked and the whole batch and have 1 weight assigned
• The Grading will only aggregate grades and marks that comply with one of the centrally administered mark schemes. If an object does not comply, it will be pointed out to users. 

Mark Schema sub-tab
The Mark Schema is done in percentages not in points.

3 User Interface Modifications

3.1 List of Affected Views

Grades-tab > NEW

3.2 User Interface Details

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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

Lauener, Hansjörg [lauener], 9.10.2018. Some general ideas.
a) global administration: Allow ILIAS-administrators to turn this functionalty and tab "off,on"
b) think about a history-feature for gradings (and/or the aggregated grading-view). Grades are really relevant for students/learners, so it should be possible to have/see the history of every change in every grading.
c) why not support these aggragated gradings also in groups? => example: "Ernennungskommissionen" at universities could maybe use this feature, when they are in a decision process. Individual marks would be collected automatically and shown in the aggregated view.
d) think about persisting. If a course is deleted, so are the grades produced by it, too!? Or do you want persisting gradings (similar to persisting certificates)?

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