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

[Bug 15725] New: Merge permission
by bugzilla-daemon＠bugs.koha-community.org 25 Dec '24

25 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15725 Bug ID: 15725 Summary: Merge permission Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice if Koha had a permission to limit access to the merge records option (Merge selected button) on the addbooks.pl search results page and the virtualshelves/shelves.pl page (lists). This is especially important in a consortial catalog environment where many people have cataloging permissions, but most probably shouldn't have the ability to merge records. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16264] New: Confirm message on deleting an authority framework subfield
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16264 Bug ID: 16264 Summary: Confirm message on deleting an authority framework subfield Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org Just using this as an example because it appears in many places on the intranet Is there a reason that we navigate to a new page to confirm or cancel a delete rather than just using a Javascript confirm message? A JS message would use much less code. I realise that in the past we had a rule that everything had to work without JS enabled but a lot of stuff on the intranet wouldn't work at all without JS so I'm not sure how much that applies anymore. Anyway, just wondering if these extra pages for confirm or cancelling a delete are still necessary or if we can do this via JS now :) -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 15728] New: Hide component parts from search result
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '24

19 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15728 Bug ID: 15728 Summary: Hide component parts from search result Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org Add an option to hide component parts from search results. When searching for a song, we may want to see album results only (albums where the song appears). This option would help the process of seeing if a song is on an album that is available. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 16223] New: Automatically remove any borrower debarments after a payment
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16223 Bug ID: 16223 Summary: Automatically remove any borrower debarments after a payment 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: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries debar Borrowers at the end of the year for having unpaid fines, like in Bug 15157. Currently librarians have to manually remove this type of debarments after Borrower has paid his/her fines. Add a system preference to define debarments that should be automatically removed after a payment is made, and add functionality to actually remove the defined debarments from Borrower. Also let libraries to define the amount of outstanding fines after payment after which the debarment will be removed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 152

[Bug 15854] New: Possible race condition for sending renewal notices
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15854 Bug ID: 15854 Summary: Possible race condition for sending renewal notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Renewal notices are sent as digests - all renewed items are collected in one e-mail that is sent out with the process_messagequeue. We have a library, where sometimes this doesn't work. Instead of one single e-mail notice to the patron for one 'process_messagequeue' interval, multiple renewal notices are generated. The majority of e-mails is generated correctly. Looking at the code, this is about how it works: - AddRenewal is exectuted per item and calls - SendCirculationAlert which calls - C4::Message->find_last_message to help decide if a new notice has to be generated or an existing one can be amended In order to test this, you need: - EnhancedMessagingPreferences - Check-out notice checked for the patron you test with - RenewalSendNotice activated - A notice called RENEWAL As I see no problem in the logic so far, I think it could be a race condition where find_last_message doesn't find an existing notice (yet)? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 16089] New: Acquisitions -> Invoice broken by Bug 15084
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16089 Bug ID: 16089 Summary: Acquisitions -> Invoice broken by Bug 15084 Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/acqui/invoice.pl?invoiceid=X OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org I'm getting an error from acqui/invoice.pl: Software error: Can't use string ("Koha::Acquisition::Currency") as a HASH ref while "strict refs" in use at /Koha/Object.pm line 248. git bisect points to Bug 15084 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 15684] New: can't import quotes
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15684 Bug ID: 15684 Summary: can't import quotes Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 47358 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=47358&action=ed… sample quotes We can't seem to import quotes anymore. I just did on 3.20, but in 3.22 when the file loads up clicking the 'save' button does nothing. This happens on a few sites. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 15869] New: change framework on overlay
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15869 Bug ID: 15869 Summary: change framework on overlay Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you stage files for import you can choose how to handle matches. One option is to replace the existing record. The problem is that many libraries use this option to load a fuller record over a quick or fast record and the framework doesn't change. So you can choose the framework before importing but that framework only applies to new records, it doesn't update records that are being replaced or overlaid. We should fix that to update the framework for all items, not just new ones. Nicole -- You are receiving this mail because: You are watching all bug changes.

1 52

[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 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