Show Advanced KnowledgeHide Advanced Knowledge

Rubrics

1 Initial Problem

Learning Progress and Competence Definitions are means to set out a yardstick for performance that can be automatically be applied by ILIAS. 

However there is a negotiational aspect in erecting and applying performance, behavior, or quality objectives: 

• What consitutes good performance? Outlining the criteria, substantiating criteria 
• What are the gradations of performance? Performance characteristics arranged in levels 

"Laying out" of objectives cannot be participatively done in Learning Progress or Competences. 
"Assessing performance against objectives" by means of self-evaluation or peer-feedback is not accomodated by the Learning Progress.  It can be using the 360° degree survey but not using negotiated objectives. 

2 Conceptual Summary

Scoring rubrics include one or more dimensions on which performance is rated, definitions / examples that illustrate the attribute(s) being measured, and a rating scale for each dimension.

• Criteria Title and Description: One or more criteria that serve as the basis for judging the students work
• Level Titel and Description: Level and with text clarifying  standards of excellence for this very performance level
• Radio Buttons: A scale of values on which to rate each dimension

The Scoring Rubrics is presented as a grid. 

The Rubric is a new tab in the course. The new tab is to be switched on in the Settings-tab of the course. 

RBAC controls who has access to the tab and has the permissions: 

• view
• read
• edit 
• feedback 

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, 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

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