Automatically select criteria catalog after adding it

1 Initial Problem

Criteria Catologues are a fine thing. In many cases users first create an excercise , the create a unit, setup the deadline and the peer feedback. While they set up the peer feedback they realize that something like criteria catalogues exist and thex hit the shy button "[+] Add criterial catalogue".

They then create and arrange the criteria. However, ILIAS does not automatically assign teh catalogue that has been created in the context of the unit to the respective unit. Users have to do that manually and many user do not realize that the catalogue actually has not been assigned.

2 Conceptual Summary

A solution for this problem would be to transfer the user directly to the screen / dialogue "Add new Criteria Catalogue" (usually on acessibly through the button "Add Catalogue" on "Settings" > "Criterial Catalogues") instead of sending them to the list of catalogues (they wanted to add one in the first place and not select one of the existing ones).

By this, the referring excercise unit could be remebered and the criteria catalogue created this way could be linked to that unit's peer feedback automatically. Even experience users would be guarded of foregtting to do this manually by this small change.

3 User Interface Modifications

3.1 List of Affected Views

• "Peer Feedback"

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

none

6 Security

none

7 Contact

• Author of the Request: Glaubitz, Marko [mglaubitz]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: Killing, Alexander [alex]

8 Funding

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

• Universität 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}.