January 2020 - Koha-bugs - lists.koha-community.org

[Bug 24151] New: Add a pseudonymization process for patrons and transactions
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '23

25 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151 Bug ID: 24151 Summary: Add a pseudonymization process for patrons and transactions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 176

[Bug 20935] New: Redesign system preferences interface
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '23

25 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20935 Bug ID: 20935 Summary: Redesign system preferences interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 76039 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76039&action=ed… Screenshot showing system preferences standard view I think the system preferences page could use some work to make it more readable. My proposal does this: - Restructure the preferences list as a <dl>, with the preference name as the <dt> and the description as the <dd>. - Add a JS filter library (mark.js) to do live filtering of the page and add search term highlighting. - When the user has searched, show links to the sections in which results were returned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 18686] New: TalkingTech_itiva_outbound.pl fails with Illegal mix of collations
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '23

25 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18686 Bug ID: 18686 Summary: TalkingTech_itiva_outbound.pl fails with Illegal mix of collations Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: larry(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the big bug fix to clean up UTF8 (bug 11944), the default collation was set to utf8_unicode_ci. However on sites that predate that change, the overduerules table may still use utf8_general_ci. This leads to the following error when running the cronjob TalkingTech_itiva_outbound.pl: DBD::mysql::st execute failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [for Statement "SELECT borrowers.borrowernumber, borrowers.cardnumber, borrowers.title as patron_title, borrowers.firstname, borrowers.surname, .... [snip] .... "] at /usr/share/koha/bin/cronjobs/thirdparty/TalkingTech_itiva_outbound.pl line 230. The problem is fixed manually by altering table overduerules and changing its collate setting. However, perhaps there should be a fix in updatedatabase.pl to change the collate if the table is still using the old value. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 23422] New: CART location feature
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '23

24 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23422 Bug ID: 23422 Summary: CART location feature 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 Why was the CART feature made to be a stored value? I am curious why a preference wasn't setup for an hour value, and if an item location is displayed anywhere, this setting could be compared to the timestamp and current time and if it is within the value entered, just display CART or Recently Returned or whatever next to the location. I know it would take changing things in several locations, but it seems this would be much more stable, and would also be less information to store. I don't know if it would cause a performance issue or not. Just thought I'd throw this out there. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24167] New: We should support installation on Debian 10
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24167 Bug ID: 24167 Summary: We should support installation on Debian 10 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Debian 10 has been stable for a little while now, and Debian 8 is nearing end of life. We really should be supporting Debian 10 now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 23024] New: Limit quantity of items in staff items
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '23

20 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23024 Bug ID: 23024 Summary: Limit quantity of items in staff items Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: b.pastern4k(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Is there a patch or a setting that can limit amount of items shown in bibliorecord? In OPAC there is something of that kind - "This record has many physical items (xxx). Click here to view them all." The issue here is that if a record has more than a couple hundred items, it takes too much time to generate template on server and user has to wait few minutes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 24221] New: Convert OPACMySummaryNote system preference to news block
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '23

20 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24221 Bug ID: 24221 Summary: Convert OPACMySummaryNote system preference to news block 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 22880 Building on 22318, the OPACMySummaryNote system preference should be converted to a Koha news block. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22880 [Bug 22880] Convert opacheader system preference to news block -- You are receiving this mail because: You are watching all bug changes.

1 21

[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 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 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