Feature Wiki
Tabs
Booking Pool: Remove Legacy UI with ILIAS 11
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 3.1 List of Affected Views
- 3.2 User Interface Details
- 3.2.1 Bookings
- 3.2.2 Participants
- 3.2.3 Schedules
- 3.3 New User Interface Concepts
- 3.4 Accessibility Implications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
This feature page contains the UI changes which were made at the Booking Pool with ILIAS 11 in order to remove the Legacy UI at the tabs 'Bookings', 'Participants' and 'Schedules'.
In addition, the UI changes at the tab 'Bookable Items' is described at the Feature Request Booking Pool: Revision of List View in tab ›› Bookable Items.
2 Conceptual Summary
Mainly the legacy tables at the tabs 'Bookings', 'Participants' and 'Schedules' are moved to KitchenSink data tables.
3 User Interface Modifications
3.1 List of Affected Views
- Bookings
- Participants
- Schedules
3.2 User Interface Details
3.2.1 Bookings
Within the UI change, the Bookings table gets the standard bulk actions. Therefore all actions can also be used as bulk actions (according to the accounts permissions).
In addition, the bug 0037366: "Period for the reservation list" setting does nothing is fixed within this UI change.
Legacy UI until ILIAS 10
KitchenSink UI ILIAS 11 and above
3.2.2 Participants
Within the UI change, the Participants table gets the standard bulk actions. Multiple participants can be deleted therefore.
Please have a look at the Feature Request Booking Pool: Add possibility to remove Participants, because this was introduced and implemented within this UI change.
Legacy UI until ILIAS 10
KitchenSink UI ILIAS 11 and above
3.2.3 Schedules
Within the UI change, the Schedules table gets the standard bulk actions. Multiple unused schedules can be deleted therefore.
Legacy UI until ILIAS 10
KitchenSink UI ILIAS 11 and above
3.3 New User Interface Concepts
No new UI concepts needed, KitchenSink is used.
3.4 Accessibility Implications
No (new) accessibility implications, KitchenSink is used.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Samoila, Oliver [oliver.samoila], Lowe, Simon [simon.lowe]
- Authority to Sign off Code Changes: Joußen, Thomas [tjoussen]
4.2 Technical Aspects
{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
4.3 Privacy
No new personal data is stored within these UI changes.
4.4 Security
No new security implications within these UI changes.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Lowe, Simon [simon.lowe]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: Yesterday, 08:15, Lowe, Simon [simon.lowe]