March 2019 - Koha-bugs - lists.koha-community.org

[Bug 19192] New: Update default DUEDGST and PREDUEDGST notices
by bugzilla-daemon＠bugs.koha-community.org 27 Jul '23

27 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19192 Bug ID: 19192 Summary: Update default DUEDGST and PREDUEDGST notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The current default digest notices are DUEDGST You have <<count>> items due PREDUEDGST You have <<count>> items due soon These are not terribly useful defaults -- the whole reason for having digest notices is to display item detail for items which are due or coming due. I suggest the following instead: DUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due: <<items.content>> PREDUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due soon: <<items.content>> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 20454] New: Suspend Holds if patron wouldn't be able to check items out
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20454 Bug ID: 20454 Summary: Suspend Holds if patron wouldn't be able to check items out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a person can't check out an item due to hitting the fine limit, it would be great if the holds could be suspended automatically so it wasn't filled until the account was cleared off. This would be a good system preference so systems that didn't want to use it wouldn't be forced into it. Currently in our system patrons can't check out if they have more than $5 in fines. Sometimes they place a hold, rack up fines, and can't check out the book when it comes in for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18855] New: Fines cronjob can cause duplicate fines if run during active circulation
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18855 Bug ID: 18855 Summary: Fines cronjob can cause duplicate fines if run during active circulation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On systems with a decent amount of fines it seems the fines cron can cause issues for patrons. The problem seems to be: 1 - Fines job runs and selects overdues 2 - Patron with an overdue returns books, fine is updated, item is checked in 3 - Fines job iterates to the item that was checked in during step 2, sees there is no accruing fine, generates a new accruing fine I am not sure what the best solution here is, possibly we should confirm the issue before generating the fine in the cronjob? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 20108] New: Hold Queue Timeout
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '23

13 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20108 Bug ID: 20108 Summary: Hold Queue Timeout Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 It would be good if there were a preference to set a Hold Queue Timeout, where a hold request goes to a branch queue for X amount of days, and if it isn't filled, it goes to the next library queue according to the cost matrix, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15708] New: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '23

13 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15708 Bug ID: 15708 Summary: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This enhancement will extend the functionality added in Bug 15532 using the library groups editor in Bug 15707 to allow not only holds from a single library match but a group of libraries that match. This will give much greater flexibility in defining what items should full what holds within a groups of libraries. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 22284] New: hiding libraries outside group for holds dev
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '23

13 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22284 Bug ID: 22284 Summary: hiding libraries outside group for holds dev Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- hiding libraries outside group for holds dev -- You are receiving this mail because: You are watching all bug changes.

1 472

[Bug 16436] New: Allow action logs to be logged to the koha log file
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16436 Bug ID: 16436 Summary: Allow action logs to be logged to the koha log file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be very useful if it were possible to log actions to a log file as well as to the database. With Koha::Logger we can give the option of sending those logs to a separate file, but by default they can go to the standard log files. They should also be off by default. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 16865] New: marking branchcode unwanted breaks self registration
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16865 Bug ID: 16865 Summary: marking branchcode unwanted breaks self registration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you add branchcode to PatronSelfRegistrationBorrowerUnwantedField then self registration fails silently. The library and the user have no idea what happened. We should have an error and/or not let branchcode be added to that preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 17364] New: branchcode should not be allowed in BorrowerUnwantedField , PatronSelfRegistrationBorrowerUnwantedField
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17364 Bug ID: 17364 Summary: branchcode should not be allowed in BorrowerUnwantedField, PatronSelfRegistrationBorrowerUnwantedField 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If branchcode is among the fields in BorrowerUnwantedField, saving the borrower record in members/memberentry.pl will generate an Internal Server Error because there is a foreign key constraint on borrowers.branchcode. To replicate the issue: 1/ Set the syspref BorrowerUnwantedField so that it contains branchcode 2/ Create a patron on members/memberentry.pl 3/ Save the patron, you will get "Internal Server Error". It follows that PatronSelfRegistrationBorrowerUnwantedField should not contain branchcode either -- it's necessary to create a record in the borrowers table, so we shouldn't be able to exclude it. Details for those who like that sort of thing: If you're watching the plack error logs,you'll see something like this: DBD::mysql::st execute failed: Cannot add or update a child row: a foreign key constraint fails (`koha_salinas`.`borrowers`, CONSTRAINT `borrowers_ibfk_2` FOREIGN KEY (`branchcode`) REFERENCES `branches` (`branchcode`)) [for Statement "INSERT INTO `borrowers` ( `address`, `address2`, `borrowernotes`, `cardnumber`, `categorycode`, `city`, `contactnote`, `country`, `dateenrolled`, `dateexpiry`, `dateofbirth`, `debarred`, `email`, `emailpro`, `fax`, `firstname`, `initials`, `mobile`, `opacnote`, `othernames`, `password`, `phone`, `phonepro`, `privacy`, `sex`, `sort1`, `sort2`, `state`, `surname`, `title`, `userid`, `zipcode`) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )" with ParamValues: 0="1234 MAIN ST", 1="", 2="", 3="TESTYTESTERSON", 4="STAFF", 5="Bradley, CA", 6="", 7="", 8='2016-09-27', 9='2024-12-27', 10=undef, 11=undef, 12="", 13="", 14="", 15="TESTY", 16="", 17="", 18="", 19="", 20='!', 21="555 555 1212", 22="", 23=1, 24="", 25="C", 26="", 27="", 28="TESTERSON", 29="", 30='testy.testerson', 31="93426"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. DBIx::Class::Storage::DBI::_dbh_execute(): Cannot add or update a child row: a foreign key constraint fails (`koha_salinas`.`borrowers`, CONSTRAINT `borrowers_ibfk_2` FOREIGN KEY (`branchcode`) REFERENCES `branches` (`branchcode`)) at /usr/share/koha/lib/C4/Members.pm line 769 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 22592] New: Elasticsearch - Support for index scan
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22592 Bug ID: 22592 Summary: Elasticsearch - Support for index scan Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi Target Milestone: --- We can emulate index scan at least to some extent by using faceting with an include filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 51