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

[Bug 31188] New: UPC or ASIN from amazon for dvd, music cds image
by bugzilla-daemon＠bugs.koha-community.org 07 May '25

07 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31188 Bug ID: 31188 Summary: UPC or ASIN from amazon for dvd, music cds image Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: julie.emond(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, We would like, in the same way as the isbn for books, that the UPC code or the ASIN for amazon enter automatically for the display of images for dvds and music cds. In short for other documents that do not have an isbn. On other request we see that some have briefly talked about it but no solution except to enter the images by hand has been submitted. A gateway between amazon and koha for the UPC code in the same way as we have a gateway for the simagette with an ISBN. Thank you for your help -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 18315] New: authentication and authorization refactoring
by bugzilla-daemon＠bugs.koha-community.org 07 May '25

07 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 Bug ID: 18315 Summary: authentication and authorization refactoring Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: oha(a)oha.it QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Currently, C4::Auth is responsible to do session management, authentication and authorization. There is no clear separations between them, and the authentication is not modular, making it increasingly harder to maintain and/or introduce no authentication integrations. I was experimenting on this for a while, and I managed to put together few commits in a branch. It started as a proposal, but turned out to be working in _most_ of my tests. here more details: I completely removed any need for CGI and CGI::Session while maintaining a fork-exec aproach to the scripts. (This made it easier to implement Koha::Middleware::Session, Koha::Session::DB and ::KohaCache) Koha::Middleware::Session inject a session object in the Plack request, and invoke Koha::Auth if any authentication tokens are available. Koha::Auth has a list of modules which will be invoked in turn and could be enabled/disabled plack.psgi is changed as well, it has enabled the new Middleware and the applications used are no longer Plack::App::CGIBin but Koha::Middleware::App. here few of the things i want to do to simplify the interaction with the current "legacy" code: I didn't change the scripts or any other module at all, instead I tried to hijack C4::Auth methods to rely on Koha::Session and Koha::Auth. This make it simple to switch back to the previous plack.psgi OR using apache and the normal cgi-bin. authentication should happen upfront, before the script is even started. script will have to verify authorization. authentication MUST be modular, possibly having different systems cooperate. (Some serious discussions must be around this point, especially about accounting and authority) what needs to be done: permissions should be reintroduced. right now permissions are read for the user and set in the template, but no checks are perform on requests. (should be fairly simple to do) reintroduce the code related to shib, cas and any other. more testing, especially for the installer (there is lots of code regarding the web installer which isn't there anymore) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 36546] New: API yaml validation is slow.
by bugzilla-daemon＠bugs.koha-community.org 07 May '25

07 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36546 Bug ID: 36546 Summary: API yaml validation is slow. 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: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org >From an strace it can take up to 6 sec on our servers. Ex: First stat: 07:48:46.941069 (+ 0.000129) brk(0x5641224ad000) = 0x5641224ad000 <0.000018> 07:48:46.941340 (+ 0.000015) stat("/home/koha/src/api/v1/swagger/swagger.yaml", {st_mode=S_IFREG|0644, st_size=30696, ...}) = 0 <0.000010> ... last one 07:48:53.453980 (+ 0.000030) lstat("/home/koha/src/api/v1/swagger/swagger.yaml", {st_mode=S_IFREG|0644, st_size=30696, ...}) = 0 <0.000015> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 79

