[Koha-bugs] [Bug 19813] New: MarcItemFieldsToOrder cannot handle a tag not existing

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Dec 14 16:30:52 CET 2017


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19813

            Bug ID: 19813
           Summary: MarcItemFieldsToOrder cannot handle a tag not existing
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Acquisitions
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: kyle at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org

MarcItemFieldsToOrder defines how Koha looks at tags in order records to
generate item data.

Let's look at a simplified case:
homebranch: 955$a
holdingbranch: 956$a

So, here we are looking at 955 for the home branch, and 956 for the holding
branch. So, it should make sense that Koha requires that these fields exist in
equal number in the record. That is, for each 955, there should be a
corresponding 956.

Let's look at a different case:
homebranch: 946$a|975$a
holdingbranch: 946$a|975$a

In this case, we are using the fallback behavior. VendorA stores the branch
data in 946, and VendorB stores it in 975. This seems like it would work, but
it won't! That's because Koha is expecting there to be the same number of 946's
as there are 975's! In reality, the VendorA records will have a number of
946's, and *zero* 975's. The inverse will be true for VendorB.

Koha should be able to skip those tags that simply don't exist in the record.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list