OBSERVED_COURSES
OBSERVED_COURSES edge/relationship definition.
Description
Connects an ( :Activity ) node to an ARCHITECTURAL ( :Place:Context ) node to record that this Activity observed/recorded surviving masonry courses for this architectural context.
Analogy
Join row(s) or table(s) linking Activities to the observation of an ARCHITECTURAL Context's surviving courses.
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_COURSES ]——> @[0..*] [ :Place:Context ] ⟵ @[0..*]
- Each FieldworkProcess may observe the masonry courses of zero or many Architectural Contexts.
- Each Context may have multiple masonry course observations by different FieldworkProcess activities.
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| complete | integer | n | n | The number of complete courses observed in this architectural context, as an integer. | 3 |
| partial | integer | n | n | The number of partial/incomplete courses observed in this architectural context, as an integer. | 2 |
| confidence | string | Y | n | Confidence level in this masonry course observation, selected from options in ( :Vocab:Confidence ). | "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.