Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Deleted value from "Call number" field from "MARC Holdings" record is not deleted from Holdings

Description

Overview: Deleted value from "Call number" field from "MARC Holdings" record is not deleted from Holdings. Once the value was entered and saved, the user can only replace it, but not delete it.
Reproducible for following fields of "Call number":
Shelving title 
Copy number
Call number type
Call number prefix
Call number
Call number suffix
Steps to Reproduce:

  1. Log into Snapshot FOLIO environment as User with following permissions:
    Inventory: All permissions
    quickMARC: Create a new MARC holdings record
    quickMARC: View, edit MARC holdings record

  2. Go to "Inventory" app 

  3. Find and open any "Instance" record with source "MARC" (you can import attached "MARC bib" file via "Data import" using "Default - Create instance and SRS MARC Bib" job profile)

  4. Click "Actions" button in third pane >> select "Add MARC holdings record" option.

  5. Select any valid location by clicking on the "Permanent location look-up" and selecting it from dropdowns.

  6. Update value of first indicator (the second box) of "852" field with "\" value with following value: "0"

  7. Add following subfields with values in "852" field:
    "$h call $i number $k prefix $l title $m suffix $t copy number"

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

  9. Check that "Holdings call number" fields are filled with entered by you values:
    Shelving title = "title"
    Copy number = "copy number"
    Call number type = "Library of Congress classification"
    Call number prefix = "prefix"
    Call number = "call number"
    Call number suffix = "suffix"

  10. Click on the "Actions" >> "Edit in quickMARC"

  11. Delete value entered at step 6 from first indicator box of "852" field.

  12. Delete values entered at step 7 from "852" field.

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

Expected Results: "Call number" fields are empty (filled with "-")

Actual Results: "Call number" fields are still filled with values as they were at step 9.

Additional Information: See attached screencast

Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

7

Checklist

hide

TestRail: Results

Activity

Show:

Valery_Pilko July 7, 2023 at 12:25 PM

Hey
According to our discussion, new Jira for described in previous comment issue was created:

Valery_Pilko July 4, 2023 at 4:11 PM
Edited

Hi  
I've tested the fix of this issue on Snapshot environment - described issue was fixed. But I've observed strange behavior, please review it, and tell if we could fix it in scope of this JIRA
See attached screencast:

Issue 1: Deleted "Call number" value trigger "500" error for request GET "/browse/call-numbers/instances"
Steps to reproduce:
1) Create "MARC Holdings" with filled "Call number" field, for example enter "$h call $i number $k prefix $l title $m suffix $t copy number" in "852" field
2) Add an "Item" record to created "Holdings"
3) Open editing window of created "MARC Holdings" record.
4) Delete added subfields which mapped to "Call number" fields, ex. : "$h call $i number $k prefix $l title $m suffix $t copy number" from "852"
5) Save "MARC Holdings" record
6) Go to "Browse" >>"Call numbers" 
7) Try to browse by deleted "Call number" value, ex.: "call number"
Expected result: not exact match placeholder is displayed in the browse result list.
Actual result: "500" error for request GET "/browse/call-numbers/instances" is displayed with following message: 

Note 1: sometimes result list is displayed, sometimes - not. But "500" error persists every time.
Note 2: reproduces also for "Holdings" records with source "Folio"
Note 3: probably it's happening because "Item's" field "effectiveShelvingOrder" doesn't clear after deletion of call number from "Holdings" record.

Workaround: restore deleted value in "MARC Holdings" record or delete an "Item"

cc:  

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Poppy (R2 2023)

RCA Group

Implementation coding issue

Affected releases

Poppy (R2 2023)
Orchid (R1 2023)
Nolana (R3 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 24, 2023 at 8:09 AM
Updated October 14, 2023 at 11:13 AM
Resolved July 13, 2023 at 2:29 PM
TestRail: Cases
TestRail: Runs