Skip to main content

Thing:Artifact

 Thing:Artifact  node definition.

Description

Nodes with both the "Thing" and "Artifact" labels, representing physical and relatively portable human-made (or human-modified) objects. Represented in visualizations by HTML hex color #3A86FF:  Thing:Artifact  with white (#FFFFFF) label text.

Analogy

A row in an "Artifacts" spreadsheet or relational database table.

Example

"Coin of Marcus Aurelius", "Glass bangle fragment", "Metal (iron) tool fragment"

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 “artifact-”"artifact-ujap-2024-034"
namestringYYUnique name by which this Artifact is known in the database."UJAP.2024.Artifact.034"
descriptionstringYnShort description of the Artifact recorded by this node. Will almost certainly be unique, but this is not enforced."Coin of Marcus Aurelius"

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 Artifact recorded by this node entity, selected from the Vocab:ArtifactType controlled vocabulary."coin"
periodProduction[string list]nnWhenever possible, an informed determination of the cultural period(s) in which this Artifact was produced, selected from choices in Vocab:CulturalPeriod as a string array.["Late Roman", "Early Byzantine"]
dateProductionEarlieststring (edtf)nnWhenever possible, an informed determination of the earliest reasonably possible date for the production of this Artifact, in extended date-time format (level 0/1 supported)."0300" for AD 300
dateProductionLateststring (edtf)nnWhenever possible, an informed determination of the latest reasonably possible date for the production of this Artifact, in extended date-time format (level 0/1 supported)."0600" for AD 600

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

——[:HAS_NOTE]——>

 :Thing:Note  )

Relationships (incoming)

 :Thing:Note  )

——[:HAS_NOTE]——>

 :Thing:Artifact  )