You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What price the organization has to pay for a space is important information that should be possible to record
Different SpaceOwners will have different prices for the spaces.
For a municpal owner, a normal pricingsystem is:
One price for organizations that are local to the municipality
Another price for organization that are registered outside the municipality
A third price for private companies
They may also have a different price for activity for children and for adults.
The pricing can be per hour, per day or per event. The pricing is usually defined in the yearly budget, so it should have a from-to date, and if this years budget hasn't been added, we should probably list the last known price.
The text was updated successfully, but these errors were encountered:
Pricing is really relevant for most organizations, and also difficult to get right for the reasons you cite above. I can add that pricing is sometimes entirely arbitrary, with no rules set.
From my research it seems that attempting to create a data model for pricing is so complicated, that it's best not to attempt modelling it in data but just describe it as human-readable text. At least for now.
In our sketches this looks like this:
That said, we have one data point that's easy to model in data: What did others pay?
In the current sketches, this is added based on the reviews others have added for a given space, and give a quick glance indication of the prices paid:
I think that combining a freeform text field with information about what others have paid will give enough value for now. Do you agree?
The problem with freetext is that you can't really sort spaces based on pricing. For the MVP, it could be done like that, and the reviews could be used for estimating a price, but it will probably be almost as hard modelling the pricing with daytime, nighttime, weekend-prices, type of organization, etc, so it would probably be easiest to do these two with the same code.
I think this feature-request should be left for a later sprint, after the MVP is public.
What price the organization has to pay for a space is important information that should be possible to record
Different SpaceOwners will have different prices for the spaces.
For a municpal owner, a normal pricingsystem is:
One price for organizations that are local to the municipality
Another price for organization that are registered outside the municipality
A third price for private companies
They may also have a different price for activity for children and for adults.
The pricing can be per hour, per day or per event. The pricing is usually defined in the yearly budget, so it should have a from-to date, and if this years budget hasn't been added, we should probably list the last known price.
The text was updated successfully, but these errors were encountered: