[GMU-1] POC - Detect which record exactly leads to the exception during the export to the error logs Created: 06/Oct/20  Updated: 10/Mar/21  Resolved: 27/Nov/20

Status: Closed
Project: generate-marc-utils
Components: None
Affects versions: None
Fix versions: 1.1.0

Type: Story Priority: P3
Reporter: Andrii Novytskyi Assignee: Igor Gorchakov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png    
Issue links:
Relates
relates to MDEXP-259 Log errors for Holdings records export Closed
relates to MDEXP-260 Log errors for Inventory Item records... Closed
Sprint: Concorde - Sprint 100, Concorde - Sprint 101, Concorde - Sprint 102
Story Points: 3
Development Team: Concorde

 Description   

Overview:
Currently, we are not able to identify which record is affected during the mapping process, to populate proper ErrorLog. For now, we are sending instance, associated holdings, and items as affected records, without specifying which exactly record affected.

Approach
Explore ways to find which record affected.

Acceptance Criteria

  • A POC is done, the result presented to the team;
  • Ticket to implement it is created.


 Comments   
Comment by Igor Gorchakov [ 03/Nov/20 ]

Flag added

Updated status to 'Blocked', now I work on p1&p2 bugs

Comment by Igor Gorchakov [ 03/Nov/20 ]

Switched back to work on this story

Comment by Viktor Soroka [ 17/Nov/20 ]

Igor Gorchakov, please move the issue to https://folio-org.atlassian.net/projects/GMU/summary as we agreed earlier.

Comment by Igor Gorchakov [ 23/Nov/20 ]

Andrii Novytskyi Illia Daliek guys do you accept my story?

Comment by Igor Gorchakov [ 27/Nov/20 ]

Verification:
The implemented approach allows catching the errors/exceptions while data translation happens, with identifying the exact record that caused an exception.
I have exported a few of Instances using default profiles just to verify nothing is broken and works as before the merge:
1. Created csv file that contains 2 uuids:
7fbd5d84-62d1-44c6-9c45-6cb173998bbd
00f10ab9-d845-4334-92d2-ff55862bf4f9

2. The job is not failed:

3. Exported file looks as before the merge:

Comment by Andrii Novytskyi [ 27/Nov/20 ]

verified in the scope of https://folio-org.atlassian.net/browse/MDEXP-262.

Generated at Thu Feb 08 22:15:43 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.