Project

General

Profile

Actions

Feature #1500

closed

Production of artifacts

Added by Bernhard Koschiček-Krombholz almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Backend
Target version:
Start date:
2021-04-16
Estimated time:
8.00 h

Description

Update

This feature allows to create events (production) for the creation of artifacts and also track their creators. Model mapping:
E12 (Production) -> P14 (carried out by) -> Actor
E12 (Production) -> P108 (has produced) -> E22 (human made object)
Information about how to use this will be added to the manual before the release.

Original issue text

An artifact is, like the name Man-Made-Object tell us, produced, created and modify by a human being or a group. For tracking the origin and history of an artifact, it is relevant who created which object at what time and where. The same questions arise with a modification.
For example a prayer book is often created by a priest, monk etc. when a new church, monastery etc. was established. This book was inherited by the successor, which often create side marks/annotations or maybe also erase whole pages, which can and should be tracked.
Same use case arise for art, like paintings, icons, busts, objects of prayer, small shrines etc. Even if we don't know the real creator, it would be useful, who gave, when and where, the order to create it (which is in most historical cases more important than the creator itself). This can be very important, because it can be a sign of political power display, religious appreciation, transformation or conflict.
Or, if graffiti is classified as E22, it is very important to know, who created, when which graffiti, and who modified it.

I can gladly give more examples if needed.

I think some projects will benefit from a new event, where the creation and modification of an artifact can have a creator/donor/contractor, timestamp of the creation/modification and place of origin. Additionally, would anything discussed in ticket #1462 also be very beneficial.

So my question is, can and will this be done? The CIDOC CRM mapping should support this quite good in several way.
In my humble opinion an event E12 Production with P108 has produced (was produced by) and E11 Modification and P31 has modified (was modified by) would be useful for that. But surely, there is a way to include everything in E7 Activity, since it is the super class and play it which types (which would be not so beautiful in my opinion).

I hope I could state my point.


Related issues 1 (0 open1 closed)

Related to OpenAtlas - Feature #1462: Current owner of artifactsClosedAlexander Watzinger2021-02-11Actions
Actions #1

Updated by Alexander Watzinger almost 3 years ago

@ Berni: it would be important to know why you would need this. A date can already be tracked (begin time span) so what else do you need? E.g. to add a creator, connect the place of the creation, ...?

Actions #2

Updated by Bernhard Koschiček-Krombholz almost 3 years ago

  • Description updated (diff)

Changed description. I hope, this is now suitable to discuss.

Actions #3

Updated by Bernhard Koschiček-Krombholz almost 3 years ago

Actions #4

Updated by Alexander Watzinger almost 3 years ago

  • Tracker changed from Question to Feature
  • Description updated (diff)
  • Category set to Backend
  • Status changed from New to Acknowledged

Thank you very much Berni for the detailed description. I too think it's possible to cover described features with CIDOC CRM and updated this issue from question to acknowledged feature.
I suggest to concentrate on the creation of artifacts, once we have done this we can think about other aspects which are still not covered (e.g. later modification of an artifact) in another issue.

To summarize:
We need an (additional) event class to enter the creation of an artifact and it should be possible to:
  • Link the artifact which was created
  • Link actors as creators
  • Link a place of creation

Dates would be covered by the event itself, please note if I missed something regarding the creation of an artifact.
This issue would be a good topic for the next team meeting and as always, it would be nice if Stefan can take a look at the modelling aspect.

Actions #5

Updated by Stefan Eichert almost 3 years ago

Hi Berni!
Is this what you were thinking of:
https://redmine.openatlas.eu/projects/uni/wiki/CIDOC-Mappings
https://redmine.openatlas.eu/attachments/download/111/source_physical.png

Here it is mapped for information carrier (which will anyway be turned into "Human Made Object" - the new man made object in the new CIDOC CRM)

Actions #6

Updated by Bernhard Koschiček-Krombholz almost 3 years ago

Hi Stefan!
This is exactly what I'm thinking of.

Actions #7

Updated by Bernhard Koschiček-Krombholz almost 3 years ago

  • Description updated (diff)
Actions #8

Updated by Alexander Watzinger almost 3 years ago

  • Assignee deleted (Stefan Eichert)

Thank you Stefan for feedback and Berni for reporting. I think we have enough information for now and can discuss it in more detail in the next team meeting.

Actions #9

Updated by Alexander Watzinger almost 3 years ago

  • Target version changed from Wishlist to 7.4.0
Actions #10

Updated by Alexander Watzinger almost 3 years ago

  • Description updated (diff)
  • Status changed from Acknowledged to In Progress
  • Assignee set to Stefan Eichert
  • Target version changed from 7.4.0 to 7.1.0
As discussed in yesterdays developer meeting: move this issue up in roadmap and assigning to Stefan.
@ Stefan: you already did quite a lot modelling preparation but maybe you could specify here the basic model relation. We would need links between:
  • actor: I would guess person but also group
  • event: a new creation event class?
  • artifact
  • do we need a new one for graffiti (INDIGO) or would artifact suffice?
Actions #11

Updated by Alexander Watzinger over 2 years ago

  • Target version changed from 7.1.0 to 252

Moved this issue to the INDIGO roadmap because we will need it there too.

Actions #12

Updated by Alexander Watzinger over 2 years ago

  • Target version changed from 252 to 6.6.0
Actions #13

Updated by Alexander Watzinger over 2 years ago

After discussing it with Stefan we decided to implement it similar to activity; E12 (Production) -> P108 (has produced) -> E22 (human made object).
It will have the same links like activity e.g. P7 -> E53 for place.

Actions #14

Updated by Alexander Watzinger over 2 years ago

  • Assignee changed from Stefan Eichert to Alexander Watzinger
Actions #15

Updated by Alexander Watzinger over 2 years ago

Just working on this and small question in the round: I would give production the same standard type (Event) as for all others at the moment (activity, move, acquisition).
Just asking because this is something that can't be changed in the application later (because it's a standard type) and changing it later with an upgrade SQL would raise questions what to do with existing links.
However, in case I hear nothing I will just proceed with it and let production share the Event type with the other event sub classes.

Actions #16

Updated by Alexander Watzinger over 2 years ago

  • Estimated time set to 8.00 h
Actions #17

Updated by Alexander Watzinger over 2 years ago

The creator(s) will be connected directly in the new/edit production form.
The relation will be E12 (Production) -> P14 (carried out by) -> Actor
Additionally, other participants can be added in the actor tab the like with other events.

Actions #18

Updated by Alexander Watzinger over 2 years ago

  • Subject changed from Creation of artifacts to Production of artifacts
  • Description updated (diff)
  • Status changed from In Progress to Closed

Minor change in the implementation:
When viewing a production, actors can be added via the actor tab (not directly in the production form) because we already use this workflow for activity, acquisition and move.
And the other way round, so when viewing an actor a production event can be added/linked via the event tab.

Actions #19

Updated by Alexander Watzinger over 2 years ago

  • Description updated (diff)
Actions

Also available in: Atom PDF