Bulk actions for booking objects

1 Initial Problem

Some users have a lot of booking objects in their booking pool. The booking objects often are temporally and have to be removed after one or two terms. With the functionality of the booking pool, every single booking object has to be removed individual.

Additionally it is not possible to copy booking objects in order to paste them into another booking pool.

This all leads to the idea to implement bulk actions for the tab booking objects of the booking pool, like e.g. at the member tab of the course.

For booking objects the actions delete, copy and book would be suitable actions. All other actions (cancel, edit) should not be done together in my opinion.

2 Conceptual Summary

Add bulk actions for managing booking objects.

3 User Interface Modifications

3.1 List of Affected Views

• Tab Booking Objects in booking pool

3.2 User Interface Details

• Add Checkboxes to the list/table of booking objects.
• Add Dropdown-menu with the options "Delete" and "Copy" above the list.
• Add the option "Copy" to the actions-menu.
• Copying booking objects is available via the clip board.
• If some booking objects are in the clip board, the button "Paste" has to appear.

3.3 New User Interface Concepts

Not needed.

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: Lowe, Simon [simon.lowe]
• Maintainer: Killing, Alexander [alex]
• 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

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