[GMU-34] Holdings notes not being exported properly in MARC Bibs when there are multiple holdings Created: 18/Aug/22  Updated: 07/Oct/22  Resolved: 29/Sep/22

Status: Closed
Project: generate-marc-utils
Components: None
Affects versions: None
Fix versions: 1.5.0

Type: Bug Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Oleksandr Bozhko
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File Export Bib+Holdings bug.mp4     File Export with holdings notes.mrc     PNG File Export with holdings notes.png     PNG File Holdings transformations.png     PNG File MichState-ExportData.png     PNG File MichState-Holdings1.png     PNG File MichState-Holdings2.png     JPEG File completed.JPG     JPEG File hold_note_annex_library.JPG     JPEG File hold_note_main_library.JPG     JPEG File job_profile.JPG     JPEG File mapping_profile.JPG     JPEG File mrk_output.JPG     JPEG File select_instance_with_2_holdings.JPG    
Issue links:
Defines
defines UXPROD-3665 Firebird - Nolana R3 2022 Enhancement... Closed
Relates
relates to FAT-3142 Review of C365624 Test Case Closed
Sprint: Firebird - Sprint 149
Story Points: 3
Development Team: Firebird
Release: Nolana (R3 2022)
Affected Institution:
MI State University/Library of Michigan
RCA Group: TBD

 Description   

Overview:
When exporting a MARC Bib with holdings data for multiple holdings, if the holdings have different notes in them, the exported note data is not separated properly between the two 9xx fields. It might be worth checking for any similar issue with repeatable fields in the holdings record when there are multiple holdings being exported as data in a MARC Bib

Environment: This is happening in a Lotus HF1 environment, but reproduces in Snapshot

Steps to Reproduce:

  1. Find an Instance in Inventory with Source = FOLIO, or else import one using Inventory Single Record Import or the default profile for creating a MARC Bib and Instance
  2. View the Instance that was created in Inventory
  3. Create a holdings on the Instance, with the following information
    • Permanent location: pick any location in the hosted ref envs (Main, Annex, etc.)
    • Add 2 notes in the holdings record
      • Note 1: pick a holdings note type from the dropdown list, add a note, and mark it Staff only
      • Note 2: pick a different holdings note type from the dropdown list, add a note, and DO NOT mark it Staff only
  4. Save the new holdings record
  5. Create another holdings record on the Instance, with the following information
    • Permanent location: pick any location in the hosted ref envs (Main, Annex, etc.), but it should be different from the location in the first holdings you created
    • Add 3 notes in the holdings record
      • Note 1: pick another different holdings note type from the dropdown list, add a note, and DO NOT mark it Staff only
      • Note 2: pick another different holdings note type from the dropdown list, add a note, and mark it Staff only
      • Note 3: pick another different holdings note type from the dropdown list, add a note, and DO NOT mark it Staff only
  6. Save the new holdings record
  7. Now you should have 2 holdings on the Instance
    • Each holdings has a different permanent location
    • Holdings 1 has 2 notes, each a different type, 1 marked as staff only, 1 not marked as staff only
    • Holdings 2 has 3 notes, each a different type from each other and from holdings 1, with 1 marked as staff only, and 2 not marked as staff only
    • So a total of 5 notes across the 2 holdings, each note a different type, with 2 marked as staff only, and 3 not marked as staff only
  8. Go to Settings/Data export/Field mapping profiles, and create the following profile
    • Name: Holdings notes and HRID
    • Record type: Holdings, Source record storage (entire record)
    • Output format: MARC
    • Transformations
      • Holdings HRID: 900 $a
      • Then select the plain and staff version fields for each of the notes that you assigned to the holdings records, and put them in successive 900 subfields. See attached screenshot for an example
  9. Save the field mapping profile
  10. Go to Settings/Data export/Job profile, and create the following profile
    • Name: MARC Bib with Holdings HRID and Notes
    • Attach the field mapping profile created in the previous step
  11. Save the job profile
  12. Go to Inventory and find the Instance that was created
  13. In the results list, go to Actions/Save instances UUIDs
  14. Go to the Data export app and upload the delimited file of UUIDs
  15. Select the job profile created above and run the export
  16. Once the MARC file has been created, download it and view the 900 fields and their subfields

Expected results:
Two 900 fields in the MARC Bib, each with a different Holdings HRID and the 2 or 3 notes pertaining to that specific Holdings

Actual results:
Two 900 fields in the MARC Bib, with the correct HRIDs, but both displaying all 5 notes

Other: see attached video, screenshots, and exported MARC file from Snapshot, plus a few screenshots from Mich State's Lotus HF1 environment

Interested parties: Joshua Barton Ann-Marie Breaux Heather McMillan



 Comments   
Comment by Denis [ 07/Sep/22 ]

might be moved to GMU - tbd

Comment by Oleksandr Bozhko [ 21/Sep/22 ]

After investigation it was decided to move this bug into GMU project.

Comment by Oleksandr Bozhko [ 28/Sep/22 ]

Magda Zacharska - this story was verified on snapshot-2 environment:

1. Select any instance and add 2 holdings with different number of holdings notes and holdings locations:

2. Go to Settings -> Data export -> Field mapping profiles -> New and create the following mapping profile:

3. Go to Settings -> Data export -> Job profiles -> New and create the following job profile:

4. Go to Data export -> drag and drop csv file with UUID of instance that contains 2 previously created holdings, select previously created job profile, Instances and click on Run:

5. Download completed .mrc file and verify the result:

As you can see above, every holdings record contains only its own holdings notes.

 

 

Generated at Thu Feb 08 22:16:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.