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

[Bug 22831] New: Elasticsearch - add a maintenance script for checking DB vs index counts
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '25

15 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22831 Bug ID: 22831 Summary: Elasticsearch - add a maintenance script for checking DB vs index counts 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: nick(a)bywatersolutions.com Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 32499] New: HOLDPLACED email goes to patron branch rather than item branch
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '25

14 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32499 Bug ID: 32499 Summary: HOLDPLACED email goes to patron branch rather than item branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The HOLDPLACED email is sent out if "emailLibrarianWhenHoldIsPlaced" is enabled. Currently, it is sent to the patron's branch, but it seems to me (and my librarians) that it would make more sense to be emailed to the item's branch, since that's the branch where the librarian is going to be able to do something about it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 29924] New: Introduce password expiration to patron categories
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29924 Bug ID: 29924 Summary: Introduce password expiration to patron categories 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 119

[Bug 34477] New: Further reduce memory usage for idle background job worker
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34477 Bug ID: 34477 Summary: Further reduce memory usage for idle background job worker 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org While bug 28413 reduced the amount of memory used by background job worker, I think that we can reduce it further yet. I'm seeing a lot of workers around 56MB RES and 104MB VIRT at the moment (although there are some smaller ones). Multiple that for multiple workers across multiple instances, and it adds up pretty quickly. Contrast that with bug 27267 where I've got an idle Zebra indexer that uses 7MB RES and 12MB VIRT. That scales up much nicer. Anyway, not a burning issue, but it would be useful to do sometime down the track. It could be an easy win for server resource usage. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31050] New: Standardize session setup
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31050 Bug ID: 31050 Summary: Standardize session setup 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We should have 1 function that sets up the basics of a $session object which we can use across all our different authentication options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 29678] New: Can't use exteral URL for XSLT stylesheet
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29678 Bug ID: 29678 Summary: Can't use exteral URL for XSLT stylesheet Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org If I try to specify an external URL as an XSLT stylesheet it doesn't work. In the error logs I see messages like this: [2021/12/10 12:37:50] [WARN] XSLT::Base: Could not create file parser context for file "https://path/to/MARC21slim2intranetResults.xsl": No such file or directory at /kohadevbox/koha/Koha/XSLT/Base.pm line 330. I have verified that the .xsl file is accessible and that internal links (to MARC21slimUtils.xsl for instance) are valid too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 20581] New: Allow manual selection of custom ILL request statuses
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20581 Bug ID: 20581 Summary: Allow manual selection of custom ILL request statuses 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 Currently the displayed status of any given ILL request is strictly prescribed by where it is in the workflow, as defined in the ILL module. While this gives an accurate indication of the current status of a request, it does not allow for any local variation in the displayed status, which can be limiting for the end user. This bug proposes adding the ability for the admin, via a syspref, to define a custom set of request statuses, which can be selected for display by the manager of an ILL request. These statuses work alongside the existing "workflow" status that an ILL request has and will, if selected, override *for display* the status of that request. This proposal will allow the ILL module to continue to strictly prescribe and manage the workflow of requests, but will also allow the end user some flexibility in the display of a given request's status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 245

[Bug 27255] New: Authorized values does not allow you to provide a description for the category
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27255 Bug ID: 27255 Summary: Authorized values does not allow you to provide a description for the category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 I am noticing that AV has descriptions for the categories that come with Koha, but when you create a category, you are not allowed to provide a description. This is probably an oversight, but I think it would be great if we could add descriptions to new or existing categories. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25999] New: Renewal due date not being honoured for items with holds
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25999 Bug ID: 25999 Summary: Renewal due date not being honoured for items with holds Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hc(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 7088 added the ability to override renewals for items that have holds by adding the "AllowRenewalOnHoldOverride" syspref. When this sys. pref. is enabled and the "Override renewal restrictions" option is ticked on the checkouts table on a patron account and then an "on hold" item is selected in the renewal column the "On hold due date" box appears. This allows a renewal date to be applied to items with holds on them. For the most part, it works except in one scenario: A new date is selected in the "Renewal due date" box. This also populates the "On hold due date" box. The content in the "On hold due date" box is deleted. The selected items are renewed. The due date for the items with holds reverts to the parameters set for the patron category/item type combination in the fine and circulation rules. According to bug 7088 the item should be "renewed by falling back to the "Renewal due date" value if a value is not specified in the "On hold due date" input box"" Has anyone else had this issue? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 26135] New: MARCItemFieldsToOrder should use "location" rather than "loc"
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26135 Bug ID: 26135 Summary: MARCItemFieldsToOrder should use "location" rather than "loc" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the syspref description for MARCItemFieldsToOrder, one is instructed to enter database field names. However, the syspref requires one to use "LOC" rather than the field name "location" for shelving location. We should use "location" here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1