Booking Pool: Revision of tab ›› Schedules ‹‹ within Removing LUI

1 Initial Problem

The tab "Schedules" of the Booking Pool uses a Legacy Table and a Legacy Confirmation Screen.

2 Conceptual Summary

The two screens will be moved to KitchenSink Data Table and Interruptive Modal.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

3.2.1 Booking Pool ›› Schedules

The Legacy Table is moved to the KitchenSink Data Table. There is no need for a View Control, because in the most cases there are only a few Schedules. There is only one Bulk Action: Delete.

3.2.2 Booking Pool ›› Schedules ›› Delete Schedule

The Legacy Confirmation Screen is moved to KitchenSink Interruptive Modal. There are no special needs.

3.3 New User Interface Concepts

There are no new UI concepts.

3.4 Accessibility Implications

There are no Accessbility Implications.

4 Additional Information

4.1 Involved Authorities

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

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

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

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}

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