Automatic Save of Assignment Evaluation in Portfolio

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

Portfolio Assignmet type offers many possibilities for different learning scenarios. However, it is still very difficult for users to receive and save a performance evaluation automatically and  for longer period of  time.

• if evaluation statement is written directly in the assignment, then it is gone after its deletion.
• if evalution is sent via email, then it has to be inserted into portfolio manually by a user
• if evaluation is received per mail, it can be saved for a long term, but user has no option to connect it to the content in portfolio

• open submission does not offer any comment or feedback function

• tutors do not have access to portfolios of the users, if they are not set online and shared. Therefore they cannot use comment funtion in portfolio directly.

2 Conceptual Summary

We propose to save received evaluation directly in the portfolio, to which this evaluation was given. This adjustment will let users to save both portfolios and evaluations in their personal workspace as long as they need it.

3 User Interface Modifications

3.1 List of Affected Views

Content of Portfolio Submission

3.2 User Interface Details

3.3 New User Interface Concepts

None

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 Information

{ 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 Implications

{ 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:
• Maintainer: Killing, Alexander [alex]
• 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.

• …

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