[Koha-bugs] [Bug 35026] Refactor addorderiso2709.pl to use object methods

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Feb 1 23:36:29 CET 2024


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

Barbara Johnson <barbara.johnson at bedfordtx.gov> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barbara.johnson at bedfordtx.g
                   |                            |ov

--- Comment #23 from Barbara Johnson <barbara.johnson at bedfordtx.gov> ---
Here is what I found in testing this bug:

* The location code of 'AV' was not imported into the 949$c tag even though it
looks correct in the sample file and the location code exists.

* No data was imported into replacement price (949$v) because there was no data
in the sample file.  It would be good to test this field because I hear many
complaints from librarians when the replacement price doesn't come through.

* The itemcallnumber from the sample file was not imported into the 949$o. It
was not specified to be included in MarcItemFieldsToOrder in the test plan.

* The barcode# from the sample file was not imported into the 949$p. It was not
specified to be included in MarcItemFieldsToOrder in the test plan.

* The sample file contains three fields with the date of 2014-09-04.  These are
in subfields d - Date acquired and w - Price effective from. Those fields were 
not specified to be included in MarcItemFieldsToOrder in the test plan which is
probably why they populated with today's date. That date was also in subfield r
in the sample file. 

* There are other fields that were not contained in the sample data that I
think it would be good to test. They are the 949$7 (Not for loan), 949$u
(Uniform resource identifier) and 949$x (Nonpublic note)

* When I saved the file and viewed it in steps 9 and 10 I got the message:
     No records imported
     No records have been imported because they all match existing records in 
     your catalog. You'll have to treat them individually.

Since that's not something I do very often I opted to not match existing
records which were successfully imported. The item data looked correct to me in
the other fields, the prices appeared correct and the ordered were split up
amongst the three funds.

Once you are ready I'll be glad to retest this one.

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


More information about the Koha-bugs mailing list