Skip to main content

Thing:Collection

 Thing:Collection  node definition.

Description

Nodes with both the "Thing" and "Collection" labels, representing multiples of Things that are assembled/curated together for study, display, or storage, as in the holdings of an archive or museum, a teaching or study collection, etc. This node refers to the Collection itself and not to its constituent items, holders, or responsible parties (these are all handled by relationships). Collections may be long-term or temporary and individual collection items may be added and/or removed over time. They may represent items that are all of a similar type (e.g., African Red Slip pottery sherds) or may be mixed (Artifacts, Ecofacts, MediaFiles, etc.). Represented in visualizations by HTML hex color #E76F51:  Thing:Collection  with white (#FFFFFF) label text.

Analogy

A row in a "Collections" spreadsheet or relational database table.

Example

"UJAP Ceramic Teaching Collection", "Umm Al-Jimal Interpretive Centre Exhibit 001"

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)
------
uidstringYYUnique identifier as alphanumeric slug, prepended with “collect-”"collect-ujap-ceramic-teaching"
namestringYYUnique name by which this Collection is known in the database."UJAP Ceramic Teaching Collection"
descriptionstringYnShort description of the Collection recorded by this node. Will almost certainly be unique, but this is not enforced."Ceramic teaching collection, featuring examples of pottery types across all periods at Umm Al-Jimal, Jordan"

TENTATIVE Properties

(these may be changed to edge/relationships with Vocab terms or XX nodes, rather than directly stored as node properties)

propertytypereq?uniq?descriptionexample(s)
------
typestringnnThe type of Collection recorded by this node entity, selected from the Vocab:CollectionType controlled vocabulary."teaching collection"

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)

 :Thing:Collection  )

——[:HAS_NOTE]——>

 :Thing:Note  )

Relationships (incoming)

 :Thing:Note  )

——[:HAS_NOTE]——>

 :Thing:Collection  )