Feature Wiki
Tabs
Multiple Actions for Ownerless Objects
Page Overview
[Hide]1 Initial Problem
It is not possible to delete several Ownerless Objects in administration >> Systemcheck.
Users must manually delete each object individually using the action menu.
This is very time-consuming and frustrating.
2 Conceptual Summary
Users should be able to select multiple objects via checkboxes in front of the object titles and then select option delete via a dropdown above the table.
To further simplify working with this table, the dropdown menu might contain the following entries in addition to Delete.
- Move
- Export
- Change Owner
3 User Interface Modifications
3.1 List of Affected Views
- Administration>>System Check>>Ownerless Objects
3.2 User Interface Details
3.3 New User Interface Concepts
None.
4 Technical Information
No special technical information.
5 Privacy Information
The implementation will use/modify the owner column of table object _data. This is unchanged compared to previous versions.
6 Security Implications
No changes compared to previous versions.
7 Contact
- Author of the Request: Zenzen, Enrico [ezenzen]
- Maintainer: Meyer, Stefan [smeyer]
- 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
Meyer, Stefan [smeyer] : I support this request. I suggest to introduce multiple actions for the commands:
- Move
- Change Owner
- Delete
Additionally I suggest to implement the following changes:
- Add additional column "Creation Date"
- Add fiter by "Name" and "Creation Date"
- Add "Description" to title column
- Make "Title" "clickable"
- Show "Full Path" and make path "Clickable". Remove column path and show path below title/description
JourFixe, ILIAS [jourfixe], 16 MAR 2020 : We highly appreciate this suggestion with the changes suggested by the maintainer and accept it for ILIAS 7. Please complete the sections for privacy and security issues afterwards.
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}.
Last edited: 27. Mar 2020, 09:40, Meyer, Stefan [smeyer]