DEFINED_GEOLOCATION
DEFINED_GEOLOCATION edge/relationship definition.
Description
Connects an ( :Activity:FieldworkProcess ) or ( :Activity:LabProcess ) node to a ( :Place:Geolocation ) node to record that the GeoLocation was defined by/during this activity.
Analogy
Join row(s) or table(s) linking Activities to the geospatial locations that they measured/defined.
CIDOC-CRM Mapping
MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.
Relevant Nodes, Directions, and Cardinality
[ :Activity:FieldworkProcess | :Activity:LabProcess ] ——[ :DEFINED_GEOLOCATION ]——> @[1] [ :Place:Geolocation ] ⟵ @[0..*]
- Each FieldworkProcess or LabProcess Activity may define zero or many GeoLocations.
- Each GeoLocation must be defined in only ONE FieldworkProcess or LabProcess Activity.
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| method | [string list] | n | n | Record the method(s) used to measure this geospatial location as a string array, selected from the ( :Vocab:MeasureMethod ) controlled vocabulary. | ["hand measurement", "optical measurement"] |
| tool | [string list] | n | n | Record the tool(s) used to measure this geospatial location as a string array, selected from the ( :Vocab:MeasureTool ) controlled vocabulary. | ["tape measure", "dumpy level"] |
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.