January 2021 - Koha-bugs - lists.koha-community.org

[Bug 21712] New: Report anonymized patron records
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '25

19 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21712 Bug ID: 21712 Summary: Report anonymized patron records 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See bug 21336 comment17. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 26884] New: overdue_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 18 Feb '25

18 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26884 Bug ID: 26884 Summary: overdue_notices.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz command line script overdue_notices.pl should 1. moved to a module (see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16063) 2. refactored/cleaned up most importantly 3. made idempotent this could be achived via a checksum/signature including the "defining" fields for the message ie borrowernumber subject content metadata letter_code message_transport_type to_address from_address reply_address content_type so before a message is created a checksum is calculated and a look-up in the database is done whether the message already exists (maybe be ignored via a flag) so no matter how often or "how/too late" the script is executed, no message is "forgotten"/send multiple times -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

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

14 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 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 12 Feb '25

12 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

[Bug 27492] New: Need ability to define hold pickup branches per patron category
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27492 Bug ID: 27492 Summary: Need ability to define hold pickup branches per patron category Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Need possibility to define hold pick up branches per patron category. Case example: our university library is open for all, but we have a lot self service hours when only faculty staff or students have access to library. Our main campus library has most service hours and we would like to define that patrons having category "other" could only choose main library as their pickup place. (although they are able to make a hold to all of our collection at any campus). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 26610] New: Add 'NULL' option to report value dropdowns
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '25

11 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26610 Bug ID: 26610 Summary: Add 'NULL' option to report value dropdowns 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Sometimes you may want to have a report optionally limit to an itemtype or branch etc. Sometimes you may want to pick NULL from that dropdown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 17898] New: Add a way to automatically convert SQL reports
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17898 Bug ID: 17898 Summary: Add a way to automatically convert SQL reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Bug 17196 move the marcxml out of the biblioitems table. That will break SQL reports using it. It would be handy to propose an automagically way to convert the SQL reports. -- You are receiving this mail because: You are watching all bug changes.

1 37