HAS_WORKED_IN Party Data
Description
Connects a :Party of client to a :Location.
This relationship is used to indicate where a client has worked. It is similar to BASED_IN. Note that this location is distinct from a client's physical address. Parties can have multiple bases. Example below shows a client that has worked in both London and Los Angeles.
Label
:HAS_WORKED_IN
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Party A node of type :Party with an active HAS_ROLE relationship to a :Role { name: "Client"} node | HAS_WORKED_IN | Location A node with the :Location label | 0..n |
Properties
HAS_WORKED_IN uses the standard relationship properties.
CREATE
A home base requires the specification of a locality along with its associated region (if available), and country. There is no limit to the number of active locations a data node can have.
If the relationship property active is true, and the locality, region, and country are exactly the same as an existing location, then the request is REJECTED.
UPDATE
Updates to the :Location node relationship are not allowed. To update a location, deactivate the existing relationship using DELETE and create a new :Location node and relationship.
DELETE
Deleting a :Location node relationship is a deactivation. No physical deletes will happen.