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

[Bug 17815] New: Problems with search for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17815 Bug ID: 17815 Summary: Problems with search for dateaccessioned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Tested this as described in bug 14861: Search from advanced search by accession date: 2011-09-01 - 2011-09-30 9461 results Searched with SQL: select distinct biblionumber from items where dateaccessioned between '2011-09-01' and '2011-09-30' 805 results The date range search doesn't seem to work right. The search for a single date appears to work correctly. It's also possible to truncate dates using *. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 27945] New: Limit the number of article requests per day per patron category
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27945 Bug ID: 27945 Summary: Limit the number of article requests per day per patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We propose adding an "Article Request Limit" field to the patron category configuration. "Allow __ article requests per day" This limit would be enforced by querying the existing article requests in the database that have been placed during the day and allowing the patron to proceed or deny the request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 172

[Bug 33292] New: Claim Return doesn't refund lost item charge when MarkLostItemsAsReturned includes "When marking an item as a return claim" and "Refund lost item fee" is on
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33292 Bug ID: 33292 Summary: Claim Return doesn't refund lost item charge when MarkLostItemsAsReturned includes "When marking an item as a return claim" and "Refund lost item fee" is on Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using Claim Return, if an item has already been charged as Long Overdue (lost) it does not get refunded when a claim is made, even if lost item fee refund on return policy is set to "Refund" and MarkLostItemsAsReturned includes "When marking an item as a return claim" Since the library is not actually checking the item in it doesn't refund automatically. The library could check the item in and not resolve the claim, but that's an extra step and may not work with all workflows. Having the option to refund the lost fee on claim would be helpful for many libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 26777] New: Give the user the option to display their patron card barcode from the OPAC
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26777 Bug ID: 26777 Summary: Give the user the option to display their patron card barcode from the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In this modern age, people are moving away from carrying cards.. but they nearly always have their smart phone to hand. It would be nice to be able to display your barcode for scanning at self service machines directly on your phone. -- You are receiving this mail because: You are watching all bug changes.

1 95

[Bug 31787] New: [DOCS] Add description and examples to membership_expiry.pl about --where option
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '25

10 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31787 Bug ID: 31787 Summary: [DOCS] Add description and examples to membership_expiry.pl about --where option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org An optional `--where` parameter was added to the `membership_expiry.pl` cronjob in 21.11. This allows for arbitrarily complex SQL where statements to be passed to the script to filter affected patrons. Add some additional information about this, and some examples on how to construct SQL queries, for example: to restrict to patrons in a specific category. See IRC discussion: http://irc.koha-community.org/koha/2022-10-14#i_2456049 See bug 28456. Topic affected: https://koha-community.org/manual/22.11/en/html/cron_jobs.html#notify-patro… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 23732] New: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '25

10 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23732 Bug ID: 23732 Summary: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 28075] New: Add missing UNIMARC for coded data 135a
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '25

10 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28075 Bug ID: 28075 Summary: Add missing UNIMARC for coded data 135a Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Bibliographic data support Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Value are missing in unimarc_field_135a.tt cf: https://www.transition-bibliographique.fr/wp-content/uploads/2018/07/B135-6… -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 33259] New: Optionally set SameSite attribute of cookie to Strict
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33259 Bug ID: 33259 Summary: Optionally set SameSite attribute of cookie to Strict Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSi… We should offer a system preference so that libraries who'd like to increase their security can set the SameSite attribute of the session cookie to Strict, rather than the default Lax. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 82

[Bug 28285] New: Lists sorted by copyrightdate display results in ascending date order
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '25

08 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28285 Bug ID: 28285 Summary: Lists sorted by copyrightdate display results in ascending date order Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you create a list and choose to sort by copyrightdate the list results will display on both staff interface and opac in ascending date order (oldest first). It would be useful to be able to choose ascending or descending as the default as often libraries will want the newest items to appear first. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27526] New: Remove Mod/AddItemFromMarc from additem.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '25

04 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27526 Bug ID: 27526 Summary: Remove Mod/AddItemFromMarc from additem.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org There is a lot of code in additem.pl that is transforming an item representation from/to HTML, XML, MARC::Record, Koha::Item We really don't need all this overhead, having the Koha::Item's attributes would be enough to update/create the item into the DB (it's no longer in the biblio MARC::Record!) Of course other places where we add/update items are valid as well: acquisition, batch item modification, etc. -- You are receiving this mail because: You are watching all bug changes.

1 203