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

[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 28641] New: ILLHiddenRequestStatuses does not consider custom statuses
by bugzilla-daemon＠bugs.koha-community.org 03 May '23

03 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28641 Bug ID: 28641 Summary: ILLHiddenRequestStatuses does not consider custom statuses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The ILLHiddenRequestStatuses syspref does a good job of filtering out requests that have statuses matching the specified values, but it doesn't take into account custom statuses. To demonstrate this, create a custom ILL status authorised value, give a request that value, then specify the status code in ILLHiddenRequestStatuses. Then view the list of requests, the list will contain the request with the custom status. Additional filtering needs to be added to filter out requests with a custom status code matching the specified values. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[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 28093] New: Additional configuration option(s) for Shibboleth-only mode
by bugzilla-daemon＠bugs.koha-community.org 01 May '23

01 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28093 Bug ID: 28093 Summary: Additional configuration option(s) for Shibboleth-only mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: Boze.1(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Regarding bug 18506 , in the staff client with Shibboleth Only Mode enabled, when one logs out, the user is immediately logged back in to the staff client. I understand that this is the intended behavior and could be solved by using Single LogOut (SLO). SLO, however, would log the user out of all current Shibboleth sessions, which would not be desirable (for us). In addition, if the user is already logged in to Shibboleth, when visiting the staff client for the first time, the user is automatically logged in without seeing a login page. We would find it preferable if there were an option for Shibboleth-only mode (in the staff client) to have a landing page that would prompt the user to log in (whether or not the user had already authenticated). If the user was already authenticated, the user would simply be passed on to the staff client without needing to provide credentials. On logout, the user would return to the landing page but not be logged out of Shibboleth. Another alternative could be to have a new option that would disable local logins (except for self checkout) if some other authentication method (CAS, Shibboleth) has been activated. Basically this would look the same as the current login page, but with no option for local login. On logout, the user would be returned to the login page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27765] New: Unable to set a custom order to library branches on opac-library.pl
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27765 Bug ID: 27765 Summary: Unable to set a custom order to library branches on opac-library.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: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org Per this comment on #13388 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13388#c28 it's not possible to rearrange the order of library branches on the "Libraries" opac-library.pl page, they must be sorted alphabetically ascending. Alphabetical ordering isn't ideal for all library systems. For instance, we have three branches: Oakland, San Francisco, and a small Materials Library that's based in SF. Alphabetically, Materials comes first but it's the least generically useful. We generally list it last when we have the option e.g. when presenting branch hours. While this bug is related to the OPAC, I suspect that Koha Administration > Branches is ultimately what needs a change, adding an ordering component to the information stored about library branches which controls the opac-library.pl display. -- You are receiving this mail because: You are watching all bug changes.

1 7

[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