Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Original Work is replaced without any warning when a new Work is created with the same fingerprint.

Description

Steps:

  1. Via Linked data editor, create a Work with any title (say, Work 1)

  2. Create an instance under that Work

  3. Create another work with the same title used in step #1 & click “Save”

  4. Actual behavior: The original work is replaced by the new Work. The instance is not shown in search results. (When opening the work for editing, you can see that the instance actually exists under the work. So, this is a search problem)

  5. Expected behavior: After clicking any “Save” button, API should return the "already_exists" error code back to UI.
    Note: UILD-508 will translate the "already_exists" error code to the friendly error message "The same resource ID already exists."
    Also, after being saved, it needs to show in the search, the instance that already was linked to the original work.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

Activity

Show:

Tetiana Kovalchuk March 6, 2025 at 10:40 AM

Tested on etesting snapshot

Build version: mod-linked-data-1.0.1-SNAPSHOT.145

Pavel Bobylev March 4, 2025 at 11:30 AM

Update resource flow (out of scope for this ticket, just for the reference):

  1. Existed resource is being deleted

  2. Incoming resource is being created with merging edges and properties from the previously existed one

  3. Created resource is being sent to the search module for indexation

 

Create resource flow:

Before this ticket:

  1. we just save new resource as is.

  2. If there is already existed one, it’s edges are connected to new one automatically because we don’t deleted anything beforehand.

  3. And it’s being indexed by the search module without previously existed edges because we don’t merge anything

After this ticket:

  1. It’s not possible to create a resource if the same ID exists

  2. If resource is created, that means there is no previously existed one with edges connected

  3. Thus there is nothing to fix in indexing functionality. New resource is being indexed correctly.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Citation

Fix versions

Release

Sunflower (R1 2025)

RCA Group

Incomplete/missing requirements

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 14, 2025 at 2:04 PM
Updated March 13, 2025 at 8:42 PM
Resolved March 10, 2025 at 6:34 PM
Configure
TestRail: Cases
TestRail: Runs