Book things for several days in a row

1 Initial Problem

The booking tool in ILIAS works on the basis of a time grid, which indicates an availability of booking objects in hours that refer to weekdays.

We would like to use the booking tool for booking equipment that can be rented / booked for several days. Therefore, the booking period is a period described in days with a maximum booking period that varies depending on the rental day and how long someone want to rent something.
e.g.: You want to book a vacation apartment from 3 days to a maximum of 28 days.

We are therefore missing a presetting of the time schedule with the following parameters in the booking tool:

- Time slot screen: setting of booking periods in days, not hours

The time slot must not have a time, just the days.

- Add Item screen:
new setting: “How long in a row could someone book” e.g.: 28 days in a row

- After Booking and by selecting “Book multiple dates” in the Booking Confirmation Screen a new opportunity should be given

2 Conceptual Summary

We want a behavior that allows us to book things over several days without specifying a time. Just as we know it from vacation homes or similar, for example. But we have tried to integrate this wish into the existing behavior of the booking tool.

2.1 An example based on wordpress

Example for booking items over several days

2.2 Sceenshots (Mockups)

In addition to the perhaps simple implementation here, it should also be discussed whether a monthly view would be possible and whether the calendar in ILIAS can be used again.

3 User Interface Modifications

3.1 List of Affected Views

• Time slot screen: setting of booking period in days not hours

• "Add item" screen: new setting: “How long in a row could someone book” e.g.: 28 days in a row
• the modal booking confirmation:  After Booking and by selecting “Book multiple dates” in the Booking Confirmation Screen a new opportunity should be given.

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

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

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: Schroeder, Thomas [Thomas.schroeder]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• HSPV NRW

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