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

[Bug 25323] New: Patrons can act as their own guarantor
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '25

03 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25323 Bug ID: 25323 Summary: Patrons can act as their own guarantor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for a patron to act as a guarantor, if the guarantee's record is returned it can be selected, therefore becoming his/her's own guarantor. This makes no sense. To reproduce: 1) Create two users, a parent and a child both with the same surname (for example Parent Smith and Child Smith) 2) Edit the child record and under the Guarantor information, use the "Search to add" button to search for a guarantor. 3) Search for Smith. Both Parent Smith and Child Smith will be listed in the results. 4) Select Child Smith and save the user record. Child Smith is now the guarantor for Child Smith. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 26024] New: Purge undone of zebraqueue in cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26024 Bug ID: 26024 Summary: Purge undone of zebraqueue in cleanup_database.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Purge script misc/cronjobs/cleanup_database.pl with --zebraqueue DAYS will delete entries from zebraqueue table with done=1 We now start to use Elasticsearch only so entries of zebraqueue with done=0 stay in database. I propose we purge all entries in cleanup_database.pl. Even with zebra, if indexing does not occur after several days (30 by default), there is a problem and one need a full rebuild. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 20954] New: Add ability to set syspref overrides in SIP as we can in apache
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20954 Bug ID: 20954 Summary: Add ability to set syspref overrides in SIP as we can in apache Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We should be able to set system preference overrides for SIP in a similar manner that we do in Apache. It would be great if we could specify those overrides on both a config level, and login level basis. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 19919] New: Writing off a Lost Item Fee marks as "Paid for by patron"
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '24

26 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19919 Bug ID: 19919 Summary: Writing off a Lost Item Fee marks as "Paid for by patron" 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: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 70293 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=70293&action=ed… An example A replacement copy was ordered for an item that was "long lost overdue" on a patron's account. The librarian wanted the old copy deleted from the system to keep the record clean. We checked in the item, marked it as lost, and then wrote off the fee associated with the item. Finally we reapplied the fee manually, no longer associated with the item. We noticed that at the point of the write off, the item gets a line that says paid for by (Patron name and barcode) DATE TIME. This also happens if the book is checked in and no longer marked as lost (say it was returned by the borrower so we wrote off the lost item fee.) The borrower has not paid for the book in either situation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 25963] New: Koha converts ":" to "=" in search terms for Zebra which causes search to fail
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '24

26 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25963 Bug ID: 25963 Summary: Koha converts ":" to "=" in search terms for Zebra which causes search to fail Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au Koha changes : to = because Zebra uses = to separate indexes from search terms, but this is problematic, because it transforms all colons. For instance, "title : subtitle" will become "title = subtitle" and that will cause a Zebra error. Here's the bug removed: buildQuery eb6b10f8 (Chris Nighswonger 2010-02-01 23:18:09 -0500 1768) # $query =~ s/:/=/g; Here's the bug re-introduced. getRecords 08c15831 (Joe Atzberger 2009-07-08 15:27:45 -0500 381) $query_to_use =~ s/\:/\=/g; # change : to = last minute (FIXME) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15725] New: Merge permission
by bugzilla-daemon＠bugs.koha-community.org 25 Dec '24

25 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15725 Bug ID: 15725 Summary: Merge permission Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice if Koha had a permission to limit access to the merge records option (Merge selected button) on the addbooks.pl search results page and the virtualshelves/shelves.pl page (lists). This is especially important in a consortial catalog environment where many people have cataloging permissions, but most probably shouldn't have the ability to merge records. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 19876] New: Koha::Account->pay() does not exit specific fine loop when balance is used up
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19876 Bug ID: 19876 Summary: Koha::Account->pay() does not exit specific fine loop when balance is used up 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron selects specific fines to pay and enters an amount less than all of those fines the loop will continue through all fines. This can be problematic for lost fines which are not paid or not paid fully as they will be marked 'Paid for...' and returned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 17138] New: UpdateFine() modyfies existing fine records even when there is no need
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '24

19 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17138 Bug ID: 17138 Summary: UpdateFine() modyfies existing fine records even when there is no need Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4/Overdues.pm: 574: # we're updating an existing fine. Only modify if amount changed 577: if ( $data->{'amount'} != $amount ) { for some numbers (e.g. 5.60) the comparison in line 577 fails ($data->{'amount'} is decimal(28,6) i.e. a string, and $amount may be a floating point number with no exact binary representation). E.g. when the fine amounts are multiple of 0.20, it fails for the 33.3% of the amounts (on average). Depending on the fine charging settings, this may trigger unnecessary database writes (and a lot of them). If 'Fine Charging Interval' is 1 day, this has very little practical consequences (misc/cronjobs/fines.pl script is usually run once per day, and all fines need an increase anyway). But if the charging interval is longer, e.g. 7 days, in a given day amount changes only for the 1/7 of the fines (again, on average), and over 60% of the database writes would be redundant. To reproduce: 1) run misc/cronjobs/fines.pl 2) add warn "AMOUNT ".$data->{'amount'}." vs $amount"; below line 577 in C4/Overdues.pm 3) run misc/cronjobs/fines.pl again 4) you'll see some warnings like 'AMOUNT 5.600000 vs 5.6' or: dump accountlines table after step 1), run the script 2nd time, dump the table again and compare the contents - some of the records would have a different timestamp. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 22403] New: Temporary Card
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '24

18 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22403 Bug ID: 22403 Summary: Temporary Card Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- We are CONSTANTLY having to write out patron card numbers on post-its for patrons that forgot their library cards. It would be great if there were an option under the print options on the patron page to print a temporary card. It could print the barcode and number, and maybe have an optional customizable message. Even better, since patrons are prone to leave these lying around, maybe it prints a temporary number that ISN'T their card number, but it is a temporary secondary number linked to their account that expires in X amount of hours. We could hand that out to them, providing of course they provide a photo id to prove who they are. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 23622] New: Add the ability to edit suspensions like fines would be edited.
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '24

17 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23622 Bug ID: 23622 Summary: Add the ability to edit suspensions like fines would be edited. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We want to be able to edit suspensions and see the suspension history of a patron on their circulation record, just as a fine and other charges would be in a library that charges fines. We want to be able to edit a suspension, to change the expiry date on it, to extend it, to waive it, or to mark it complete. In addition we need to be able to input a staff note as to the reason why this happened. This should be on the account tab on the Fines link from the lefthand navigation menu. The last thing we want any staff member to do is delete a suspension, as that gives a false report on the patron re returning materials to the library. At the moment we can only delete a suspension, but we may want to shorten it. If we delete it there is nowhere to record the reason why that is associated with the suspension. At the moment the suspension either remains or can be removed completely but often situations might arise where some compromise is required depending on circumstances. The ability to edit suspensions allows for greater flexibility in dealing with patron suspensions. Messy patron records result. Without the ability to edit it can mean greater difficulty in dealing with issues in relation to suspensions which in turn impacts on staff time and customer service and satisfaction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4