IRSS: Delete Resources in Resource-Overview

1 Initial Problem

All files stored in the IRSS are already listed in the resource overview and links to the respective components can be used to show where they are used. However, resources cannot currently be deleted in this view.

2 Conceptual Summary

The stakeholders, which are used to identify who is using a resource, have had a method since the beginning that can be used to react to the deletion of a resource; this functionality has not been used so far and is now to be used for ILIAS 10.

By deleting a resource in the administration (or possibly later in other ways, e.g. if the videnscanner subsequently detects a virus), the relevant stakeholders should react to this deletion. in some cases nothing needs to be done, other stakeholders must, for example, delete the entire object that uses the resource. others may want to inform the owner of the resource about the deletion. what exactly happens when a resource is deleted in the consumers is decided by the respective components and the stakeholders.

3 User Interface Modifications

3.1 List of Affected Views

• Administration > General Settings > File Services > Resource Overview

3.2 User Interface Details

In the Actions-menu of a Component we will implement a new Entry "Delete" which opens a Confirmation (Modal). After confirming the deletetion, all involved stakeholders (in moste cases only one) are informed using the \ILIAS\ResourceStorage\Stakeholder\ResourceStakeholder::resourceHasBeenDeleted method.

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

The use of existing UI components does not introduce any new implications for accessibility.

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

See conceptual summary

6 Security

The implementation of the feature does not introduce any new attack vectors. there are no further special security-related considerations to be made.

7 Contact

• Author of the Request: Schmid, Fabian [fschmid]
• Maintainer: Schmid, Fabian [fschmid]
• Implementation of the feature is done by: sr.solutions

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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.