Show own reservations in the booking overview

1 Initial Problem

Bookings are displayed in Booking Tool in the Reservations-tab. If the same booking object is to be reserved again, the already reserved time slots are no longer displayed in the calendar overview. This also applies to your own reservations.

If you want to get an overview of the slots you have already reserved during a new booking process, you have to open the booking dialog and the tab Reservations at the same time. Since there can be several reservations per booking object, it is very complicated to get an overview this way.

2 Conceptual Summary

Own reservations should be displayed in the calendar overview (week view), during the booking process. The reservations do not get a checkbox and are displayed in a gradation of "brand-success", because the reservation has already been made.

If you click on the title of the reserved time slot, the reservation is displayed in a modal.

• The Back-button takes you back to the booking process.
• If you click on Cancel Reservation, the reservation is cancelled. The modal is closed. The booking object is displayed again in the corresponding time slot.
• If the booking object is present in a certain number, a Save button is displayed instead of the Back button. The number can be changed in the modal. If you click on Save you will get a confirmation message in the modal. You can close the modal with the close-glyph in the upper right corner.
• You can close the modal with the close-glyph in the upper right corner.

This means that multiple reservations for the same timeslot are not possible. There can be exactly one reservation for each timeslot.

Current behavior:

• A booking object is available 10 times. A user can make 10 separate reservations for a time slot. He receives 10 reservations for the booking object for the same timeslot.

• A booking object is available 10 times. A user can only make one reservation per time slot for the booking object. If he wants to change the number of the booking object, he must edit the reservation.

This request is part of a major revision of the Booking Tool. The core of the revision is the introduction of a calendar overview. If the following request (Week View for Booking Tool) is accepted by the jour fixe, the own reservations should also be displayed in the overview (see Mockup).

3 User Interface Modifications

3.1 List of Affected Views

Booking Tool > Booking Object (if the Calender View for Booking Tool is introduced)
Booking Tool > Booking Object > Booking Process

3.2 User Interface Details

Mockups based on ILIAS 6

Mockups based on the introduction of calender view (Week View for Booking Tool)

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

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 Information

{ 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 Implications

{ 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:  Glaubitz, Marko [mglaubitz], Falkenstein, Rob [rob], Zenzen, Enrico [ezenzen]
• 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.

• Universität Freiburg

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}

Approval

Approved at {date} by {user}.