MARC Bib | Can't update invalid "07" position of "LDR" field

Description

Overview: When "MARC Bibliographic" record has invalid value at "07" position of "LDR" field, the user can't save this record with updated "07" value.
Steps to Reproduce:

  1. Log into MG Bugfest FOLIO environment as User with the following permissions:
    Data import: Can upload files, import, and view logs
    Inventory: All permissions
    quickMARC: View, edit MARC bibliographic record

  2. Go to "Data import" app.

  3. Import the attached ".mrc" file via "Data import" app using "Default - Create instance and SRS MARC Bib" job profile.

  4. Once import is complete, click on the title at appeared row.

  5. Click on the "Created" hyperlink at "instance" column to open the imported "Instance" record.

  6. Click on the "Actions" >> "Edit MARC bibliographic record"

  7. Edit "07" position of "LDR" field with valid value [for example: "i"]

  8. Open "DevTools" (F12 button).

  9. Click on the "Save & close" button.

Expected Results: The request was sent. The "MARC Bibliographic" record has been saved.
Actual Results: The request was not sent. The editing window of "MARC Bibliographic" record is being displayed.

Discussion for how to address this issue: Ignore stored 008 when Leader 07 value is invalid. 

  • When user does not change the Leader 07 invalid value and makes edits/additions to the record and hits Save Then display the invalid Leader 07 position value (see requirement - https://folio-org.atlassian.net/browse/UIQM-234

  • When user changes the Leader 07 invalid value to a valid value THEN display the default MARC 008 set of bytes AND when user hits Save Then the save should be successful and all updates including to Leader 07 and 008 should be saved. 

Additional Information: See attached screencast.
Also, user can't derive new "MARC Bibliographic" record from the record with invalid 07 position of LDR field.
URL: https://bugfest-mg.int.aws.folio.org/inventory/view/20c14229-5cc2-4217-872e-e19b8c770326 
Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Khalilah Gambrell September 10, 2023 at 1:43 PM

Hey   - I cannot reproduce this issue now that we have updated 008 handling. 

Khalilah Gambrell August 4, 2022 at 1:01 PM

  and   - I am moving this to Nolana at this point, I need to redesign Leader and 008 handling. Users have a workaround - re-import. 

Denys Bohdan August 4, 2022 at 7:45 AM

Hey , could you also provide default 008 bytes values please?

Denys Bohdan August 3, 2022 at 4:08 PM

Moved from In Progress to Open for now to re-estimate with new requirements

Cannot Reproduce

Details

Assignee

Reporter

Priority

Development Team

Spitfire

Release

Quesnelia (R1 2024)

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 3, 2022 at 11:46 AM
Updated November 6, 2023 at 3:57 PM
Resolved September 10, 2023 at 1:43 PM
TestRail: Cases
TestRail: Runs