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

[Bug 37081] New: Add Order Confusing On acqui/addorderiso2709.pl page
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37081 Bug ID: 37081 Summary: Add Order Confusing On acqui/addorderiso2709.pl page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When staging or adding a new file to a basket in Acquisitions, on the acqui/addorderiso2709.pl? Next the items to select, there is an ADD ORDER button. At the bottom of the page there is a SAVE button. ADD ORDER does not add this item to the order, it starts a new blank order. I believe we should reword this button to say what it does, NEW ORDER instead. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34805] New: Add order search form to acq start page
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34805 Bug ID: 34805 Summary: Add order search form to acq start page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Triggered by discussion about bug 33662 we've discussed adding the order search form to the acquisition start page. This would be consistent with other module start pages that offer search options, like serials and patrons. It would also save some clicks. We've discussions some variations: * Generally the vendor search and pending suggestions on top were preferred * The order search could/should be shortened to take not up so much space * We could add less/more or a link to the full page * Ideally already entered search terms would be kept when switching to the full form page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 37022] New: Allowing holds on not for loan item types
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37022 Bug ID: 37022 Summary: Allowing holds on not for loan item types Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com - Long context: We have a number of items in our collection that are not for loan, but are available for reference. Some of them are in our closed stacks. (see Use Case in bug #35299 ) In order to consult those, our users should be able to place a hold on them from the OPAC. I am able to fix that for items that have an item type that is normally for loan by setting the "952$7 - Not for loan" status to a negative value, e.g. "-2" (from the authorized values NOT_LOAN). However, instead of setting a not for loan status for each item individually, we work with certain item types that are always not for loan on the item type level (by checking the "Not for loan" box in Administration > Item types). The "952$7 - Not for loan" status for these is "0" and it doesn't help to change it to "-2", as the not for loan status is apparently stored elsewhere because of the item type. So, a hold cannot be placed on these items. We could make the item type for loan and change the status for each item individually, but that creates other issues. E.g. during Covid time items could not be consulted in the library, so all items where exceptionally made available for loan. This was 'easy' to do, as we just needed to add a specific circulation rule for those item types and then uncheck the box for the item type to make it for loan. Afterwards we just needed to tick the box again. It has happened another time because of other exceptional circumstances that we needed to make all items temporarily for loan and it might happen again in the future. - Enhancement request: Is it possible to add an extra option to the 'not for loan' status on item type level for items that are not for loan but holdable? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31304] New: Add ability to customise availability searching
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31304 Bug ID: 31304 Summary: Add ability to customise availability searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently in Zebra 'limit to available' means: ## 'available' is defined as (items.onloan is NULL) and (items.itemlost = 0) Bug 25375 proposed for ES a slightly wider net: 783 onloan => undef, 784 notforloan => 0, 785 withdrawn => 0, 786 itemlost => 0, 787 damaged => 0 We should have a configuration for this, a way to allow libraries to decide which statuses are available/unavailable -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 27973] New: Limit to currently available items should have an option to filter out notforloan statuses
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27973 Bug ID: 27973 Summary: Limit to currently available items should have an option to filter out notforloan statuses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many libraries find it problematic that the 'Limit to currently available' does not filter out notforloan statuses (example: ordered). It would be handy if there was a system preference that allowed librarians to choose which notforloan statuses could be filtered out. to recreate one potential problem: -do an OPAC search that includes some items with a notforloan of -1 (ordered) -click 'Limit to currently available items' -the ORDERED items remain this can be frustrating for a patron who could reasonably assume that after clicking the 'Limit to currently available' filter they would be looking only at items that are currently available to them to checkout -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 27340] New: We should introduce Koha::PickupLocation(s)
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27340 Bug ID: 27340 Summary: We should introduce Koha::PickupLocation(s) 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Looking at the codebase, a pickup location is a combination of a branch/library, and now also a 'desk'. So it would make sense to have a special class for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 26915] New: Koha explodes when writing off a fee with FinePaymentAutoPopup
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26915 Bug ID: 26915 Summary: Koha explodes when writing off a fee with FinePaymentAutoPopup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org - To test activate FinePaymentAutoPopup - Create a manual fee - Write it off using the write off button on the account line (not below table) - Experience error on saving the writeoff http://localhost:8081/cgi-bin/koha/members/printfeercpt.pl?action=print&acc… Can't call method "unblessed" on an undefined value at /home/vagrant/kohaclone/members/printfeercpt.pl line 64 This problem was first found in 20.05.03 so affects stable releases as well! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 38013] New: Some return messages in returns.tt lack specific classes
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38013 Bug ID: 38013 Summary: Some return messages in returns.tt lack specific classes Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Most of the messages that Koha might display on the checkin page have distinct classes. We do not apply a specific class when a checkout had an issue note: https://github.com/Koha-Community/Koha/blob/b4054dbb1578349cd1b8caa8fac9cbe… Or when the patron has fines: https://github.com/Koha-Community/Koha/blob/b4054dbb1578349cd1b8caa8fac9cbe… We should do so in both cases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 38156] New: Auto renew cron job mangles digest notices when parallel processing is enabled
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '24

20 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38156 Bug ID: 38156 Summary: Auto renew cron job mangles digest notices when parallel processing is enabled Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 29507 When the automatic renewal cron job is running multiple loops simultaneously, it aims to process all of the renewals for any given patron together in one chunk, in order to avoid data conflicts. To accomplish this, it starts a new data chunk each time it encounters a new patron. However, in practice, all of a patron's checkouts for a given day might not end up being consecutive in the database table if multiple patrons are using different checkout stations at the same time. (Or if differing circulation rules cause checkouts from different days to auto-renew at the same time.) If a patron's checkouts are not all consecutive in the database, they will end up being split over separate chunks. This causes digest notices not to generate correctly - depending on how the timing works out, a patron may get their renewals split over multiple digests, some renewed items may be missing from digests, or the digest may not generate at all. Sorting the issues by borrowernumber before splitting them into chunks for processing should solve this. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29507 [Bug 29507] Speed up auto renew cronjob via parallel processing -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 34546] New: Report group code should only contain ASCII chars
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '24

20 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34546 Bug ID: 34546 Summary: Report group code should only contain ASCII chars Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When creating a new report, one can create a new report group. Since its code will be used in tab id attribute, it should be tested to contain only ASCII chars (and no space) : [a-zA-Z0-9_-] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3