[Bug 36958] New: Internal server error when importing MARC file with bad encoding into an order
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36958 Bug ID: 36958 Summary: Internal server error when importing MARC file with bad encoding into an order Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 167168 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=167168&action=e… Test record in MARC 8 with an encoding error (uses extended character set for Simplified Chinese characters) To reproduce: 1. Go to Cataloguing > Stage Records for Import 2. Upload the attached example file, which is encoded in MARC 8 3. Select the correct encoding and stage the file for import 4. Find or create an open basket in the Acquisitions module 5. Click Add to basket 6. Select From a staged file 7. Select the file that was just staged --> Page crashes with Internal Server Error (or a stack trace if you're testing in KTD) On the other hand, if you return to Cataloguing > Manage Staged Records and import the staged file from there, the import completes and the records are added to the catalog. The badly encoded biblio records can still be viewed (and the biblio detail page displays a warning about the bad encoding). Not sure if it makes sense to allow addorderiso2709.pl to simply import the bad record anyway like manage-marc-import.pl does, or if that would break something else in the ordering process. At the very least it should display an error message instead of crashing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 39667] New: Copy and replace of 952$y to 942$c MARC modification template fails
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39667 Bug ID: 39667 Summary: Copy and replace of 952$y to 942$c MARC modification template fails Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To replicate 1. Make sure there are no record overlay rules that protect the 942$c. 2. Find a bibliographic record. Edit the record in the advanced editor and remove the 942$c if there is one. 3. Create a MARC modification template with these actions: Copy and replace 1st 952$y to field 942$c if field 942$c doesn't exist. 4. Apply the MARC modification template to the example record. Look at the MARC and notice the 942$c has not been replaced. This scenario can be repeated with a bibliographic record that does have a 942$c, but have it be different from the 952$y. Update the template to: Copy and replace 1st field 952$y to field 942$c if 942$c doesn't match Apply the template to the record and see that the 942$c is untouched despite the success message. Multiple variations on the rules above result in no changes to the bibliographic record. I think the rule is trying to apply the descriptive text of the 952$y to the 942$c and it is being rejected because the descriptive text is not the same as the item type code. The success message after the template is applied is in error because no changes were made to the bibliographic record. The 942$c needs to have the item type code in order for the template to work. As an alternative example the template actions of Update existing and add new work, but only if the item type code is entered into the template. Many libraries have bibliographic records with a missing 942$c but have item records with a 952$y. It would be nice if the MARC template can be used to update the bibliographic records by copying the item type code of the 952$y to the 942$c, if it is at all possible. While a library could create a rule using the Update existing or add new rule, they would have to run reports to sort the records by item type first. Which is perhaps less efficient if there are thousands of records. Otherwise the libraries have to manually edit each record or have a script run from a terminal to accomplish the same thing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38586] New: Typo: OPAC preferences - "will only effect"
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38586 Bug ID: 38586 Summary: Typo: OPAC preferences - "will only effect" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the OPAC preferences chapter, under HighlightOwnItemsOnOPAC and HighlightOwnItemsOnOPACWhich (https://koha-community.org/manual/latest/en/html/opacpreferences.html#highl…) "This system preference will only effect sites" effect -> affect -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38587] New: Typo: OPAC preferences - "it's"
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38587 Bug ID: 38587 Summary: Typo: OPAC preferences - "it's" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the OPAC preferences chapter, under OpacAdditionalStylesheet (https://koha-community.org/manual/latest/en/html/opacpreferences.html#opaca…) "enter the full URL pointing to it’s location" it's -> its Please also review this whole sentence. I think there are missing words and puctuation. "If you would rather, you can upload your CSS to another server and enter the full URL pointing to it’s location remember to begin the URL with http://" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 38812] New: Typo: Not for loan: check this option for items type that should not circulate.
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38812 Bug ID: 38812 Summary: Typo: Not for loan: check this option for items type that should not circulate. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de This is from administration.rst: Not for loan: check this option for items type that should not circulate. I think it should probably read: for item types... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 38585] New: Typo: Logs preferences - "patron's accounts"
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38585 Bug ID: 38585 Summary: Typo: Logs preferences - "patron's accounts" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the Logs preferences chapter, under FinesLog (https://koha-community.org/manual/latest/en/html/logspreferences.html#fines…) "Koha should log actions done on charges in patron’s accounts." I'm not sure about this one, I think it should be "patrons' accounts"? A native English speaker's input would help! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38553] New: Typo: Introduction - If you're interesting
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38553 Bug ID: 38553 Summary: Typo: Introduction - If you're interesting Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Typo in the Introduction chapter of the manual. "If you’re interesting in contributing new features" interesting -> interested -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5