CARRIED_OUT_BY
CARRIED_OUT_BY edge/relationship definition.
Description
Connects an ( :Activity ) node to an ( :Actor ) node to record that this Activity was carried out by this Actor (with optional role and date properties).
Analogy
Join row(s) or table(s) linking Activities to their responsible Actors.
CIDOC-CRM Mapping
MAYBE include a short summmary here, but leave the details for the designated CIDOC-CRM section.
Relevant Nodes, Directions, and Cardinality
[ :Activity:FieldSeason | :Activity:FieldworkProcess | :Activity:LabProcess | :Activity:Sampling ] ——[ :CARRIED_OUT_BY ]——> @[1..*] [ :Actor:Group | :Actor:Person ] ⟵ @[0..*]
- Each Activity must be carried out by at least one Actor (but can be carried out by many Actors).
- Actors may be Groups, People, or a mix, with separate CARRIED_OUT_BY edges pointing to the relevant Actors.
- Each Actor may carry out zero or many Activities.
- Multiple CARRIED_OUT_BY relationships may exist between the same source and target nodes, provided they differ by property values (e.g., role).
Edge/Relationship Properties
| property | type | req? | uniq? | description | example(s) |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| role | string | n | n | The role that this specific actor played in the performance of this specific activity, selected from the Vocab:ActivityRole controlled vocabulary. | "licensing authority" |
| dateStart | string (edtf) | n | n | Where relevant and available, the date this activity role began, as precise as possible, in extended date-time format (level 0/1 supported). | "2022-05-01" |
| dateEnd | string (edtf) | n | n | Where relevant and available, the date this activity role ended, as precise as possible, in extended date-time format (level 0/1 supported). | "2022-06-10" |
POSSIBLE: System/Audit Properties
Need to decide if we should include the full (or a partial) audit trail for edge/relationships. I'm leaning toward YES.(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" |
Example Visualization
Insert visualization here, drawn in Arrows.app and using the correct color-coding.