Project

General

Profile

Actions
Copy link

Feature #2127

open

Linking artifacts with other artifacts

Added by Nicholas Melvani about 1 year ago. Updated 9 months ago.

Status:
Acknowledged
Priority:
Normal
Assignee:
-
Category:
CRM
Target version:
Wishlist
Start date:
2023-11-23
Estimated time:

Description

I would like to show that a manuscript (B) was copied from another manuscript (A). I can obviously use the production event, but I would like to be able to show the relationship, i.e., that manuscript B is a copy of manuscript A (and vice versa).

Actions
Copy link
 #1

Updated by Alexander Watzinger about 1 year ago

  • Tracker changed from Question to Feature
  • Category set to CRM
  • Status changed from New to Assigned
  • Assignee set to Stefan Eichert
  • Target version set to 8.3.0

Thank you for reporting. As far as I know, currently this isn't possible but I hand it over to Stefan, our model expert, kindly asking him to take a look at it:
Maybe there is something I overlooked and in case I haven't, how we could map/implement this.

Actions
Copy link
 #2

Updated by Stefan Eichert about 1 year ago

This could be implemented by using a relation similar to actor-actor relationships. OA7

Artifact - Artifact relationship:

E18 - P16i(was used for) - E5 - P16i(was used for) - E22

The connecting event is defined by an entity of class E55: [Relationship from original manuscript to copied manuscript (E5)] has type (P2) [Original of/Copy of]
The connection can be directed, eg. in the case of a copy.

Actions
Copy link
 #3

Updated by Alexander Watzinger about 1 year ago

  • Status changed from Assigned to Acknowledged
  • Assignee deleted (Stefan Eichert)
  • Target version changed from 8.3.0 to Wishlist

Thanks a lot Stefan for your feedback and looking into the model.
@Nicholas Melvani - Although Stefan kindly solved the model implementation we still have to evaluate the general usefulness vs. the effort to implement it. Because it won't fit in this year I put it on the wishlist for now but also on the agenda of the next developer meeting.

Actions
Copy link
 #4

Updated by Bernhard Koschiček-Krombholz 9 months ago

Can this be a possibility without shortcut: E22 > P130 > E22

Actions
Copy link
 #5

Updated by Alexander Watzinger 9 months ago

  • Status changed from Acknowledged to In Progress
  • Assignee set to Bernhard Koschiček-Krombholz

As discussed in our OpenAtlas developer meeting, Bernhard may have found a model solution as noted by him here and will look into it.

Actions
Copy link
 #6

Updated by Bernhard Koschiček-Krombholz 9 months ago

  • Status changed from In Progress to Acknowledged
  • Assignee deleted (Bernhard Koschiček-Krombholz)

After discussing it with Alex, this E22 > P130 > E22 is a good approach to handle this issue.

Sadly, our model expert Stefan is currently not available, and this feature most likely needs substantial restructuring of the existing model. That is why we keep it on the wishlist for now.

Actions
Copy link

Also available in: Atom PDF