Introduce a start and end date for fixed schedules

1 Initial Problem

Schedules in the booking tool currently require do not have limits than can be set. We would like to support scenarios in which a future start and end date for time limits is allowed. This would also support cases in which appointments don't take place in a sequence but in a changing sequence.

Example: Room A offers a consultation hour course. It takes place in week 1 on Monday, 08.00-10.00 + Tuesday 09.00-11.00. In week 2 this course takes place on Monday, 18.00-20.00 + Tuesday 19.00-21.00. This is currently not easily implementable in the booking tool. If we introduced a new function for schedules which allows to set a start and end time for the schedule this scenario could be easily built using 2 schedules (schedule 1 = week 1; schedule 2 = week 2) and two booking objects.

2 Conceptual Summary

We would like to extend the schedule functionality by a new option which allows to set the start and end time of the schedule.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

Pic 1. Introduce a start and end date of the schedule.

{ 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: {Please add your name.}
• 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.

• …

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