Extension of the sharing options

1 Initial Problem

So far, portfolios in ILIAS can be shared with different users and user groups, but sharing for courses and groups requires that you are a member of the course or group yourself.

Currently, it is possible to select individual persons when sharing via a group, but the missing role specification makes it difficult to select the desired persons (see Figure 2). Furthermore, only if the option "Release for all members" is selected, members that were added later, receive the right to access the respective portfolio automatically.

2 Conceptual Summary

Portfolios developed by students should be made available to users assigned to a specific role. 

The sharing options include "Course Administrators" and "Group Administrators".  If selected the workflow should be exactly as implemented for "Course Members" or"Group Members" but with different local role. 

3 User Interface Modifications

3.1 List of Affected Views

• Personal Workspace > Portfolio > Action menu of specific portfolio, Action "Share" > Tab Share

3.2 User Interface Details

3.3 New User Interface Concepts

No new UI Elements

3.4 Accessibility Implications

No new controls, merely another option in an existing dropdown. 

4 Technical Information

The current implementation of the second screen is part of Services/Contacts. There are several classes like ilMailSearchObjectGUI which contain code that should be part of the Workspace component. This needs a general refactoring of the interface or a strong decoupling by moving/copying code.

5 Privacy

Current privacy status for portfolios: https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/Modules/Portfolio/PRIVACY.md

This feature will slightly change the way how groups of users are identified when resources are being shared. Internally it will continue to store single user IDs, group, course or role IDs to identify the target group.

6 Security

No security issues.

7 Contact

• Author of the Request: Elena Brinkmann
  
• Maintainer: Killing, Alexander [alex] (Workspace), Jansen, Michael [mjansen] (Contact/Mail)
• 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

Killing, Alexander [alex], 24 Nov 2022: I hope that all language experts are ok with the presentation of participants/members, Teilnehmer/Mitglieder this way. I have no strong preferences here, but support this, if this is the current way to deal with this. From the technical side, there are some challenges. The current implementation is partly done in Services/Contacts and Michael and I should agree on how and if these components should interact in the future. Currently there are multiple SoC voilations and no strong interfaces.

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