Vocab:InclusionSize
Vocab:InclusionSize node definition.
Description
Nodes with both the "Vocab" and "InclusionSize" labels, defining approved terms for the AVERAGE size/fragmentation of the material included in a DEPOSIT ( :Place:Context )). Terms are derived from those commonly used by UJAP and other archaeological projects. 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
"flecks", "small fragments", "medium fragments", "large fragments", "very large fragments", "unfragmented"
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 InclusionSize but not necessarily across all Vocab nodes. | "medium fragments" |
| description | string | Y | n | Short description of the InclusionSize vocab term recorded by this node. Will almost certainly be unique, but this is not enforced. | "Diameter or longest measured dimension of individual particles measures between 20–60mm." |
| referenceURI | string | n | n | Where 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)
| 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:InclusionSize ) ——[:RELATE]——> ( :Node2 )
Relationships (incoming)
( :Node2 ) ——[:RELATE]——> ( :Vocab:InclusionSize )