While it is easy to create single bookings, many uses of the Common House recur on a regular schedule (circle meetings, interest group meetings, etc.)
Status quo
- each booking must be created individually, entering the same information repeatedly for each occurrence
- if changes are needed due to schedule changes for the meeting, those must be done individually to each occurrence
Impact of status quo
- Circle admins and interest group coordinators do not book circle meetings into the future
- Conflicting bookings when two groups book the same space at the same time
Suggestions for possible approaches
- Link the spaces to be booked to a full calendar system (e.g. Google Calendar), let that calendar system manage recurrence
- Create a calendar system in Rails which permits the same flexibility for recurrences as Google Calendar/Outlook/Apple Calendar
While it is easy to create single bookings, many uses of the Common House recur on a regular schedule (circle meetings, interest group meetings, etc.)
**Status quo**
1. each booking must be created individually, entering the same information repeatedly for each occurrence
2. if changes are needed due to schedule changes for the meeting, those must be done individually to each occurrence
**Impact of status quo**
- Circle admins and interest group coordinators do not book circle meetings into the future
- Conflicting bookings when two groups book the same space at the same time
**Suggestions for possible approaches**
1. Link the spaces to be booked to a full calendar system (e.g. Google Calendar), let that calendar system manage recurrence
2. Create a calendar system in Rails which permits the same flexibility for recurrences as Google Calendar/Outlook/Apple Calendar