Duplicate calendar opening validation

Created on 8 June 2024, 7 months ago

I'm wondering if it would be feasible to have the option to validate if a calendar opening will create duplicate or overlapping opening instances.

Currently you can create as many calendar openings as you want for the same date/time period, I understand that you may want to offer several different things that are happening at the same time that can be booked, however I believe the more common use case is that only a single bookable instance would be offered during any paticular date/time range, especially considering the concept of available slots.

This creates an issue for the site admin trying to organise/maintain their calendar, where they can easily create duplicate and overlapping openings for the same thing which in many cases will be a mistake. They have to look at what openings are already there and ensure they don't add the same thing again.

Some kind of conflict check that provides a warning or a stop would massively improve the robustness of this module, I would see this as being an option that can be turned on, like "Warn on duplicate/overlapping openings", this could just provide feedback like "This calendar already has an opening for this date/time range, do you want to continue?".

I'm not sure the best way to detrmine a conflict, considering that the calendar opening has a free-text Title field. Possibly just check if an opening exists with the same title and same date/time range, this would at least be an initial improvement.

Ideally I think it would be preferable for this module to have the concept of Calendar Opening Types which can be added in the configuration settings, then when a calendar opening is being added, you choose the opening type from a list instead of just typing in a random title each time. This wouldnt take away any existing functionality and would make things like the above validation easier. The opening types wouldnt need to be entities, its doesnt need to be complex, a simple list held in config would be fine.

Happy to help in whatever way I can if this seems like a good idea.

Feature request
Status

Active

Version

2.2

Component

Code

Created by

🇬🇧United Kingdom problue solutions Northern Ireland

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024