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

[Bug 26195] New: Add a way to specify authorised values should be expanded [OAI]
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26195 Bug ID: 26195 Summary: Add a way to specify authorised values should be expanded [OAI] Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It is not uncommon to prefer descriptions to codes when exposing the library data through OAI. I propose we add a configuration option (off by default) that allows such a thing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 17536] New: Remove Duplication of receipting code in EDI
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '24

15 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17536 Bug ID: 17536 Summary: Remove Duplication of receipting code in EDI 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When the Current Koha/EDI.pm was written the api to Acquisitions::ModReceiveOrder was unstable as a result the process was duplicated in Koha::EDI as the interface has stabilised EDI should revert to using the Acquisitions interface and remove the duplicate code. This should guard against bugs from incompatibilities and allow it to take advantage of enhancements in C4::acquisitions (e.g. new handling of Standing Orders) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 26802] New: Improve speed with records with many items
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '24

14 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26802 Bug ID: 26802 Summary: Improve speed with records with many items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org Koha has a performance problem displaying records with many items in search results and details pages. For example, Koha takes around 20/30 seconds to process a record XML with 1000 items using XSLT. The Koha's response speed reduces even more with bigger items counting. Maybe we can improve Koha speed with some decisions: - Don't use the complete XML (record without items) for XLSTs processing. - Add pagination to the items table (like is done with other Koha tables) and JS load. Test case (search results): - Add some records with 1000 items and the same title - Try to do a search for the title Test case (details and other record views): - Add one records with 1000/2000/3000 items - Try to open the record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 26654] New: Add item number column to item search results
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '24

11 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26654 Bug ID: 26654 Summary: Add item number column to item search results 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 When doing an item search some libraries would find it useful if there was a column showing the item number -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 16002] New: ALL/MULTI choices in report dropdowns
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '24

11 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16002 Bug ID: 16002 Summary: ALL/MULTI choices in report dropdowns 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org When adding choices like <<branches>> to a report, it would be great if parameter could be added to the choice where ALL could be a choice at the top of the list. Maybe something like <<branches{ALL}>>. Similarly, it would be great if MULTI could also be a parameter, where the user could select several items from the list, like <<branches{MULTI}>>. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 26692] New: Add barcode image generator service for OPAC
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '24

11 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26692 Bug ID: 26692 Summary: Add barcode image generator service for 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would like to add a scannable barcode to the patron self service area of the opac for patrons who do not have their library cards with them. The existing svc/barcode on the staff side should work fine, but requires a staff login. It makes sense to duplicate this script but only require a valid patron login to use it. -- You are receiving this mail because: You are watching all bug changes.

1 59

[Bug 21530] New: overdue_notices.pl aborting because error is not caught
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '24

09 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21530 Bug ID: 21530 Summary: overdue_notices.pl aborting because error is not caught Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Saw this triggered by a situation where a branch had been removed but some rules remained. However when doing a lookup the return should always be tested for validity. Because it wasnt when methods were called on null the overdues_notices process aborts with a runtime error and subsequent branches overdues are not processed. Untested returns are one of the biggest causes of errors and often hard to track down errors in the system . -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 16201] New: Tie automatic cancellation of holds to a system preference to allow easier configuration
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '24

09 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16201 Bug ID: 16201 Summary: Tie automatic cancellation of holds to a system preference to allow easier configuration 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, if you run multiple instances on a server, you can not easily configure for some, but not others, that holds not picked up will automatically cancelled. The cronjob used is: misc/cronjobs/holds/cancel_expired_holds.pl If it's scheduled, the feature is active for all instances - or you'd have to maintain a list, change the default cron files etc. It would be nice if this feature was tied to a new system preference, so that you can easily activate/deactivate it from within Koha and without accessing the server. This might also be useful for libraries that want to wait a little longer with cancelling in some cases, for example after a holiday period or when the library has been closed for a while. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24491] New: Add filters to debit types interface
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '24

08 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24491 Bug ID: 24491 Summary: Add filters to debit types interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On cgi-bin/koha/admin/debit_types.pl, we have the option to filter down to only user-defined debit types, hiding those defined by the system. It would be helpful to also be able to filter to only those flagged for manual invoice and only those flagged for purchase. If we had a filter for purchasable items, we could then make the link off of the point of sale page point to debit types with that filter enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 26376] New: Add itemnumber to writeoffs
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '24

08 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26376 Bug ID: 26376 Summary: Add itemnumber to writeoffs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org See: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17894#c8 After careful consideration our position on this has changed. We believe we should be recording the itemnumber for writeoffs where we can, libraries use this information for reporting and tracking -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2