Vocab:Dimension
Vocab:Dimension node definition.
Description
Nodes with both the "Vocab" and "Dimension" labels, defining approved terms for measurable dimensions (e.g., distance, area, weight) that may be recorded for ( :Place ) or ( :Thing ) node entities. Terms are derived from those used by UJAP, many other archaeological field projects, and the Getty Art & Architecture Thesaurus, using a subset that currently includes a range of relevant options. Additional terms may only be added to this controlled vocabulary by database administrators.
Vocab nodes are usually not displayed in graph visualizations but if they do, will appear with a white (#FFFFFF) background with black (#000000) text, regardless of the node label.
Analogy
A list of approved terms that are used to populate drop-down menu items to constrain user input to only specifically approved options that have an established meaning. These may be stored in a spreadsheet or relational database table but are often implemented in application logic.
Example
"area", "capacity", "count", "depth", "diameter", "height", "length", "volume", "weight", "width"
CIDOC-CRM Mapping
MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.
Node Properties
Basic Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| term | string | Y | Y | The approved term/name for this vocabulary item which will appear in dropdown selections, etc. Term must be UNIQUE for Dimension but not necessarily across all Vocab nodes. | "length" |
| description | string | Y | n | Short description of the Dimension vocab term recorded by this node. Will almost certainly be unique, but this is not enforced. | "brief description here" |
| referenceURI | string | n | n | Where relevant, the URI for this term in an external thesaurus or taxonomy from which it is derived. | "http://vocab.getty.edu/page/aat/300055645" |
System/Audit Properties
(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" |
Relationships (outgoing)
( :Vocab:Dimension ) ——[:RELATE]——> ( :Node2 )
Relationships (incoming)
( :Place:Context ) ——[:HAS_DIMENSION]——> ( :Vocab:Dimension )