HAS_NOTE

HAS_NOTE edge/relationship definition.

Description

Connects nodes of all types to a (  :Thing:Note  ) node in order to record additional information not covered by other nodes, edges, or properties.

Analogy

Join row(s), column(s) or table(s) linking various nodes to Notes.

CIDOC-CRM Mapping

MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.

Relevant Nodes, Directions, and Cardinality

[  Node1  ] ——[ :HAS_NOTE ]——> @[0..*] [   :Thing:Note   ] ⟵ @[0..*]

• Each node may have zero or many Notes.
• Each Note may be related to zero or many other nodes.

Edge/Relationship Properties

property	type	req?	uniq?	description	example(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)

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.