April 2020 - Koha-bugs - lists.koha-community.org

[Bug 24683] New: Holds on biblios with different item types: rules for holds allowed are not applied correctly if any item type is available
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '21

08 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24683 Bug ID: 24683 Summary: Holds on biblios with different item types: rules for holds allowed are not applied correctly if any item type is available Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hans.palsson(a)hkr.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 99257 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=99257&action=ed… An example of a biblio with mixed itemtype items. When having different rules for placing holds for each item type, having both item types on one biblio "breaks" these rules. As shown in the attachment: Smart rules for item type "Course literature" allows patrons to place holds on items. The smart rules for the item type "Dayloan" does not allow patrons to place holds on the items. When having both item types on one biblio, it should in theory be possible to place a hold on biblio level even if the dayloan item type is available. Setting the option "AllowHoldItemTypeSelection" to allow does not solve the problem. Various other options have been tried, but as long as there is an available item that is not "not for loan", then placing holds is not possible. This is troublesome for us, since holds must be placed manually by staff. The Dayloan item type is for having a copy available for many students and should not be placed on hold. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[Bug 24855] New: Lost items not marked returned when floating-point math causes amountoutstanding to be not-quite-zero
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '21

04 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24855 Bug ID: 24855 Summary: Lost items not marked returned when floating-point math causes amountoutstanding to be not-quite-zero Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Floating point math and a strict "if amountoutstand=0" result in things not getting marked as returned when they should. I've had a hard time figuring out exactly when this will go wrong, so I've got some very specific steps to recreate. To test: - set MarkLostItemsAsReturned to never mark items returned - turn on Fines log - find/create a patron with no outstanding fees or fines - manually apply 8 overdue charges of $4.10 - create an item with a replacement cost of 6.99 - check item out to patron - mark item lost, generating 6.99 lost fee for patron - pay off entire balance using the Pay Amount button - confirm patron no longer owes any fees, but item has not been marked as returned when fee was paid off - check fines log, see that the accountline for this lost fee recorded a payment of "6.98999999999999" and a new amountoutstanding of "7.105427357601e-15" While we round these values to 4 decimal places in accountlines, that rounding happens *after* Koha checks if amountoutstanding=0 when deciding whether or not to mark the lost item returned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 22591] New: Allow to temporarily exclude patrons from routing lists
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '21

04 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22591 Bug ID: 22591 Summary: Allow to temporarily exclude patrons from routing lists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- At the moment it's not possible to temporarily exclude patrons from routing lists. This would be very handy when patrons like internal research staff are known not to be available for a longer time to receive issues (vacation, sickness, remote research...) It could work similarily to suspending holds where you set a date on which to reactivate the routing list memberships. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 22673] New: Road types only on one address
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '21

03 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22673 Bug ID: 22673 Summary: Road types only on one address Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- When adding/editing a patron, the authorized values for road types only appear next to the first address - if we really want them to be used as authorized values all addresses should have the pull down. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20662] New: The "most poplular" function on the opac does not honour opac supression
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '21

02 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20662 Bug ID: 20662 Summary: The "most poplular" function on the opac does not honour opac supression Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The "most popular" function on the OPAC does not honour the opac suppression in the 942$n subfield. I think this is because "most popular" is based on a database query, and the opac suppression is in a MARC field which is indexed in Zebra. I think the solution is probably to create a biblio.suppressed field and have the 942$n store data in that field. Then we check that database field for things like "most popular" and other database queries. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 20415] New: Remove UseKohaPlugins system preference
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '21

01 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20415 Bug ID: 20415 Summary: Remove UseKohaPlugins system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In order to use plugins you need: - to have uploaded some plugins - to have activated the relevant part of your koha conf file - to have the right permissions - to have activated this system preference I think that's a little too much and the system preference could be removed and be always on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59

[Bug 25109] New: Add execution locking to Koha::Script
by bugzilla-daemon＠bugs.koha-community.org 31 May '21

31 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25109 Bug ID: 25109 Summary: Add execution locking to Koha::Script 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 52

[Bug 17661] New: Differences in whitespace cause duplicate facets
by bugzilla-daemon＠bugs.koha-community.org 29 May '21

29 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17661 Bug ID: 17661 Summary: Differences in whitespace cause duplicate facets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 57658 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57658&action=ed… 490 $a Harry Bosch mysteries; $v 3 -- whitespace after semicolon in 490$a There are two marc files attached; 'a.marc' and 'b.marc' Each contains the string "Harry Bosch mysteries;" in 490$a. In a.marc, this is followed by a trailing space character, in b.marc, it is not. If you import both records and do a keyword search for 'Harry Bosch mysteries', you will see that Harry Bosch mysteries shows twice in the Series facet. -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 23626] New: Add a system preference to limit the number of rows of data used in a chart when viewing report results
by bugzilla-daemon＠bugs.koha-community.org 28 May '21

28 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23626 Bug ID: 23626 Summary: Add a system preference to limit the number of rows of data used in a chart when viewing report results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul(a)flo.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 23624 Created attachment 92845 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=92845&action=ed… New syspref ReportsMaxRowsInChart The number of rows generated by a report is potentially unlimited; this has the potential to exhaust all available memory, bringing a Koha server down to its knees. The attached patch introduces a system preference to limit the number of rows used when charting report results; at this time, and with bug #23624 fixed, that is the only aspect of reporting that loads all results into memory at once. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23624 [Bug 23624] Count rows in report without (potentially) consuming all memory -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 72

[Bug 24541] New: Database cleanups, purge messages
by bugzilla-daemon＠bugs.koha-community.org 27 May '21

27 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24541 Bug ID: 24541 Summary: Database cleanups, purge messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz misc/cronjobs/cleanup_database.pl provides some database cleanup. Yet some tables that could need cleanup are not in this script. Purge messages older than day (default 365). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31