HAS_PARENT_TERM
HAS_PARENT_TERM edge/relationship definition.
Description
Connects a ( :Vocab ) node to another ( :Vocab ) node to record a nested/hierarchical relationship between the two controlled vocabulary terms.
Analogy
Join row(s), column(s), or table(s) defining hierarchical relationships between vocabulary terms.
CIDOC-CRM Mapping
MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.
Relevant Nodes, Directions, and Cardinality
[ :Vocab ] ——[ :HAS_PARENT_TERM ]——> @[0..*] [ :Vocab ] ⟵ @[0..*]
- Each Vocab term may have zero or many parent terms.
- Each Vocab term may be the parent of zero or many other Vocab terms.
- NOTE: This relationship is NEVER applied to the "Vocab" label only, but ALWAYS to label pairs (e.g., "Vocab:MediaType")
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
There are no basic properties for this relationship, unless we decide to include the following audit properties:
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.