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

[Bug 21260] New: Show a few more items in Availability line of XSLT search results
by bugzilla-daemon＠bugs.koha-community.org 09 May '23

09 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21260 Bug ID: 21260 Summary: Show a few more items in Availability line of XSLT search results 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org It seems that bug 5079 introduced the one item in lines like: Availability: Items available for loan: [Call number: XXX](2). The following would imo be more clear: Availability: Items available for loan (2): [Call number: XXX, YYY]. The Call number part still being a span which could be hidden with css. Two changes: [1] Move the item count before the bracket list and make it bold too. [2] List a few item call numbers (not all). We could control this with a preference providing the number listed (now 1 by the chosen condition in the XSLT sheet). Essentially, this will be a code simplification. We do not need the generate-id construction in the current code, etc. -- You are receiving this mail because: You are watching all bug changes.

1 57

[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 26689] New: Monetary accounts notices should be definable at the credit_type/debit_type level
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26689 Bug ID: 26689 Summary: Monetary accounts notices should be definable at the credit_type/debit_type level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently, the print and email notices associated with account actions (receipts, invoices, credit notes etc) are confusingly named and are generalised for all types. We should allow for per-type notices to be assigned to credit/debit types to enable a more accurate approach to these notices. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 25449] New: Make itemtype mandatory by default
by bugzilla-daemon＠bugs.koha-community.org 05 May '23

05 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25449 Bug ID: 25449 Summary: Make itemtype mandatory by default Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Items without homebranch, holding banch and/or itemtype can cause errors in Koha that are not all caught (and probably never will). As we ship Koha with item-level_itypes = item and this is the most common setting, I suggest to make the itemtype mandatory in our default and additional sample frameworks to help avoid problems. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[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 24310] New: Use Text::Lorem instead of String::Random in Test::Builder
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '23

27 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24310 Bug ID: 24310 Summary: Use Text::Lorem instead of String::Random in Test::Builder Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org That would help to get something more readable. Currently we generate a string of one word that is the size of the column. It produces a lot of overflow when displayed on the screen. -- You are receiving this mail because: You are watching all bug changes.

1 6

[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 27074] New: When a subscription is closed, it still shows as current in OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '23

25 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27074 Bug ID: 27074 Summary: When a subscription is closed, it still shows as current in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When a subscription is closed in the staff interface, it will still show as current (running) in the OPAC: Subscription from: 12/29/2019 to: now (current) This is due to the subscription history end date being empty. In order to fix this, you need to activate manual history and set it manually, lots of clicks. I suggest that we either automatically fill the subscription end date on closing the subscription (I think the predicted or receive date of the last issue would be good) or offer an option to do so. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2