October 2022 - Koha-bugs - lists.koha-community.org

[Bug 21762] New: ES: Is it possible to differentiate between any and anywhere?
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '23

17 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21762 Bug ID: 21762 Summary: ES: Is it possible to differentiate between any and anywhere? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl See also bug 8962 about differentiating any from anywhere in Zebra. Any would be the sum of all user defined indexes, and anywhere would really be all data. Is this possible in Elastic Search ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31994] New: Clicking the next button of a DataTable loading its data from the HTML does nothing
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31994 Bug ID: 31994 Summary: Clicking the next button of a DataTable loading its data from the HTML does nothing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: olivier.hubert(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When the next button of a DataTable with data straight from the HTML is clicked, nothing happens. Additionally, an error can be found in the console similar to: Uncaught TypeError: q is undefined Note that this problem does not occur when the data is sourced using Ajax. Steps to reproduce: 1. Open itemtypes.pl. 2. If there are fewer than 11 item types, create additional item types until there are more than 10, so that the next button can be used. 3. Click on the next button / link. 4. Notice that nothing happens. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 31640] New: Fuzzy translations of preferences can cause missing sections and inaccurate translations
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31640 Bug ID: 31640 Summary: Fuzzy translations of preferences can cause missing sections and inaccurate translations Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: kevin.carnes(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr We noticed that when installing the Swedish translations in 22.05, the translate program was using fuzzy translations for preferences. This resulted in many strange translations when viewing the preferences in Swedish. There were also some sections that were missing since multiple sections had the same translated name and there can only be one section for each name since they are hash keys. Our solution is to ignore fuzzy translations for preferences, since we prefer the original English, but it can be made an option if the fuzzy translations are helpful to others. The solution also adds warnings if a translation causes multiple sections to have the same name. When I run the warnings with fuzzy translations in 22.05.03, I get warnings in 65 languages (am-Ethi, ar-Arab, az-AZ, be-BY, bg-Cyrl, bn-IN, ca-ES, cs-CZ, cy-GB, da-DK, de-CH, el-GR, en-GB, en-NZ, eo, eu, fa-Arab, fr-CA, gl, he-Hebr, hi, hr-HR, hu-HU, hyw-Armn, id-ID, is-IS, ja-Jpan-JP, ka, ko-Kore-KP, ku-Arab, lo-Laoo, mi-NZ, mon, mr, ms-MY, nb-NO, ne-NE, nl-BE, nl-NL, nn-NO, oc, pbr, pl-PL, prs, pt-BR, pt-PT, ro-RO, ru-RU, sd-PK, sk-SK, sl-SI, sq-AL, sr-Cyrl, sv-SE, ta-LK, te, tet, th-TH, tl-PH, tr-TR, uk-UA, ur-Arab, vi-VN, zh-Hans-CN, zh-Hant-TW). If there are languages where multiple sections should have the save name, we can discuss using an array instead of a hash for the sections. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 25590] New: B_streetnumber is missing from opac-memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25590 Bug ID: 25590 Summary: B_streetnumber is missing from opac-memberentry.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If a patron adds an alternate address to their patron record in the OPAC, there is no option to enter a street number. This field is available in the staff client. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 18280] New: Item barcodes should be locked when record is created
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18280 Bug ID: 18280 Summary: Item barcodes should be locked when record is created Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When several cataloguers are cataloguing simultaneously and the autoBarcode system preference is set to generate the barcodes in 1, 2, 3 form, it is possible that the same item barcode will be assigned to two different items at the same time which prevents the record from being saved. Koha should lock the barcode in some way once it has been allocated, even if the item record is not yet saved. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 30277] New: Make fetching ILL data from the API more efficient
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30277 Bug ID: 30277 Summary: Make fetching ILL data from the API more efficient Change sponsored?: --- Product: Koha Version: master 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 Librarians are complaining that displaying the full table of ILL requests is taking a lot of time, even with moderate amounts of requests (on the order of 100-200). I think there are a couple of bottlenecks: 1. Embedding data We are embedding - metadata - patron - capabilities - library - status_alias - comments - requested_partners That's at least 6 additional queries times the number of requests in the table. Not sure what can be done here in general, though. 2. Capabilities/status graph For every request, the whole status graph is included with each request. When I look at the JSON data returned for one request in a sample database, it is about 540 lines of data. But about 400 of those make up the status graph, and since this system only has one active backend, those 400 lines are (as far as I can see) identical for all 200 requests. Could we send the status graph once per backend, and then have some reference/link from the request to the correct status graph? 3. Fetching requests selectively Today, data is fetched for all requests not hidden by ILLHiddenRequestStatuses before the table of requests is displayed. Bug 30200 proposes to add configurable tabs to the ILL requests table. Could it be possible to load the data for the tabs just-in-time, so that only the data for the first tab is loaded initially? Instead of loading everything just-in-case when the page is first shown. And then have the "All" tab to the right, so that "all" data is only loaded if the user asks for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 23021] New: Quick Spine Label Creator doesn't use regex splitting rule
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23021 Bug ID: 23021 Summary: Quick Spine Label Creator doesn't use regex splitting rule Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I'm working with a library that enters their LCC call numbers in the format "PN6728 .B36" rather than "PN 6728 .B36." This means that the default LCC splitting rule doesn't insert a line break between PN and 6728. So I wrote a regex splitting rule that does that fine. However, the regex splitting is only applied when using the full label creator. When printing via the quick spine label creator it appears to still be splitting based on the default LCC splitting rule. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28395] New: allow patron enrollment period to be set in days for patron categories
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28395 Bug ID: 28395 Summary: allow patron enrollment period to be set in days for patron categories Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Admin > Patron categories Some libraries would find it useful to be able to set the enrollment period in days instead of months. Currently you can only set it in months. It would be handy if we could set it in days or months. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 27642] New: Add notes to receipts
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27642 Bug ID: 27642 Summary: Add notes to receipts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Would love it if there were a way to add notes to the bottom of checkout receipts - Maybe a piece of information a patron wants that we could manually fill out - maybe called "Receipt Notes". It would also be cool if down the road, if a patron has a book checked out, and they wanted to have a list of books in the series, that there would be some kind of button or link next to the book we could click that would add that list to these notes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30265] New: Hide 'Log into your account' in OPAC authentication page
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30265 Bug ID: 30265 Summary: Hide 'Log into your account' in OPAC authentication page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 131536 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131536&action=e… Screenshot showing double auth form If not logged in, in OPAC header there is link 'Log into your account'. Using it shows a popup with authentication form. In authentication page /cgi-bin/koha/opac-user.pl this double authentication form feels not ergonomic. It may lead to misunderstanding. We can simply hide this link in this special page. -- You are receiving this mail because: You are watching all bug changes.

1 20