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

[Bug 22346] New: Populate items.booksellerid when creating items in serials
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '24

18 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22346 Bug ID: 22346 Summary: Populate items.booksellerid when creating items in serials Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- When creating items for serials via the serials module, a lot of the fields are preset, but items.booksellersid is not automatically set to the id of the subscription's vendor. It would be nice if this could be added as it will help with statistics, especially if the vendor changes in the lifetime of a serial subscription. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27966] New: Fix plural handling for AUTO_RENEWALS_DGST message
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '24

18 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27966 Bug ID: 27966 Summary: Fix plural handling for AUTO_RENEWALS_DGST message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 18532, 27829 AUTO_RENEWALS_DGST does not handle properly plural vs singular error and success messages. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18532 [Bug 18532] Messaging preferences for auto renewals https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27829 [Bug 27829] [OMNIBUS] Remove specific LANG installer data -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 20340] New: Ability to use authentication plugin
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '24

18 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20340 Bug ID: 20340 Summary: Ability to use authentication plugin 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: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org This enhancement intends to allow adding and use authentication plugins. A plugin can be enabled with a system preference (AuthenticationModule) and placed in the <pluginsdir> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 93

[Bug 18886] New: Restructure storage of circulation rules to reduce complexity and enable increased flexiblity
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18886 Bug ID: 18886 Summary: Restructure storage of circulation rules to reduce complexity and enable increased flexiblity 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This report is an omnibus bug for the Circulation Rules Revamp as defined on the wiki ( https://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backen… ) The rough outline to complete this is as follows: 1) Create new circ rules table that will eventually replace all existing rule tables including but not limited to: issuingrules branch_borrower_circ_rules branch_item_rules default_borrower_circ_rules default_branch_circ_rules default_branch_item_rules default_circ_rules refund_lost_item_fee_rules 2) Transfer circ rules behavior over to the new table one rule at a time ( or as groups of logically connected rules ) in separate bug reports / patch sets to make testing and qa. The interface will remain unaltered at this point. 3) Update the rules editor interface to allow more flexibility in the way rules are set, solve the issue of the "ever widening" rules table 4) Unleash the full power of the Koha's circulation rules by "decoupling" the rule sets. At the moment, a full set of rules is tied to each branch/borrower/item combo. Even if all the rules except a single column are the same, a full set is currently created for each combination. We should be able to set all the rules for */*/* *except* for that single rule ( e.g. loan length ) thus greatly simplifying the rules needed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 37079] New: Searching a column in the Item Search table requires the authorized value code
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37079 Bug ID: 37079 Summary: Searching a column in the Item Search table requires the authorized value code Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Go to Item Search and do a search. 2. Under the ItemType column attempt to do a search such as "Books". It shows "No data available in the table" even though "Books" is an available item type. 3. Attempt to do the same search using "BK", which is the item type code for "Books". This will filter the column for just "Books". This is also affecting the shelving location. Previously both those columns had a dropdown for selecting the search filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 35628] New: Add additional statuses to catalog concerns
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35628 Bug ID: 35628 Summary: Add additional statuses to catalog concerns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The catalog concerns system currently only supports 'open' and 'resolved' states. We should allow for a more fine-grained approach to these ticket workflows.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 126

[Bug 26471] New: Datatables js error on missing pdfmake.min.js.map
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26471 Bug ID: 26471 Summary: Datatables js error on missing pdfmake.min.js.map Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing this error in the Firefox console on a page with a datatables table (e.g. admin/z3950servers.pl) Fout bij brontoewijzing: Error: request failed with status 404 Bron-URL: https://dev.rijkskoha.nl:28443/intranet-tmpl/lib/datatables/datatables.min_… Brontoewijzings-URL: pdfmake.min.js.map Compare with an older mention of this error from bug 15400: > I'm getting a different error that I'm not sure how to fix > > Source map error: Error: request failed with status 404 > Resource URL: > http://localhost:8081/intranet-tmpl/lib/datatables/datatables.min_19.1200060. > js > Source Map URL: pdfmake.min.js.map I am kind of lost in datatables land. It is a nightmare component imo. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 37195] New: Add ILL as option to TrackLastPatronActivityTriggers
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 Bug ID: 37195 Summary: Add ILL as option to TrackLastPatronActivityTriggers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com This has a couple of tricky aspects to it, I think. Basically, the problem is that for some patrons their only activity in the library could be to request article copies/prints through ILL. At least the way it works in Sweden, with ILL based around Libris, an ILL reques for a book would update lastseen, when the book is issued to the patron. But a request for an article copy/print would not update lastseen, because the ILL is just handled in the Libris backend, and there is no loan or other activity that is tracked today. The solution is probably to update lastseen from the Libris backend when a copy/print is marked as received, like so: $patron->update_lastseen('activity'); But that "activity" needs to be activated in TrackLastPatronActivityTriggers. Questions: - Should we add a generic "ill" activity? Or would it make sense to have e.g. "ill_loan" and "ill_copy"? - Would it be OK to have "ill" listed as an activity for TrackLastPatronActivityTriggers even if the ILL module is not activated? - Would it make sense to have an activity in TrackLastPatronActivityTriggers that perhaps does nothing out of the box, but relies on the different backends to actually call update_lastseen? Or could the ILL module itself call update_lastseen, and not rely on the backends to do it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 33426] New: Add client storage of user-selected DataTables configuration to suggestion.tt
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33426 Bug ID: 33426 Summary: Add client storage of user-selected DataTables configuration to suggestion.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 22276 Bug 22276 added a method to columns_settings.inc to support the use of the DataTables "saveState" option. Making use of that function in suggestion.tt would enable the suggestion table to remember individual users' local changes to the table configuration. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22276 [Bug 22276] Add client storage of user-selected DataTables configuration -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 31181] New: Merge function does not include local copy images
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31181 Bug ID: 31181 Summary: Merge function does not include local copy images Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It seems that merge-from item local cover images are not merged to the merge-to entry. Is thie intentional or is it a bug? If intentinal there should be a warning to the user before the merge is performed, so that they may save the current images and re-locad them once the merging is complete. Are the images left in limbo, or are they deleted from the db once the merge is complete? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5