April 2025 - Koha-bugs - lists.koha-community.org

[Bug 39590] New: Better handling of fast add duplicates
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39590 Bug ID: 39590 Summary: Better handling of fast add duplicates 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See: Bug 37702 comment 2 Bug 39561 comment 3 One suggestion is that we should only apply the duplicate check to other fast add records. I suggest maybe we need something more. The situation here seems to be that a book has come to the desk and needs to be issued. It is a new copy of an existing title. The librarian with fast add enters title and author and a duplicate is found. I think there should be an option to add the new duplicate, but have it linked to the original record. I am thinking while we want the circulation to go smoothly, we also want an easy way for catalogers to see that there is a fast add duplicate of an existing record that likely needs to be merged -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 17643] New: The bug 3333 breaks intranet search results in column Location
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17643 Bug ID: 17643 Summary: The bug 3333 breaks intranet search results in column Location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: christophe.croullebois(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The Bug 3333 corrects in Opac by setting notforloan=1. But it has a side effect on intranet search result page due to the use of authorized value on 'notforloan'. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 30723] New: Allow for notices to have custom header/footer includes
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30723 Bug ID: 30723 Summary: Allow for notices to have custom header/footer includes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries like to add the same custom header/footer to many notices/slips. It would be handy if there was a way to set a custom header/footer and then call on it in each notice/slip where you'd like to have them. That way you would not have to add the same header/footer content to each notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 39527] New: Cannot create a new notice when running Koha as a Mojolicious application
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39527 Bug ID: 39527 Summary: Cannot create a new notice when running Koha as a Mojolicious application Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When running Koha as a mojolicious application, trying to create a new notice results in a CSRF error, because two different 'op' parameters are sent (one in the URL, one in the POST body) -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 27730] New: Innocent changes to framework silently delete bibliographic data
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27730 Bug ID: 27730 Summary: Innocent changes to framework silently delete bibliographic data Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P3 Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ian.bays(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you copy and change a framework and either delete a subfield in the new framework or mark the subfield tab as "ignore", then any bib data with data in that subfield, when saved in the new framework will be silently destroyed with no option to undo. Test Plan to confirm behaviour: 1. Create bib record in default framework with minimal data, but add tag 365 (as it has a number of subfields all visible) and populate subfields a through h with "fa" through "fh". Save the record and with sql check the contents of the metadata. (I found this SQL gives enough information substituting the correct bib number of the saved record: select tagfield, tagsubfield, frameworkcode, tab, hidden, (select ExtractValue(metadata, '//datafield[@tag="365"]/subfield[@code>="a"]') from biblio_metadata where biblionumber = 37002 and (select frameworkcode from biblio where biblionumber = 37002) = marc_subfield_structure.frameworkcode) tv from marc_subfield_structure where frameworkcode in ('', 'TEST') and tagfield = '365'; ) 2. Copy the default framework to a TEST framework and set (say 365$b to tab ignore and delete 365$d). (I used export the default framework to a csv, create new TEST framework and import from the saved default csv) 3. Edit the bib record and change framework to TEST framework (settings > change framework) and save the record. 4. Run the SQL again and observe the data from subfields b and d have both disappeared from the metadata. If you were to rerun these tests you may need to reload memcache to ensure the newly changed frameworks are picked up. I understand it has been broadly known by some long-term Koha users that deleting a subfield from the framework has this effect, but both these situations potentially cause bib data to be silently and permanently delated from the database. Many users will be unaware and may not discover the problem for some time. Potential solutions might include: a) For subfields not in the framework or with tab "ignore" allow the data to be saved as is on saving for edit; b) When selecting "change framework" detect if data would be lost and alert the user with an option to back out of the change without losing data; c) Do not allow deletion of a subfield from a framework and do not allow the "ignore" option for the tab. If a field is to be ignored but hidden there are plenty of visibility options in the framework. NB: The current delivered default framework has 13 subfields set to the "ignore" tab. I cannot see what purpose these serve as no data can survive within them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 35581] New: ILL Koha classes are not consistent
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35581 Bug ID: 35581 Summary: ILL Koha classes are not consistent 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 127

[Bug 35083] New: Koha::Illbatchstatus should be kosher
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35083 Bug ID: 35083 Summary: Koha::Illbatchstatus should be kosher Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 The following methods should just be overloading their counterparts and follow what we do everywhere else: * create_and_log => overloaded store * update_and_log => overloaded store * delete_and_log => overloaded delete Also, tests need to be placed in t/db_dependent/Koha/Illbatchstatus.t -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 35082] New: Koha::Illbatch should be kosher
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35082 Bug ID: 35082 Summary: Koha::Illbatch should be kosher Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 The following methods should just be overloading their counterparts and follow what we do everywhere else: * create_and_log => overloaded store * update_and_log => overloaded store * delete_and_log => overloaded delete Also, tests need to be placed in t/db_dependent/Koha/Illbatch.t -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 39668] New: Add option to show/hide inactive vendors by default on acqui/booksellers.pl
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39668 Bug ID: 39668 Summary: Add option to show/hide inactive vendors by default on acqui/booksellers.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On acqui/booksellers.pl if you have inactive vendors, they show by default. Some would like an option to hide the inactive vendors by default with the option to toggle/display inactive ones. Maybe we don't a sys pref. Use localStorage maybe? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 26500] New: Automatic renewals show incorrect count of renewals allowed when CircControl is set to "the library you're logged in at"
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26500 Bug ID: 26500 Summary: Automatic renewals show incorrect count of renewals allowed when CircControl is set to "the library you're logged in at" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When CircControl is set to "the library you're logged in at," the Renew column in the patron checkouts table will show the count of permitted renewals based on the library you're logged in at. This is correct for manual renewals, since those are the rules that will be enforced. However, for automatic renewals this can mean we're showing the user an incorrect number. To recreate: - Create an All Libraries rule that allows 10 renewals - Create a rule for branch A that allows 1 renewal - Creare a rule for branch B that allows 99 renewals - Check an item out from Branch A, set to auto-renew - While logged in as Branch A, confirm Koha tells you you have 1 renewal available - Log in as Branch B, see you have 99 renewals - Log in as Branch C, see you have 10 renewals - Set No Renewal Before to allow renewal immediately - run the auto_renew cron, item renews once - run the auto-renew cron again, confirm too_many error because only 1 renewal is allowed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9