Details
Assignee
Ryan TaylorRyan TaylorReporter
Kateryna SenchenkoKateryna SenchenkoPriority
P3Development Team
FolijetRelease
Trillium (R2 2025)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Ryan Taylor
Ryan TaylorReporter
Kateryna Senchenko
Kateryna SenchenkoPriority
Development Team
Folijet
Release
Trillium (R2 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created July 7, 2023 at 8:00 AM
Updated March 4, 2025 at 8:38 PM
Waiting for confirmation from the SMEs
Temp solution in MODSOURCE-530: error the second copy of the record and do not process. What is the desired behavior for the SMEs?
Duplicate record = 2 or more MARC Bibs that will match to the same Instance
If file contains duplicate records - DI should log them as errored and prevent further processing.
New mechanism should be added in SRM. After incoming record is parsed - check (by 001 value) if such record has already been parsed for a particular job execution. To do that - add table to store 001 values and job execution id, add composite constraint on both values, try saving new value - if save is successful then proceed as usual, if db throws constraint violation error - throw DI_ERROR with message "Incoming record is a duplicate of <001> record". When job is marked COMPLETED - delete rows from that table by job execution id.
Add tests.