OBSERVED_DIMENSION
OBSERVED_DIMENSION edge/relationship definition.
Description
Connects an ( :Activity ) node to an ARCHITECTURAL or CUT ( :Place:Context ) node to record that this Activity observed/recorded a dimensional measurement for this Context.
Analogy
Join row(s) or table(s) linking Activities to the observation of a Context's measured dimension(s).
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 ] ——[ :OBSERVED_DIMENSION ]——> @[0..*] [ :Place:Context ] ⟵ @[0..*]
- Each FieldworkProcess may observe zero or many dimensions for zero or many Contexts.
- Each Context may have multiple dimension observations by the same or different FieldworkProcess activities.
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| dimension | string | Y | n | The specific dimension recorded by this observation, selected from options in Vocab:Dimension. | "length" |
| value | float | Y | n | A numerical value for the measurement of this dimension, in terms of the unit defined in the next property, to two decimal points. | 3.23 |
| unit | string | Y | n | The unit of measurement for the recorded value, selected from options defined in the ( :Vocab:MeasureUnit ) controlled vocabulary. | "meters" |
| method | [string list] | n | n | Record the method(s) used to measure this dimension as a string array, selected from the ( :Vocab:MeasureMethod ) controlled vocabulary. | ["hand measurement", "second method"] |
| tool | [string list] | n | n | Record the tool(s) used to measure this dimension as a string array, selected from the ( :Vocab:MeasureTool ) controlled vocabulary. | ["tape measure", "second tool"] |
| confidence | string | Y | n | Confidence level for this dimension measurement, 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.