Activity:Sampling

Activity:Sampling node definition.

Description

Nodes with both the "Activity" and "Sampling" labels, representing an individual sample-taking activity, which may have occurred in or out of the field, from contexts, artifact, ecofacts, or other samples. "Sampling" activities may take place during a "FieldSeaon" activity or separate from a FieldSeason, and may be composed of multiple sub-sampling or lab processes. Represented in visualizations by HTML hex color #386641: Activity:Sampling with white (#FFFFFF) label text.

Analogy

Sampling (or sample-taking) activities are rarely documented explicitly, but the samples themselves are, usually in a "Samples" spreadsheet or relational database table, or as a column in a "Contexts" spreadsheet or table. The Sampling activity is, therefore, usually inferred rather than explicitly recorded.

Example

We need to develop a coherent, consistent, and logical naming scheme. Collection of a soil sample (e.g., "UJAP.2024.Sample.077") from a deposit context (e.g., "UJ.U.10.034") during excavation of that context.

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)
-	-	-	-	-	-
uid	string	Y	Y	Unique identifier as alphanumeric slug, prepended with “samp-”	"samp-ujap-2024-077"
name	string	Y	Y	Unique name by which this Sampling is known in the database.	"UJAP.2024.Sample.077"
description	string	Y	n	Short description of the Sampling activity recorded by this node. Will almost certainly be unique, but this is not enforced.	"Sampling of soil from Context UJ.U.10.034"
dateStart	string (edtf)	n	n	Where relevant and available, the date this activity began, as precisely as possible, in extended date-time format (level 0/1 supported).	"2024-05-17"
dateEnd	string (edtf)	n	n	Where relevant and available, the date this activity ended, as precisely as possible, in extended date-time format (level 0/1 supported).	"2024-05-17"

TENTATIVE Properties

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

property	type	req?	uniq?	description	example(s)
-	-	-	-	-	-
method	[string list]	n	n	A list of general methods used in this Sampling activity, as a string array. Values are selected from the Vocab:MethodType controlled vocabulary	["method1," "method2"]
tool	[string list]	n	n	A list of general tools/equipment used in this Sampling activity, as a string array. Values are selected from the Vocab:ToolType controlled vocabulary.	["tool1", "tool2", "tool3"]
conditions	[string list]	n	n	A list of conditions under which this Sampling activity took place, as a string array. Values are selected from the Vocab:ActivityConditions controlled vocabulary.	["condition1", "condition2"]

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"