Add optional Deadline to Booking Mode No Schedule, Direct Booking

1 Initial Problem

The current available booking modes are not covering the following scenario: The booking tool is often used to distribute topics or similar things to students. There is no need for a schedule for every single booking object. For this reason, the teacher would have to choose the booking mode "No Schedule, Direct Booking". When choosing this booking mode, it is possible to limit the number of bookings.

In our scenario, the topics have to be distributed until a fixed deadline, e.g. because the bookings have to be approved by the teacher or the students have to start with their work.

We tested a few different settings, also with the other booking modes, but there is no user-friendly way to implement this with the current booking modes. A limited availability for the booking tool would stop the students from booking new objects, but then they also are not able to view the already booked objects.

2 Conceptual Summary

The Booking Mode "No Schedule, Direct Booking" is supplemented by an optional deadline. Bookings can only be made until the deadline.

3 User Interface Modifications

3.1 List of Affected Views

• Settings of the booking tool, in detail the booking mode settings
• User-View before passing Deadline
• User-View after passing Deadline

3.2 User Interface Details

3.2.1 Settings of the Booking Tool, Booking Mode

3.2.2 User-View before passing Deadline

3.2.3 User-View after passing Deadline

3.3 New User Interface Concepts

There are no new UI-elements needed.

3.4 Accessibility Implications

No Accessibility Implications.

4 Technical Information

No technical issues.

5 Privacy

Current state: https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/Modules/BookingManager/PRIVACY.md

This feature will not implement any privacy related changes.

6 Security

No security issues.

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

JourFixe, ILIAS [jourfixe], 21 AUG 2023: We highly appreciate this suggestion and schedule the feature for ILIAS 9.

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