005 is not created/updated when action profile's is set to update FOLIO record type = MARC bibliographic/MARC authority/MARC holdings

Description

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. 

  1. Settings > Data import > Set up an Update bib records profile with the following configuration 

    1. Match profile (does not matter if the match is MARC to MARC or MARC to Instance) 

    2. Action profile (see screenshot 1)  where the action = Update and FOLIO record type = MARC bibliographic 

    3. Field mapping profile (see screenshot 2) where the FOLIO record type = MARC bibliographic 

  2. 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 

  3. 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

  1. Update MARC Bib via Data Import/incoming bib has valid 005

  2. Update MARC Bib via Data Import/incoming bib has invalid 005

  3. Update MARC Bib via Data Import/incoming bib does not have an 005

  4. Update MARC Authority via Data Import/incoming bib has valid 005

  5. Update MARC Authority via Data Import/incoming bib has invalid 005

  6. Update MARC Authority via Data Import/incoming bib does not have an 005

  7. Update MARC Bib via quickMARC; check for updated 005

  8. Update MARC Authority via MARC Auth app; check for updated 005

  9. Update MARC Holdings via quickMARC; check for updated 005
     

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux November 13, 2023 at 3:00 PM

Tested on Poppy BF with 1) regular import 010$a to Instance HRID and Instance update, and 2) ISRI update. All fine, Closing this issue

Svetlana Amirova November 9, 2023 at 8:07 AM

Hello  

Ticket fixed and retested on https://bugfest-poppy.int.aws.folio.org/

JenkinsNotifications November 7, 2023 at 6:05 PM

Deployed to the Poppy bf env. Moved status to In bugfix review from status Awaiting deployment. Please proceed with the verification.

Ann-Marie Breaux November 6, 2023 at 7:03 AM

Thanks, . all looks good in Snapshot for regular updating of 005, plus situations when there is a malformed 005 in the incoming record and no 005 in the incoming MARC record. Moving this to Awaiting release

Svetlana Amirova October 30, 2023 at 12:23 PM

Everything works as expected, checked on Snapshot. Moving to in review

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

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
TestRail: Cases
TestRail: Runs