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

[Bug 17602] New: Integrate support for ONeclickDigital/Recorded Books API
by bugzilla-daemon＠bugs.koha-community.org 08 May '23

08 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17602 Bug ID: 17602 Summary: Integrate support for ONeclickDigital/Recorded Books API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Recorded Books / Oneclickdigital are a provider of electronic audio books. They have an API that lets users checkout/checkin/search/place holds etc on their items. It would be great if users could do this within Koha http://developer.oneclickdigital.us/ -- You are receiving this mail because: You are watching all bug changes.

1 168

[Bug 21381] New: OMNIBUS: Circulation history UI improvements - Add Serial enumeration / chronology information at title column
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21381 Bug ID: 21381 Summary: OMNIBUS: Circulation history UI improvements - Add Serial enumeration / chronology information at title column 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: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If librarian lookig for specific item (periodical), on circulation history absent info about serial enumeration / chronology -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 22714] New: ILL table population call might benefit from being inside the datatable
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22714 Bug ID: 22714 Summary: ILL table population call might benefit from being inside the datatable 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: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- As pointed out by Owen (http://irc.koha-community.org/koha/2019-04-16#i_2134071) the ILL table doesn't display any "loading" message while the API call is in progress. It would be a better experience for the user if it did. We should investigate populating the table from within the datatable object, we will then get the benefit of then in built loading message. If not, we could always add a message manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 22718] New: Authorized value for not for loan not showed in cataloging search results
by bugzilla-daemon＠bugs.koha-community.org 02 May '23

02 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22718 Bug ID: 22718 Summary: Authorized value for not for loan not showed in cataloging search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- In the search results in cataloging module (staff client interface), the reason why an item is "not for loan" isn't showed (in the Location column) and can create some confusing situation. For example, some schools put the authorized values for online items and they can't be available for a physical loan but are always available. Are we able to add in the authorized value for the "not for loan" status, something like "not for loan (authorized value)" ? In the same manner as it appears in a normal search in the catalog. In the cataloging module, the info only appears in the detailed view of the item. Thanks, Alexandre -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22693] New: ILL "Price paid" column does not appear in column configuration
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22693 Bug ID: 22693 Summary: ILL "Price paid" column does not appear in column configuration 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: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- "Price paid" was added in bug 22121, it seems I forgot to add it to the column configuration list. Doh. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[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 24 Apr '23

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