Open fysch opened 3 years ago
While I get the idea I'm not sure if this works with Sabre. Sabre needs to identify each resource uniquely and right now that is done via an email address. If you have x instances of the same resource then they all need a unique identifier for Sabre to figure out availability.
I'm not familiar with Sabre, but maybe this could be resolved "in between".
When a user creates "Soccer Ball" with quantity 20, it will create something like multi_[uniqueId]_soccer_ball_1, multi_[uniqueId]_soccer_ball_2, multi_[uniqueId]_soccer_ball_3 and so on.
And if a user wants to book multiple soccer balls, the first n balls will be reserved.
"multi" is the keyword, that there are multiple soccer balls and [uniqueId] should help us to identify them. But there are probably much more pitfalls.
Let's first get make rooms and resources work nicely, then we can look into these special cases :wink:
Feature Request
Add a "quantity" attribute to resources, such that the same resource can be booked multiple times. Especially for resources with a high quantity, this would make booking higher amounts much easier.
Example
Create a resource "Soccer Ball" with quantity 20.
Soccer-Teams 1 and 2 have their training at the same time.
Soccer-Team-1 assigns 15 soccer balls to their calendar event. Soccer-Team-2 can now assign max. 5 soccer balls to their calendar event.