Task Service for 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

There is no task service for portfolios. By sharing his portfolio user has no option to notify his supervisor/tutor automatically. And supervisor/tutor has to look for a shared portfolio proactively in
Personal Workspace → Portfolio → Portfolios of Other Users → Search. It takes time and supervisors do not use portfolio funtion very often, unless they get a request from a student per email.

2 Conceptual Summary

Supervisor should be notified automatically about shared portfolios, he has to comment on. Once a student shared his portfolio with a supervisor and set the dates for sharing (it has its own feature request Time-limited sharing of Portfolios), a short entry appears automatically in the task list of the supervisor on his dashboard. Clicking the entry, the supervisor is automatically directed to the shared portfolio and can comment on it.

3 User Interface Modifications

3.1 List of Affected Views

Dashboard - Tasks
Personal Workspace - Tasks

3.2 User Interface Details

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

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

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