June 2023 - Koha-bugs - lists.koha-community.org

[Bug 30451] New: Delete a subscription delete the linked order
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30451 Bug ID: 30451 Summary: Delete a subscription delete the linked order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org Several issues happened when you delete a subscription linked to an order : - the warning message doesn't mentioned an existing order - the deletion of the subscription deleted the order too. That's annoying... I think the deletion should only empty the aqorder.subscriptionid datafield. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 23548] New: AQ field required in checkin response
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23548 Bug ID: 23548 Summary: AQ field required in checkin response Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When doing checkin through SIP, the AQ field is a required field in the response (code 10), however it is only provided when the item checked in is found. There should be an empty "AQ|" in the return message when the item is not found to not violate the required field status. For context, this is an actual issue with the checkin stations from PV-SUPA when you want them to accept any book, even if they're not found by Koha. It gives an error, and refuses to handle the checkin further. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 34036] New: Single receive doesn't reload data and order lines appears as pending
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34036 Bug ID: 34036 Summary: Single receive doesn't reload data and order lines appears as pending Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 8179 When you receive a single order line using the Receive link, the table appears with the order line still pending instead of it showing in the "Already received" section. When you manually reload the table, the order line moves. To test: * Create a basket and order line, close basket. * Receive shipment, create invoice. * Click on the receive link in the table of pending order lines. * Fill out the form, especially the quantity received. Save. * Verify the line still shows in the "pending orders" table, instead of the "Already received" area below. * Reload page, order line now moves. I believe we need to reload some data? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 [Bug 8179] Receiving multiple order lines at once -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 22135] New: Inventory tool doesn't export "out of order" problem to CSV
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '23

15 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22135 Bug ID: 22135 Summary: Inventory tool doesn't export "out of order" problem to CSV Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: marka(a)pobox.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21408 Target Milestone: --- Created attachment 84013 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=84013&action=ed… Fix for out of order problem seen as blank in CSV exported by inventory tool When using the inventory tool with an uploaded barcode file and checking the "Compare barcodes list to results", "Check barcodes list for items shelved out of order" and "Export to CSV file" checkboxes, the resulting CSV file shows a blank in the "problem" column for items with out of order callnumbers. I was able to fix this using the attached patch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21408 [Bug 21408] Inventory - Warn of items possibly scanned out of order -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 33656] New: In serial collection, items with "Missing" status are always checked by default
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33656 Bug ID: 33656 Summary: In serial collection, items with "Missing" status are always checked by default Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: maude.boudreau(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Created attachment 150534 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=150534&action=e… Example Hi, In serial collection, items with "Missing" status are always checked by default. Some libraries always maintain this status in issues. This creates a problem when they want to prune issues. Example : (see file attachment) To prune all the numbers of 2021, i need to : Go to the 2022 and 2024 tab to uncheck all missing numbers so that it is not deleted. Go to the 2021 tab, click on "select all" and on "delete selected issues". If you forget to uncheck before clicking delete, all the missing numbers of 2022 and 2024 will be deleted! Also, when we edit serials. All missing numbers appear. Which can become cumbersome when there are several numbers for several years. It would be nice to have a system preference that allows us to choose if we want to check it or not by default Thanks! Maude -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31213] New: When performing a basic search with no results, repeat the search with term quoted
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31213 Bug ID: 31213 Summary: When performing a basic search with no results, repeat the search with term quoted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Under elastic, when searching for some special characters a search may fail: Ivy + Bean The 6:20 man etc. These terms work when quoted: "Ivy + Bean" It would be nice if we just tried this automatically for the user -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 31179] New: Duplicate item is duplicating internal item fields
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31179 Bug ID: 31179 Summary: Duplicate item is duplicating internal item fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Duplicate item is intended to duplicate the visible cataloging fields of an item, however, currently it is duplicating the complete internal record of the item To recreate: 1 - find an item in Koha staff client, copy the barcode 2 - Issue this item to a patron 3 - Return to the record 4 - Edit items 5 - Click 'Actions->Duplicate' for the item in question 6 - Save the item 7 - Note in the items table above for that 'Total checkouts' 'Due date' etc. have been copied to new item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 30042] New: Remove Date::Calc use in cleanborrowers.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30042 Bug ID: 30042 Summary: Remove Date::Calc use in cleanborrowers.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 28493] New: Make koha-passwd display the username
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28493 Bug ID: 28493 Summary: Make koha-passwd display the username Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com The current output looks like this: sudo koha-passwd <site> Password for <site>: abc123 Press enter to clear the screen... But who remembers what the username looks like? It would be helpful to print this too, along with the password. (The format of the username is "koha_<site>".) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 32271] New: Overdue fines cap (amount) set to 0.00 when editing rule
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '23

14 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32271 Bug ID: 32271 Summary: Overdue fines cap (amount) set to 0.00 when editing rule Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I noticed that when I add a circulation rule, if I leave the Overdue fines cap (amount) field empty, it is displayed as 0.00. If I later edit this rule, the Overdue fines cap (amount) field is *set to* 0.00, even if that's not what I wanted. This causes the fines.pl script to charge no fine at all. To test: 0. Preliminary settings 0.1. finesMode system preference must be set to Calculate and charge 0.2. MaxFine system preference must be empty 0.3. In Tools > Calendar, today must not be a holiday 1. Add a circulation rule with fines but no fines cap 1.1. Go to Administration > Circulation and fines rules 1.2. Add or modify a circulation rule, make sure - There is a quantity in "Current checkouts allowed" - There is a number of days in "Loan period" - There is an amount in "Fine amount" - There is a number in "Fine charging interval" (usually 1) - "Overdue fines cap (amount)" is **empty** 1.3. Save the circulation rule --> Note that the amount in "Overdue fines cap (amount)" is displayed as 0.00 2. Checkout an item with a date in the past to create an overdue 2.1. Find an item barcode 2.1.1. Go to Item search 2.2.2. Click Search 2.2.3. Copy a barcode from the search results 2.2. Go to a patron's file 2.2.1. Go to Patrons 2.2.2. Click on "Search" 2.2.3. Click on a patron's name 2.3. Click on the "Check out" tab on the left of the patron's file 2.4. Click on the settings icon in the "Enter item barcode" field 2.5. Pick a due date in the past 2.6. Paste the item barcode in the field 2.7. Click "Check out" or press Enter 2.8. Click "Yes, check out" --> Patron should have an overdue 3. Run fines.pl 3.1. In a terminal, run ./misc/cronjobs/fines.pl 4. Check that the patron has fines 4.1. Go to the patron's file 4.2. Click on the "Accounting" tab on the left --> Patron should have a fine (accruing) 5. Modify the circulation rule, change any field except "Overdue fines cap (amount)" (let's say the quantity of current checkouts has gone up) 5.1. Go to Administration > Circulation and fines rules 5.2. Click "Edit" next to the rule created in step 1 --> Note that the amount in "Overdue fines cap (amount)" is 0.00 5.3. Change any setting except "Overdue fines cap (amount)", e.g. change Current checkouts allowed to another number 5.4. Click "Save" --> Note that the amount in "Overdue fines cap (amount)" is displayed as 0.00 6. Redo step 2 7. Redo step 3 8. Redo step 4 --> Note that the patron has no fine If Overdue fines cap (amount) is empty, it should display as empty (or "Unlimited"), and when we edit the rule, the field should still be empty and save as empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56