Done
Details
Assignee
Tatsiana TarhonskayaTatsiana TarhonskayaReporter
Khalilah GambrellKhalilah GambrellPriority
P2Story Points
3Sprint
NoneDevelopment Team
FolijetFix versions
Release
Poppy (R2 2023) Bug FixRCA Group
Implementation coding issueAffected releases
Poppy (R2 2023)Orchid (R1 2023)Nolana (R3 2022)Morning Glory (R2 2022)Affected Institution
!!!ALL!!!TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Tatsiana Tarhonskaya
Tatsiana TarhonskayaReporter
Khalilah Gambrell
Khalilah GambrellPriority
Story Points
3
Sprint
None
Development Team
Folijet
Fix versions
Release
Poppy (R2 2023) Bug Fix
RCA Group
Implementation coding issue
Affected releases
Poppy (R2 2023)
Orchid (R1 2023)
Nolana (R3 2022)
Morning Glory (R2 2022)
Affected Institution
!!!ALL!!!
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 24, 2023 at 7:49 PM
Updated December 11, 2023 at 3:09 PM
Resolved November 6, 2023 at 7:03 AM
Problem: When action profile is set to update FOLIO record type = MARC bibliographic/MARC authority/MARC holdings when user attempts to import an updated MARC bib/MARC authority/MARC holdings record via data import then the following issues are observed.
If 005 is invalid then the MARC record is stored with the invalid 005 value
If 005 is not present then the MARC record is stored without a 005 value
If 005 is present AND the record is updated via data import then the 005 is not updated with the date+time of when data import
Steps to reproduce
Precondition: Bib records already created in system. Can use attached file.
Settings > Data import > Set up an Update bib records profile with the following configuration
Match profile (does not matter if the match is MARC to MARC or MARC to Instance)
Action profile (see screenshot 1) where the action = Update and FOLIO record type = MARC bibliographic
Field mapping profile (see screenshot 2) where the FOLIO record type = MARC bibliographic
Via data import, update a bib record(s) with 005\without 005\OR invalid 005 using the Update bib records profile specified in step 1
Once data import job is complete then View source record
Expected outcome: 005 should be present and should represent the date+time stamp that the record's update (via import or quickMARC) was completed. If 005 is not present, or if formatting is invalid, add or correct the 005, and update it to reflect the current update date and time. See requirement details here: https://folio-org.atlassian.net/wiki/display/MM/005+handling
Actual outcome: If 005 is not included in the import then no 005 is present. If invalid 005 in the import then invalid 005 is stored. If valid 005 is present it does not update. MARC holdings and MARC authority record updates has the same issue and should be fixed in the context of this issue. https://folio-org.atlassian.net/wiki/display/MM/005+handling
AND field mapping profile has the following setup
Testing
Update MARC Bib via Data Import/incoming bib has valid 005
Update MARC Bib via Data Import/incoming bib has invalid 005
Update MARC Bib via Data Import/incoming bib does not have an 005
Update MARC Authority via Data Import/incoming bib has valid 005
Update MARC Authority via Data Import/incoming bib has invalid 005
Update MARC Authority via Data Import/incoming bib does not have an 005
Update MARC Bib via quickMARC; check for updated 005
Update MARC Authority via MARC Auth app; check for updated 005
Update MARC Holdings via quickMARC; check for updated 005