HAS_ONLINE_ADDRESS Party Data
Description
Connects a :Party, :Venue or :EventSeries to an :OnlineAddress
Label
:HAS_ONLINE_ADDRESS
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Party A node with the :Party label | HAS_ONLINE_ADDRESS | Online Address A node with the :OnlineAddress label | 0..n |
| Venue A node with the :Venue label | HAS_ONLINE_ADDRESS | Online Address A node with the :OnlineAddress label | 0..n |
| EventSeries A node with the :EventSeries label | HAS_ONLINE_ADDRESS | Online Address A node with the :OnlineAddress label | 0..n |
| EventInstance A node with the :EventInstance label | HAS_ONLINE_ADDRESS | Online Address A node with the :OnlineAddress label | 0..n |
Properties
HAS_ONLINE_ADDRESS uses the standard relationship properties.
CREATE
All :OnlineAddress nodes have a primary property. There can be one and only one active primary online address for a given type attached to a party.
If property primary is true, and the relationship property active is true, then all other active and primary online addresses of the same type must have the primary property set to false.
If the relationship property active is true, and the address and type properties are exactly the same as an existing active online address property for this party, then the request is rejected with a 409 status code.
There is no limit to the number of active online addresses in any type, but as stated earlier, only one can be primary in any given type.
UPDATE
Updates to the :OnlineAddress node relationship are not allowed. To update a phone, deactivate the existing relationship using DELETE and create a new :OnlineAddress node and relationship.
DELETE
Deleting an :OnlineAddress node relationship is a deactivation. No physical deletes will happen.
If deactivating the relationship would result in no active primary online address of the deleted online address's type, then the request is rejected with a 400 status code. The client must first activate another online address of the same type.