Skip to main content

Vocab:Color

Vocab:Color node definition.

Description

Nodes with both the "Vocab" and "Color" labels, defining approved terms for different colors recorded for a wide variety of (  :Thing  ) nodes. Different edges will be used to connect different types of Things with their relevant color(s), e.g. [:HAS_DEPOSIT_COLOR] connects DEPOSIT (  :Place:Context  ) to the relevant Color node. Terms are derived from the MUNSELL Soil Color Book and a Modifier+Hue+Color (e.g., "dark reddish brown") system used by many archaeological projects as an alternative to MUNSELL notation. 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

"brown" (color only), "reddish brown" (hue + color), "dark brown" (modifier + color), "dark reddish brown" (modifier + hue + color), "7.5YR 5/3" (MUNSELL notation for one of several "brown" colors)

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 Color but not necessarily across all Vocab nodes."reddish brown", "7.5YR 5/3"
descriptionstringYnShort description of the Color vocab term recorded by this node. Will almost certainly be unique, but this is not enforced."dark reddish brown", "brown"
referenceURIstringnnWhere relevant, the URI for this term in an external thesaurus or taxonomy from which it is derived."URI to external source here"

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:Color  ) ——[:RELATE]——> (  :Node2  )

Relationships (incoming)

 :Place:Context  ) ——[:HAS_COLOR]——> (  :Vocab:Color  )