Hide resources that have been shared with me

1 Initial Problem

Portfolios, blogs and files can be shared with other users. A classic use case: a learner shares a resource to a teacher.
After this sharing has exceeded its need, the sharing remains mostly. This leads to the overflow of shared resources on the teacher.

The table violates the User Name Presentation Guideline.

We prefer "teilen" over "Freigabe" in German Language. 

2 Conceptual Summary

Users should be able to actively remove / disable sharing for these resources.

We can share with individual users, all registered users or members of courses / groups.
Receiving users could theoretically remove the resource shared with them. But if it was shared with them via a membership there is no easy opt-out. 

We suggest to

1. be able to hide list entries in the table actions. This will result in two shy buttons Hide and Copy. We discussed Split Buttons and multiactions and decided against it.
2. a "Show Hidden Resources"-filter is available. 
3. Column should be sortable (besides Shared With)
4. to change the order of the table columns and give the table a "Cloumn"-picker to manage the columns

• Name [Last Name, Firstname] > shown by default but hideable
• Login > hidden by default
• Type (former "Type of Resource") > always shown
• Title (former "Title of Resource") > always shown
• Shared With > shown by default but hideable
• Date of Share  > hidden by default Action

3 User Interface Modifications

3.1 List of Affected Views

• Shared Resources in Workspace
• Shared Resources in Portfolios of other Users

3.2 User Interface Details

OS: New Mock-Up

3.3 New User Interface Concepts

No.

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 Contact

• Author of the Request: Samoila, Oliver [oliver.samoila]
• 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.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

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