Feature Wiki

Information about planned and released features

Tabs

Recurrent Bookings

Page Overview

[Hide]

1 Requirements

It should be possible to do recurrent bookings. The start date is determined by the selected slots (see the following screen of ILIAS 4.4). The form needs to get two additional inputs:
  • Recurrency: No recurrency, Weekly, Every 2 Weeks, Every 4 Weeks.
  • Recurrency End Date
After the user has entered these dates, ILIAS has to check, if free items are available for all the recurrent dates. If not, a failure message is displayed and the user has to modify the values.
 
Other recurrence types for bookings, e.g. monthly, are currently not possible, since the schedules only provide weekly recurrences. This would need different types of schedules first.
Booking Screen ILIAS 4.4

2 Status

  • Scheduled for: Release 5.0
  • Funding: Kivinan BBS Zeven
  • Maintainer: Jörg Lützenkirchen
  • Implementation of the feature is done by Leifos
  • Contract settled: Yes
  • Tested by / status: (name, e-mail), (status information set after implementation)

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:
  • Information about concept: Alex Killing, killing (at) leifos.de
  • Information about funding: Wolfgang Hübsch, Kivinan BBS-Zeven, wolfgang.huebsch  (at) kivinan.de
  • Information about implementation: (name, e-mail)

4 Discussion

JF 11.11.2013: We appreciate this feature and schedule it for 4.5.

Matthias Kunkel, 16 Jan 2015: There is one usability issue in the booking workflow that should be fixed: On the screenshot below I have booked an object starting at Jan 27 for "every 14 days". Now I have to define an end date for recurrence. Fine! But why does it offer me "16 January 2015" as first value? A date that lays in the past when the first booking takes place. It shouldn't be that difficult to show a reasonable date for this date field. And reasonable would be e.g. 10 February 2015 (=Jan 27 + 14 days).

I have added a suggestion for a Time Default Values Guideline and would like to discuss it on the next Jour Fixe.

JF 19 Jan 2015: Jörg will set a default to the date of the earliest time slot.

5 Implementation

JL 24 Feb 2014: This has been implemented as described above in trunk/4.5. The list of reservations has been enhanced to be able to handle large numbers of bookings.

JL 17 Jun 2014: we completely overhauled the reservation list. It now groups the bookings by date and has enhanced filters. "In use" has been removed.

Last edited: 19. Jan 2015, 16:12, Killing, Alexander [alex]