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

[Bug 37657] New: koha-list --elasticsearch is super slow
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37657 Bug ID: 37657 Summary: koha-list --elasticsearch is super slow Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you have a large number of instances on a server, "koha-list --elasticsearch" takes a very long time to run. I think it's about 1-2 seconds per instance. That probably doesn't sound like much, but if you multiple it against a large number then it starts adding up. If it's run as part of an "apt-get install koha-common", that means that you've got a lot of downtime for what should be a very simple task. It's not an urgent issue, but I figure at some point I'll look at optimizing this lookup. The fun part with apt-get install koha-common is that "koha-list --elasticsearch" gets run 2 times. On some test machines I'm running, the slowest part of an update is "koha-list --elasticsearch". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 37495] New: Add ability to specify a single plugin to run for plugins_nightly.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37495 Bug ID: 37495 Summary: Add ability to specify a single plugin to run for plugins_nightly.pl Change sponsored?: --- Product: Koha Version: unspecified 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 It would be nice to have the ability to specify a single pluign for plugins_nightly.pl to run for a few reasons: 1) It would be very useful for development and testing 2) It gives the ability to run different nightly triggers at different times 3) Some other third thing -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 29031] New: Authorities see also links - plack error
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29031 Bug ID: 29031 Summary: Authorities see also links - plack error Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: vitorfernandes87(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The authorities see also links in Koha 21.05.01 OPAC gives a plack error: Can't call method "authtypetext" on an undefined value at opac-authorities-home.pl line 155 Test plan: - Create for example an UNIMARC authority with the following fields: - 250$a - test1 - 550$a - test2 - Open the created authority in OPAC - Click on the link test2 (see also section) - Error 500 -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 37328] New: Cannot delete report after using Update and Run SQL button
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37328 Bug ID: 37328 Summary: Cannot delete report after using Update and Run SQL button Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a report or edit an existing one - on the edit screen (/cgi-bin/koha/reports/guided_reports.pl?id=XXX&op=edit_form), click "Update and run SQL" - On the resulting page, where you see both your results and the edit form, click Edit and then Delete - Nothing happens. The delete confirm modal doesn't appear, so the deletion doesn't move forward. The url on that results + edit screen is just "/cgi-bin/koha/reports/guided_reports.pl" -- I don't know if that's part of the issue? The report can still be deleted from other pages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 36977] New: Google does not read sitemaps with the name sitemapNNNN.xml
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36977 Bug ID: 36977 Summary: Google does not read sitemaps with the name sitemapNNNN.xml Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: michael.skarupianski(a)gmail.com, pedro.amorim(a)ptfs-europe.com, robin(a)catalyst.net.nz We have experienced problems with Google indexing: it seems (controlled in Google search console) that Google does not "like" sitemaps with a name like sitemapNNNN.xml (does not read them). Changing the name to sitemap_NNNN.xml miraculously resolves the issue: individual pieces of sitemap are read as they are declared in sitemapindex.xml. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 36991] New: Add ability to scan call numbers index/search field
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36991 Bug ID: 36991 Summary: Add ability to scan call numbers index/search field Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Some libraries ask for the ability to scan/browse the call numbers index. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 36603] New: UNIMARC: automatically copy the ISNI number over when linking authorities with authorities
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36603 Bug ID: 36603 Summary: UNIMARC: automatically copy the ISNI number over when linking authorities with authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org The 2023 edition of the IFLA UNIMARC Authorities Format Manual [1] has the following to say about subfield $o of authority fields 500, 510 and 520 [2,3,4]: "$o International Standard Name Identifier (ISNI) The subfield $o (International Standard Name Identifier) is used in field 510 to record the ISNI of the related identity. When the preferred access point of an authority record that contains field 010 is transferred to the 500/510/520 access point of another record (while establishing a link between both authority records), the number contained in the 010 field of the first record will also be transferred in a devoted subfield $o. Repeatable." So, when linking authorities with other authorities in UNIMARC instances I think it would be a good idea if Koha automatically copied the contents of subfield 010$a [5] into the corresponding 5xx$o subfield (if such an ISNI number exists in the source record, of course). [1] https://repository.ifla.org/handle/123456789/3011 [2] 500 RELATED ACCESS POINT – PERSONAL NAME [3] 510 RELATED ACCESS POINT – CORPORATE BODY NAME [4] 520 RELATED ACCESS POINT – FAMILY NAME [5] 010 INTERNATIONAL STANDARD NAME IDENTIFIER (ISNI) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37944] New: Object deletion should be logged with a JSON diff of changes, implement for items
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37944 Bug ID: 37944 Summary: Object deletion should be logged with a JSON diff of changes, implement for items Change sponsored?: --- Product: Koha Version: unspecified 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 We should store deleted objects as diffs just as we do for modification and item created. This enhancement will store modification diffs if the action is set to DELETE, and an "original" object is passed in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 32413] New: JSON reports shows inaccurate results with repeated parameters
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32413 Bug ID: 32413 Summary: JSON reports shows inaccurate results with repeated parameters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org If I create a report that uses a repeating parameter, for example <<library>>, more than once in a report, and then run a JSON call on that report, I get inaccurate results (Like every other result). Currently, the only workaround is to make each parameter unique, and then repeat the parameter over as many times as it is needed in the report. For example, https://mydomain.com/cgi-bin/koha/svc/report?id=938&sql_params=blah would only return half the results if the report because I use the same parameters 7 times int he sql. However, if I rename each parameter something different, like <<library1>>, <<library2>>,etc, and call https://mydomain.com/cgi-bin/koha/svc/report?id=938&sql_params=blah&sql_par…, it works. The JSON call needs to be updated to accept repeated parameters. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 37639] New: items.stack ( shelving control number ) not included in items API endpoint
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37639 Bug ID: 37639 Summary: items.stack ( shelving control number ) not included in items API endpoint Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com items.stack is not included at /api/v1/items/ I think it should be -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52