HAS_PHYSICAL_RELATE_TO
HAS_PHYSICAL_RELATE_TO edge/relationship definition.
Description
Connects a ( :Place:Context ) node to another ( :Place:Context ) node to record a physical relationship between the two Contexts. NOTE: stratigraphic relationships between Contexts are separately handled, but physical relationships are an essential element in determining the stratigraphic sequence. NOTE: the direction of this edge is particularly important, as PhysicalRelateType terms are communicated with particular semantic meaning "e.g., "laid on" means one thing when read in one direction, but would be understood as "overlaid by" in the opposite direction.
Analogy
Join row(s) or table(s) linking Contexts to Contexts, with necessary properties to further define details of the relationship.
CIDOC-CRM Mapping
MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.
Relevant Nodes, Directions, and Cardinality
[ :Place:Context ] ——[ :HAS_PHYSICAL_RELATE_TO ]——> @[0..*] [ :Place:Context ] ⟵ @[0..*]
- Each Context may be physically related to zero or many other Contexts, in both directions.
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| type | string | Y | n | The type of physical relationship, selected from options in ( :Vocab:PhysicalRelateType ). | "laid against" |
| boundary | string | n | n | The observable clarity of the boundary/horizon between these two contexts, selected from options in ( :Vocab:ContextBoundary ). | "diffuse" |
| confidence | string | Y | n | Confidence level for asserted physical relationship, selected from options defined in the ( :Vocab:Confidence ) controlled vocabulary. | "moderate" |
POSSIBLE: System/Audit Properties
Need to decide if we should include the full (or a partial) audit trail for edge/relationships. I'm leaning toward YES.(these are not required/enforced by Neo4j but are populated via the UJAP Database web application; these could also be handled—perhaps more simply—by edge/relationship to AuditEvent nodes)
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| proposedAt | datetime | n | n | Timestamp of entity proposal (initial database record creation) | "2026-01-30T02:39:15.638Z" |
| proposedBy | string | n | n | Email or userID of the person who created this entity's initial/proposed record | "person@email.com" |
| approvedAt | datetime | n | n | Timestamp of entity proposal (initial database record creation) | "2026-01-30T12:47:15.638Z" |
| approvedBy | string | n | n | Email or userID of the person who created this entity's initial/proposed record | "person@email.com" |
| committedAt | datetime | n | n | of node entity COMMIT (i.e., formal approval/ publishing to database by an admin). | "2026-01-31T02:41:56.043Z" |
| committedBy | string | n | n | Email or userID of the person who COMMITTED this node entity. | "person@email.com" |
Example Visualization
Insert visualization here, drawn in Arrows.app and using the correct color-coding.