Issues
- "Patron look-up" option causes error in Circulation log app for user with only "Circulation log: All" permissionUICIRCLOG-167Resolved issue: UICIRCLOG-167Irina Pokhylets
- TBD if this work should be done R1 2024. Accept circulation LOG_RECORD events of type REMINDER FEE with action Reminder fee triggeredMODAUD-165Resolved issue: MODAUD-165
- Pickup expired not showing in Circulation logCIRCSTORE-265Resolved issue: CIRCSTORE-265Siarhei Charniak
- Recall requests not appearing in circulation logCIRC-1491Resolved issue: CIRC-1491Alexander Kurash
Unexpected DI results
RCA Group
Description
Environment
Potential Workaround
defines
relates to
Checklist
hideTestRail: Results
Details
Assignee
Kateryna SenchenkoKateryna SenchenkoReporter
Kateryna SenchenkoKateryna SenchenkoPriority
P2Story Points
0Sprint
NoneDevelopment Team
FolijetRelease
Poppy (R2 2023) Bug FixTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Reporter
Priority
P2Story Points
Sprint
Development Team
Release
TestRail: Cases
TestRail: Runs
Activity
Kateryna SenchenkoOctober 18, 2023 at 1:13 PM
Closing as duplicate of
Kateryna SenchenkoOctober 18, 2023 at 12:37 PM
Further discussion showed that the problem is in matching - records that were not supposed to be found matched. The root cause for such behavior is unclear at the moment. is created, there will be documented the reproduction steps, actual and expected results. Folijet will continue working on the issue in scope of .
is it OK to close this task as it accounted only for the preliminary investigation?
Kateryna SenchenkoSeptember 28, 2023 at 9:56 AM
A couple of points to clarify: * Job did not fail. Import runs successfully with no errors reported.
Profile contains branching. In case incoming records don't match - a new Instance, Holdings, Item are created. If records match no actions are supposed to be taken in the first processing node. However, the profile contains a Modify MARC Bib action at the end, and this action is not placed under the previous branches, therefore it is a standalone action that will be taken on every incoming record.
Modify MARC Bib is a tricky action - it modifies not only the MARC Bib, it also updates the Instance, because each action on MARC Bib should also be reflected on the Instance.
What happened in the job in question - 2 nodes of profile were processed: # The match and actions depending on the result of the match. Nothing for the match; Create Instance, Holdings, Items for the non-match. Incoming file contained 37 new records that didn't match (for those Instance, Holdings, Items were created) and 41 records that matched (inventory already contained Instances with same System Control Number) - no actions were taken for those records.
The Modify action that modified MARC Bibs and reflected those changes in linked Instances. This action is standalone in the profile and is taken on each record in the incoming file. Hence the Updated status for each Instance.
What can be done to prevent actions on records that already exist:
Place Modify action in the branch to be executed only on those records that were supposed to be created. That way profile will contain only one node for processing. Please review changed profile on bugfest https://bugfest-orchid.int.aws.folio.org/settings/data-import/job-profiles/view/125fc72c-cda0-4c1e-90cf-82d604f9c8fe?sort=name
Library reported that the import completed successfully. There were 78 records in the file. The DI job matches the incoming marc 035 9 to the instance system control number. If there is a match, the job stops, if there isn't a match, then instances/holdings/items/marc SRS are created. These were all new records. The job created 78 SRS marc bibs, 37 instances, 37 holdings and 37 items. However, 41 instances/holdings/items weren't created. The log has marc SRS created and instance updated.