Delete courses via dashboard

1 Initial Problem

It would be helpful if users would have the possibility to delete courses directly via the dashboard because they have direct access to their courses there. There are users who cannot find their way through the repository or who are not allowed to do further administrative actions on the platform and therefore need this direct access.

2 Conceptual Summary

Administrators (global), course administrators (local) and owners of a course have the permission to delete courses. To do so, they must be in the right container object and can then delete the course via the Actions menu.
This should now also be possible via the dashboard, in which the Actions menu of the course is enriched with the function "Delete" for the permitted users, if this has been activated in Administration > Dashboard. 

3 User Interface Modifications

3.1 List of Affected Views

• Actions menu for courses on Dashboard
• Administration > Dashboard

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

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

{ 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: Lorenz, Katharina [klorenz]
• Maintainer: Szmais, Ingmar [iszmais] und Scharmer, Lukas [lscharmer]
• 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.

• Hochschule Bremerhaven

9 Discussion

Lorenz, Katharina [klorenz] 02 JAN 2023: Thank you Lukas for your comments via Discord, I have added the information you requested (Who is allowed to delete? Configurable?).

Scharmer, Lukas [lscharmer] 20 FEB 2023: After a discussion with Szmais, Ingmar [iszmais] we agree that this proposal uses the Dashboard as a configuration view for courses, which is not the purpose of the Dashboard and which is why we do not recommend this feature.

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