Skip to main content

Vocab:MasonryTechnique

Vocab:MasonryTechnique node definition.

Description

Nodes with both the "Vocab" and "MasonryTechnique" labels, defining approved terms for a range of techniques that are used in architectural masonry structures. Terms are derived from those used by UJAP, many other archaeological 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

"Battered Wall", "Bench Tables", "Corbels", "Interlocking Stones", "Quoins", "String Courses"

CIDOC-CRM Mapping

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

Node Properties

Basic Properties

propertytypereq?uniq?descriptionexample(s)
------
termstringYYThe approved term/name for this vocabulary item which will appear in dropdown selections, etc. Term must be UNIQUE for MasonryTechnique but not necessarily across all Vocab nodes."battered wall"
descriptionstringYnShort description of the MasonryTechnique vocab term recorded by this node. Will almost certainly be unique, but this is not enforced."Wall construction where the wall inclines or slopes inward as it rises; narrower at the top than the bottom."
referenceURIstringnnWhere relevant, the URI for this term in an external thesaurus or taxonomy from which it is derived."http://vocab.getty.edu/page/aat/300002472"

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)

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"
THE FOLLOWING RELATIONSHIPS REQUIRE ATTENTION/EDITING!

Relationships (outgoing)

(  :Vocab:MasonryTechnique  ) ——[:RELATE]——> (  :Node2  )

Relationships (incoming)

(  :Node2  ) ——[:RELATE]——> (  :Vocab:MasonryTechnique  )