What about a marker (simple boolean) to show, if a event is open air or not?
I can imagine that it can be at the event entity or the place. What do you think?
You can link the event to a place, it’s the place that should show this open air info, IMO, rather than repeat it on all event for this place.
The type of place already kind of tell this info, no? Stadium, hall, studio, etc.
1 Like
What about when the main stage is in the open, but some of the smaller stages are under canvas?
I would say some place types do indicate if it is open air or not. But some are unclear about this or do not tell anything at all. Festival stage for example can be open air, in a tent or indoor.
And I think you are right, it should be located in the place, not the event. I think a place can not be open air sometimes and indoor at another time, or?
1 Like
There is always an exception…
Sometimes indoor halls hold events outdoors.
De La Warr Pavilion, Bexhill on Sea.
They hold plenty of concerts indoors in the winter. Last summer that event above was scheduled for outside in the grounds. Then a storm was scheduled and they moved the whole event inside at two days notice. Aircon could not really keep up so you could see why outside was preferred.
But maybe then it is better to have sub places for the venue? Like we have the festival stages as separate places with part of rel.
And when there is a change in place one have to edit anyways.
1 Like
Yeah, the sub-places makes sense to have inside\outside flag attached. These already exist with the main MB Places. I’ve not gone into Events much, but do plenty of adding bootlegs to the main MB.
So a marquee tent is inside due to the roof even though it doesn’t have walls?
And a performance at Cardiff Castle would be outside as it has walls, but no roof.
A simple definition - do I get wet when watching?
1 Like
Some stadiums have closeable roofs too. Not sure how much it matters at that level though, since I’m not quite sure what the usefulness is really of open-air vs not. Is it about the acoustics, or about getting wet if it rains? 
2 Likes
I think closable locations are a rare edge case we don’t have to handle. And the open or close during an event seems even more rare.
So should I create a ticket or is it not important enough?
Btw. I can imagine more fields I would like to use. But I think they are too niche. Maybe there is another way to save that information?
I am talking about
- sold out
- sold out date
- approximate entry price
- approximate people capacity for places
and so on.
Maybe Annotations? But the single information is not machine readable because it is just plain text. Maybe we can use some kind of convention like key value pairs with a specific syntax. Then a client can parse that information.
These two I find interesting personally
re. sold out data, I find it a bit tricky data-wise and personally not so interesting, but it’s so obviously helpful for third-party event tools/apps that it might be worth adding anyway? A question that arises in that case is if the data is too granular and time-sensitive for editors to add reliably (e.g. too many fields, not enough event editors), is it worth having at all? If it’s okay for it to be sometimes accurate, sometimes not, then it might be worth adding.