HAS_CONFIGURATION Party Data
Description
Connects a :Venue to a :Configuration.
See Venues for more information.
Label
:HAS_CONFIGURATION
Valid nodes
| From | Relationship | To |
|---|---|---|
| Venue A node with the :Venue label | HAS_CONFIGURATION | Configuration A node with the :Configuration label |
| StageInstance A node with the :StageInstance label | HAS_CONFIGURATION | Configuration A node with the :Configuration label |
Properties
HAS_CONFIGURATION uses the standard relationship properties.
CREATE
A :Venue bookable node must have at least one :Configuration connected via the HAS_CONFIGURATION relationship. This relationship specifies the default configuration for a venue. Venues can have multiple configurations depending on the differ capacity and indoor/outdoor configurations offered at a venue.
UPDATE
Updating the bookable property of a :Venue to FALSE will also trigger the deactivation of any active HAS_CONFIGURATION relationships connected to that venue. In addition, if a venue is unbookable, any attempts to create a new HAS_CONFIGURATION relationship will be REJECTED.
Updates to a :Configuration node relationship are not allowed. To update a configuration, deactivate the existing relationship using DELETE and create a new :Configuration node and relationship.
There may be some instances where information within a configuration node will need to be updated, but that action should be left only to DMO personnel.
DELETE
Deleting a :Configuration node relationship is a deactivation. No physical deletes will happen.