Enter evaluation statement in list view

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Giving Feedback is an important step in every learning process, and if learners get feedback often, that is even better. For this reason giving students feedback on exercises or assignments should be as easy and unfussy as possible. 
Right now giving one student feedback for one exercise requires to click on the „Actions“-menu, choose „Write evaluation statement“, writing the evaluation statement and clicking on “Save”. This process has to be repeated for every student and every assignment. Assuming that you have 40-60 students and more than 10 exercises, that’s a lot of clicking.

Please Note: There is a possibility to give students feedback directly in the "Grades View”. However, this “Remark” applies to the exercise as a whole, and not to a specific assignment.

This is the current situation when adding an evaluation:

2 Conceptual Summary

The process of giving written feedback could be streamlined considerably if tutors could write the evaluation statement directly in the Assignment view where the people who handed in something are listed.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

This is a mockup of the desired result:

3.3 New User Interface Concepts

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 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

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

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Weber, Frank [franklin66]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.