Skip to main content

HAS_CONTEXT_TYPE

HAS_CONTEXT_TYPE edge/relationship definition.

Description

Connects a (  :Place:Context  ) node to a ( :Vocab:ContextType ) node to record the type of Context recorded by this node entity, selected from choices in Vocab:ContextType.

Analogy

"Type" column in "Context" table or join row(s), column(s), or table(s) defining relationship between a Context and a ContextType.

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_CONTEXT_TYPE ]——> @[1] [  :Vocab:ContextType  ] ⟵ @[0..*]

  • Each Context must have ONE ContextType.
  • Each FormationType may be related to zero or many Contexts.

Edge/Relationship Properties

propertytypereq?uniq?descriptionexample(s)
------

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)

propertytypereq?uniq?descriptionexample(s)
proposedAtdatetimennTimestamp of entity proposal (initial database record creation)"2026-01-30T02:39:15.638Z"
proposedBystringnnEmail or userID of the person who created this entity's initial/proposed record"person@email.com"
approvedAtdatetimennTimestamp of entity proposal (initial database record creation)"2026-01-30T12:47:15.638Z"
approvedBystringnnEmail or userID of the person who created this entity's initial/proposed record"person@email.com"
committedAtdatetimennof node entity COMMIT (i.e., formal approval/ publishing to database by an admin)."2026-01-31T02:41:56.043Z"
committedBystringnnEmail 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.