Improve the Sharing of Portfolios

We want to abandon the option to Share Portfolio with all registered Users. Accordingly, this option is not included in the feature request.

1 Initial Problem

The portfolio sharing process is very complex. Ready in the first step, users often overlook the options in the dropdown. To separate the options more clearly, the sharing process should be revised.

Single users should be able to be added more easily and quickly. To do this, users should not necessarily be taken to a sublevel.

2 Conceptual Summary

Some options for sharing should be taken out of the dropdown and be offered as separate buttons in the toolbar. For this purpose, a known pattern from the mail system/Courses and Groups should be reused. The user search for sharing should be streamlined and adapted to the user search in the mail system/Courses and Groups:

1. To add individual users, an input field is displayed. A user name can be entered here. User suggestions are displayed via autofill. By clicking the Share with User button, the portfolio is shared with the user.
2. A "My Courses" and "My Groups" button is displayed for each of the "Share with Course/Group" options. When users click on these buttons, they will see a list of all the courses and groups they are a member of. The rest of the workflow does not change at this point. 

3 User Interface Modifications

3.1 List of Affected Views

• Personal Workspace » Portfolio » Sharing Process

3.2 User Interface Details

See Conceptual Summary.

3.3 New User Interface Concepts

None.

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

{ 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

No Security Issues.

7 Contact

• Author of the Request: Zenzen, Enrico [ezenzen]
• 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.

• University of Cologne

9 Discussion

Killing, Alexander [alex], 29 Aug 2022: This feature request currently assumes that the option Share Portfolio with all registered Users will be abandoned in general. However this has been rejected (follow the link to see the JF decision). Morover this request does not take the options to share "with the WWW" into consideration. The request needs to specify the screens, if all these options are available/activated, which still is possible.

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