LOCATED_IN Party Data
Description
Connects a data node, such as :Party, :EventSeries or :EventInstance, to a :Location.
Label
:LOCATED_IN
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Party A node with the :Party label | LOCATED_IN | Location A node with the :Location label | 0..n |
| Party A node with the :EventSeries label | LOCATED_IN | Location A node with the :Location label | 1..n |
| Party A node with the :EventInstance label | LOCATED_IN | Location A node with the :Location label | 1..n |
Properties
LOCATED_IN uses the standard relationship properties.
CREATE
If the relationship property active is true, and the latitude and longitude are exactly the same as an existing active :Location for this party, then the request is rejected with a 409 status code.
There is no limit to the number of active locations a data node can have.
In the context of an :EventInstance, an instance must have an active LOCATED_IN relationship with a :Location node. This is independent of the instance having an active HAPPENS_AT relationship with a venue. The active LOCATED_IN relationship must connect with a location that includes a locality along with either a region or country.
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.