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

[Bug 29854] New: ES timeout is not configurable
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '22

12 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29854 Bug ID: 29854 Summary: ES timeout is not configurable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com Using the sandboxes system I am getting a timeout during the commit request. This is the 'request_timeout' parameter that is defaulting to 30 https://metacpan.org/pod/Search::Elasticsearch::Role::Cxn#request_timeout Setting it to 60 resolved the problem. We should make this value configurable. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 21022] New: Exceptions should skip stringifying if message manually passed
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '22

12 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21022 Bug ID: 21022 Summary: Exceptions should skip stringifying if message manually passed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 20590 introduced a way to create more useful and testable exception messages. But we should still be allowed to pass manual messages, because we might not have all the information we need to build the stringified version like it proposed. Notably on Koha::Object->store, in which we parse the DBI warning. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 29508] GET /patrons/:patron_id should use Koha::Patrons->search_limited
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29508 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)|22.05.00,21.11.02 |22.05.00,21.11.02,21.05.08 released in| | Status|Pushed to stable |Pushed to oldstable CC| |andrew(a)bywatersolutions.com --- Comment #10 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- Pushed to 21.05.x for 21.05.08 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #12 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Still chewing on this. You wouldn't have to have a separate table to link libraries, shelving locations and maps, if you created specific shelving locations for each library, limiting that location to that library. That would create a long shelving locations table, but it would mean not creating a new table, and if you are limiting to the library, that library is only seeing their shelving locations. Theoretically, that would work. With each unique shelving location code, I would create a separate Authorized Value in a category like SHELVINGMAPS, and use the same shelving location code, and provide the url. In jQuery, I would find the itemnumber, get the shelving code, and then link the map. This would be more ideal if it were built in. Better yet, if I am going to the trouble of creating individual shelving locations for each library, why not take advantage of the icons for that location. It would be great if we could upload our own images for a custom icon, and just define the map in the shelving location. (Unless the icons for shelving locations are actually used somewhere.) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #11 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Actually, instead of linking specific items to maps, I would suggest that perhaps there could be some way of specifying a specific combination of branch and shelving location in the Authorized Values table that, if matched on a item in the record details, an symbol appears next to the shelving location that patrons can click on to show the map in a model. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 --- Comment #10 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Would love to see this get some steam behind it again. I could easily see an authorized value category with codes to urls for specific locations in the library. This would work great as we could limit codes to specific libraries. Then we would just need a table linking the item to a code, and make this selectable in item editing. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 Christopher Brannon <cbrannon(a)cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cbrannon(a)cdalibrary.org --- Comment #9 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Would love to see this get some steam behind it again. I could easily see an authorized value category with codes to urls for specific locations in the library. This would work great as we could limit codes to specific libraries. Then we would just need a table linking the item to a code, and make this selectable in item editing. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10814] Add a link to shelving locations / LOC authorised value for pointing to a map or similar
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10814 Christopher Brannon <cbrannon(a)cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC| |cbrannon(a)cdalibrary.org --- Comment #1 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- *** This bug has been marked as a duplicate of bug 737 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 737] Map of library in search system
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=737 Christopher Brannon <cbrannon(a)cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nengard(a)gmail.com --- Comment #8 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- *** Bug 10814 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29848] New: Add option to increase fund warnings when met
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '22

11 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29848 Bug ID: 29848 Summary: Add option to increase fund warnings when met Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When setting up a fund, one can provide an amount and/or percentage of money expended beyond which to warn the user. Once that limit has been exceeded, all subsequent orders against that will generate a warning. It would be helpful if the warning popup provided an easy interface with which to increase the warning amount and / or percentage. That would allow the user to do something like set a warning for 50% and, upon reaching that, increase the percentage to 75% in order to get a future warning at another significant point. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0