[GMU-7] Missing holdings statement causes permanent location to be omitted in the export Created: 15/Jul/21  Updated: 19/May/23  Resolved: 19/Aug/21

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

Type: Bug Priority: P3
Reporter: Magda Zacharska Assignee: Oleksandr Bozhko
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File SearchInstanceUUIDs2021-07-12T17_46_27-04_00-7262.mrc     Microsoft Word SearchInstanceUUIDs2021-07-12T17_46_27-04_00.csv     PNG File actual_result.PNG     PNG File field_mapping_profile.PNG     File instances_with_holdings_and_no_holdings_statements-6.mrk     File instances_with_holdings_and_no_holdings_statements.csv     PNG File job_profile.PNG     PNG File select_job_profile.PNG    
Issue links:
Defines
defines UXPROD-3030 Data export maintenance Closed
Sprint: Firebird Sprint 121
Story Points: 5
Development Team: Firebird

 Description   

Overview:
 When a holdings record doesn't have a holdings statement, the permanent location is not included in the export if both properties were mapped in the mapping profile to the same field but different subfields, if holdings statement  subfield proceeds permanent location subfield.  The problem doesn't occur if the properties are mapped to the different MARC fields.
 

Steps to Reproduce:

  1. Create a mapping profile that includes Source record storage and holdings.  Include holding statement and permanent location in the same field starting with holding statement.  Bugfest example of the mapping profile: https://bugfest-juniper.folio.ebsco.com/settings/data-export/mapping-profiles/view/a9d51730-7f1b-4350-a278-e7bece3cda33?sort=-updated%2Cname
  2. Create a job profile that is associated with the mapping profile from the prior step. Bugfest example of the job profile:  https://bugfest-juniper.folio.ebsco.com/settings/data-export/job-profiles/view/755e736a-3236-494b-b3cf-a455b2a670b8?sort=name
  3. Start export using the job profile

Expected Results:

Specified in the mapping profile field is always present, even if holding statement is not populated in the record
Actual Results:

If the holding statement is missing, the field is not a part of the export, even if the permanent location is there.  

Additional Information:

  • Attaching file used to trigger the export and the file generated by the export.
  • If the fields are mapped to separate files the record is exported as expected
  • I tried with other fields combination (call number for example) and the behavior is as expected as well
  • With the reversed order of the subfield the behavior is also as expected. 
    URL:
    Interested parties:


 Comments   
Comment by Michael Paulmeno [ 20/Jul/21 ]

This issue affects Skidmore College.  I have not tried it on records which have a holdings statement, but no location as we don't seem to have such records.

Comment by Oleksandr Bozhko [ 19/Aug/21 ]

Magda Zacharska , the result has been verified on https://folio-testing.dev.folio.org environment:

  1. Find any instances with holdings, but without holdings statements. For example: instances_with_holdings_and_no_holdings_statements.csv
  2. Go to Settings -> Data export -> Field mapping profiles -> New and create (or use existing) field mapping profile. In this profile we use the same field (866) for both of holdings statements and permanent location (subfields are different):
  3. Go to Settings -> Data export -> Job profiles -> New and create (or use existing) job profile:job_profile.PNG
  4. Go to Data export -> select instances_with_holdings_and_no_holdings_statements.csvfile and run the job (for example, GMU-7 Closed ):
  5. Open the completed job and check the result (instances_with_holdings_and_no_holdings_statements-6.mrk):
  6. As you can see, if there is a holdings permanent location, field 866 is present in the marc record with the correct subfield $z even if there is no holdings statements.
Generated at Thu Feb 08 22:15:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.