HAS_SUBVENUE Party Data
Description
Relates multiple venues located within a larger property or facility. For example, the Tennessee Performing Arts Center (TPAC) is made of three venues: Johnson, Jackson and Polk Theaters. The TPAC Party would connect to each of these theaters using the HAS_SUBVENUE relationship.
See here for more information.
Label
:HAS_SUBVENUE
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Venue A node with the :Venue label | HAS_SUBVENUE | Venue A node with the :Venue label | 0..n |
Properties
HAS_SUBVENUE uses the standard relationship properties.
CREATE
A :Venue can have multiple HAS_SUBVENUE relationships.
A :Venue can only be the subvenue of one :Venue. Attempts to set a :Venue with more than one parent :Venue will be REJECTED.
Once a :Venue is a subvenue, it cannot be a parent of another :Venue. Attempts to make a child :Venue the parent of another will be REJECTED.
A parent :Venue is a general name for a group of independently booked subvenues. The parent venue is not a bookable venue in and of itself. Because of this, the parent :Venue cannot have any seating configurations attached to it. Attempts to set a :Venue with active HAS_CONFIGURATION relationships will be REJECTED
The establishment of subvenue relationships should be restricted to DMO personnel only.
UPDATE
Updates to :Venue subvenue relationship are not allowed. To update a subvenue relationship, deactivate the existing relationship and create a new HAS_SUBVENUE relationship.
DELETE
Deleting a :Venue subvenue relationship is a deactivation. No physical deletes will happen.