Skip to main content

Thing:Pail

 Thing:Pail  node definition.

Description

Nodes with both the "Thing" and "Pail" labels, representing the temporary aggregate collection of materials from a discrete FieldworkProcess within a discrete Context (e.g., a "pottery pail" or "pottery bucket" that was collected in Context UJ.U.10.034 on the morning of 3 June 2024), and to which non-pottery finds from the same Context and collection activity are associated. "Pails" are an important part of the archaeological retrieval and recording process, establishing a close relationship between finds. Some materials will later be separated from their Pail for permanent curation, etc., but this initial aggregate collection is essential to archaeological interpretation. Represented in visualizations by HTML hex color #495057:  Thing:Pail  with white (#FFFFFF) label text.

Analogy

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

Example

"UJAP.2024.Pail.098"

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 “pail-”"pail-ujap-2024-098"
namestringYYUnique name by which this Pail is known in the database."UJAP.2024.Pail.098"
descriptionstringYnShort description of the Pail recorded by this node. Will almost certainly be unique, but this is not enforced."Pail 098 from UJAP.2024 FieldSeason, collected on 22 May 2024 from Context UJ.U.10.034"

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)
------

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:Pail  )

——[:HAS_NOTE]——>

 :Thing:Note  )

Relationships (incoming)

 :Thing:Note  )

——[:HAS_NOTE]——>

 :Thing:Pail  )