HAS_PHONE Party Data
Description
Connects a :Party, :Venue, or :EventSeries to a :Phone.
Label
:HAS_PHONE
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Party A node with the :Party label | HAS_PHONE | Phone A node with the :Phone label | 0..n |
| EventSeries A node with the :EventSeries label | HAS_PHONE | Phone A node with the :Phone label | 0..n |
| Venue A node with the :Venue label | HAS_PHONE | Phone A node with the :Phone label | 0..n |
Properties
HAS_PHONE uses the standard relationship properties.
CREATE
All :Phone nodes have a primary property. There can be one and only one active primary phone number for a given type attached to a party. It is acceptable that a party may have multiple phone numbers of one type with none specifically being marked as primary.
If property primary is true, and the relationship property active is true, then all other active and primary phones of the same type must have the primary property set to false. If no prior phone number exists for a given type, then the first phone number created for that type must have primary set to true.
If the relationship property active is true, and the type, number, and extension are exactly the same as an existing active phone for this party, then the request is REJECTED. It is acceptable to have the same number and extension assigned to a different type. For example, this could be used to indicate the a "Mobile" number for a party is the same as the party's "Home" number.
There is no limit to the number of active phones in any type.
UPDATE
Most updates to existing phone numbers should be REJECTED in favor of deactivation and create flow as described above, so as to preserve the history of changes. To update a phone, deactivate the existing relatipnship and create a new :Phone node and active relatinship.
However, there are some situations where we will need to change a phone number on an existing :Phone node because of typographic error and where holding on to the original phone number would not be appropriate. In all cases before, the only properties that may be changed are number and extension and the API update operation should be limited to data management (DMO) personnel. If updating a phone and/or extension of any type, the ACID transaction be to update phone and/or entension, and modified properties.
DELETE
For phone numbers, the DELETE verb corresponds to deactivating the relationship between the party and the :Phone node. No physical deletes will happen.