Configuration
Description
Venues can be arranged to have different configurations that will alter the capactity for a specific event. Configuration is used to store the name reference to a configuration and its associated capacity. Example configurations for venues could include standing vs seating, line of sight seating arrangements (160°, 180°, 220° views), or traditional stages vs in-the-round stages.
Label
:Configuration
Properties
| Property | Description | Type |
|---|---|---|
| id | The tag's unique identifier (uuid) | string |
| name | The name of a configuration | string |
| capacity | The capactity associated with a configuration | number |
| outdoor | TRUE if configuration can be outdoor, FALSE is indoor | boolean |
| primary | Whether this is the "primary" configuration | boolean |
| createdBy | the person or process that created the node | string |
| createdDate | dateTime | |
| modifiedBy | the person or process who last modified the node | string |
| modifiedDate | dateTime |
Configurations with primary=True are considered as the "default" capacity indication for the venue. Primary Configurations are not expected to have a name, and any name property would be managed by the API.
Key
id
Relationships
The HAS_CONFIGURATION relationship connects a :Venue node to :Configuration nodes