November 2022 - Koha-bugs - lists.koha-community.org

[Bug 30696] New: Customized Templates for Patron Setup by Branch
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30696 Bug ID: 30696 Summary: Customized Templates for Patron Setup by Branch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great for consortiums (especially the combined Public, k-12 and academic libraries) for Koha to allow for individual branches to determine what fields are mandatory and should display for patron registration as opposed to having this be a global setup option. This would include, borrowermandatoryfield, borrowerunwantedfields and CollapseFieldsPatronAddForm- if these preferences could be set up at the branch level, that would be ideal for libraries in a consortium to uniquely identify what they need during patron registration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20185] New: Some scripts does not pass perl -wc
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20185 Bug ID: 20185 Summary: Some scripts does not pass perl -wc Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: normal 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 -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 16105] New: Cache::Memory is loaded even if memcache is used
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16105 Bug ID: 16105 Summary: Cache::Memory is loaded even if memcache is used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW 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 Depends on: 11998, 16104 Cache::Memory is loaded and Koha::Cache::_initialize_memory is called even if a memcached cache has been correctly initialize, it does not make sense. It should only be initialize if needed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11998 [Bug 11998] Syspref caching issues https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 [Bug 16104] Warnings "used only once: possible typo" should be removed -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 16104] New: Warnings "used only once: possible typo" should be removed
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 Bug ID: 16104 Summary: Warnings "used only once: possible typo" should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal 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 Since bug 11998, the following warnings are raised: Name "Tie::Hash::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::LRU::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. It comes from the Koha::Cache 103 if ( can_load( modules => { 'Cache::Memory' => undef } ) ) { -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 21955] New: Cache::Memory should not be used as L2 cache
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21955 Bug ID: 21955 Summary: Cache::Memory should not be used as L2 cache Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: critical 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 If Plack is running with several workers we must not use Cache::Memory as L2 cache. If a value is set from a worker, it will not be available from other workers as the Cache::Memory instance is not shared (of course!) Moreover we now have Koha::Cache::Memory::Lite that does the same job, so we should not expect performance regressions by removing it. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 27923] New: Inventory tool should be able to skip lost items
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '25

17 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27923 Bug ID: 27923 Summary: Inventory tool should be able to skip lost items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the inventory tool, the "Optional filters for inventory list or comparing barcodes" section allows one to filter results to only consider items with certain lost values. However, there isn't an option to only look at items with no lost status. We should have a "Skip lost items" checkbox, as we have "Skip items on loan" and "Skip items on hold awaiting pickup." If a library is reasonably sure that their lost items will not be on the shelf, they should have the option to just not interact with them in inventory. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 32328] New: Add ability to specify how long an item stays on a library's holds queue
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '25

17 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32328 Bug ID: 32328 Summary: Add ability to specify how long an item stays on a library's holds queue Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With multi-location libraries that are open varying hours, it would be helpful to be able to specify how long an item appears on a library's hold queue before the item appears on another location's queue. For example, Title A is available at both Library D and Library E. The patron wants to pickup the item at Library D. Library D is closed Saturday and Sunday, but Library E is not. Currently, the item could potentially show on Library E's hold queue. Since it takes three days of transit time to move the item from Library E to Library D, it would be faster to fill the hold from Library D, but because it was moved off Library D's queue, it won't be filled there. It would be nice to be able to specify by Library how long an item will appear on the holds queue for that library before it is moved, and the item is sent from another library. Using Holds Queue Skip Closed (and the other associated sys prefs) does not address this sufficiently. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 16196] New: Acquisitions Module Not Showing Subtotals
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '25

17 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16196 Bug ID: 16196 Summary: Acquisitions Module Not Showing Subtotals Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: amy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Partner reports that when receiving books in the Acquisitions module, subtotals are not identifying which fund they are for. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22531] New: Allow for multiple requests to partners and display partners in audit log
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22531 Bug ID: 22531 Summary: Allow for multiple requests to partners and display partners in audit log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- Currently, when an ILL request is sent to partners it is not possible to send to further partners, should the first partner not be able to fulfil the request. A better approach would be to allow the "Place request with partners" option to be selected even when this action has already taken place. This will allow the user to try multiple partners subsequently. As such, we should log which partners a request has been sent to and this information should be displayed in the "Display request log" functionality added in Bug 20750 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 27444] New: Allow reports to use the calendar to count open/closed days based on the calendar
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27444 Bug ID: 27444 Summary: Allow reports to use the calendar to count open/closed days based on the calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When writing reports related to fines or overdue notices, one runs into difficulties based on how Koha holidays are stored. There's no good way for SQL to calculate out how many days within a given span were open days. So if you're using the calendar to calculate when to send overdue notices at 10 open days past the due date, there's no way to get SQL to tell you which items should have gotten an overdue notice today. This becomes more of an issue as we use the patron emailer more, since the patron emailer relies upon a report. If one wanted to use the patron emailer to send a fourth overdue notice, one would not be able to calculate when to send that notice using the Koha calendar. I'm not sure what the solution is here. Maybe some syntax one could use in a report to ask Koha to generate a value? So you could say something like: WHERE timestampdiff(days,date_due,curdate()) = <<opendays:date_due,curdate()>> ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3