Feature Wiki
Tabs
Schedule Based Restriction of Bookings
Page Overview
[Hide]1 Initial Problem
The booking process does not check if the user already booked another resource for the requested timeslots. For example: Say you have a laser (resource 1) and a plotter (resource 2). Both resources share the same schedule and can be booked from 09:00 AM till 12:00 AM. User can book the laser first and then the plotter, even if:
- the resources are not at the same location and booking them at the same time does not make sense due to travel time
- booking (or rather "blocking") both resources at the same time is not allowed
2 Conceptual Summary
An new configuration setting for schedules is introduced that, when activated, will alter the booking process so that: ILIAS will check if the user has an at least 1 active reservation for another resource sharing the schedule. If that is the case ILIAS will not show the time slots booked in the active reservation.
3 User Interface Modifications
3.1 List of Affected Views
- book/schedules/edit
- book/object-schedule/book
3.2 User Interface Details
![](./data/docu/mobs/mm_68016/schedule-based-restriction-of-bookings.png?il_wac_token=9aeec562d79b160b48c7fb21e3c3e0ace48c1854&il_wac_ttl=5&il_wac_ts=1725755810)
3.3 New User Interface Concepts
No new user interface concepts.
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 Contact
- Author of the Request: Sesterhenn, Fabian [sesterhenn]
- 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.}
6 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
7 Discussion
8 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}.
Last edited: 30. Apr 2019, 13:26, Sesterhenn, Fabian [sesterhenn]