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

[Bug 26794] New: Item transfer modal may close automatically after a delay
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26794 Bug ID: 26794 Summary: Item transfer modal may close automatically after a delay Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi Koha, We got complains from users that the new item transfer modal is not convenient when using barcode scanner and mouse/keyboard is unavailable. I've made a small javascript to add in intranetuserjs that closes this modal after a delay (here, 3 secs). Some colleagues of mine told me I shall open a BZ to document this, there it is : <pre> /* Close item transfer modal after 3sec */ $('#item-transfer-modal').on('shown.bs.modal', function (e) { window.setTimeout(function () {$('#item-transfer-modal').modal('hide')}, 3000) }); </pre> Best, Arthur from BibLibre's Koha Support -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38012] New: Remove ispermanent from returns.tt and branchtransfers.tt
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38012 Bug ID: 38012 Summary: Remove ispermanent from returns.tt and branchtransfers.tt Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The templates for returns and branch transfers both have code to display an error for the value "ispermanent," but that doesn't appear to actually be in use elsewhere in the code. https://github.com/Koha-Community/Koha/blob/b4054dbb1578349cd1b8caa8fac9cbe… https://github.com/Koha-Community/Koha/blob/b4054dbb1578349cd1b8caa8fac9cbe… Looking at returns.pl, it makes reference to "ispermanent" in 3.0 but not 18.05. It seems like this is a remnant of a previous method for handling return behavior and transfers? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 36555] New: Add report_id to file name when exporting report results
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36555 Bug ID: 36555 Summary: Add report_id to file name when exporting report results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org If one were in the habit of creating reports with fairly generic names, one might download a bunch of report results and then have trouble remembering what's what. This very relatable and not at all foolish situation could be helped by including the report ID in the file name, making it easier to find the query that produced the downloaded file. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 27872] New: Expand {QUERY_KW} function from OPACNoResultsFound to not-empty search results page
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27872 Bug ID: 27872 Summary: Expand {QUERY_KW} function from OPACNoResultsFound to not-empty search results page 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron finds a record but it is unavailable, they can use OPACSearchForTitleIn to look for that same record elsewhere. If a patron finds nothing at all, they can use OPACNoResultsFound to repeat their search in another catalog. But if a patron performs a search that returns *something* but not the thing they want, then they don't have a path to another catalog. We should allow that. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 37412] New: Style placeholder text in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37412 Bug ID: 37412 Summary: Style placeholder text in the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED 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 Depends on: 36651 Created attachment 169222 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169222&action=e… Screenshot showing re-styling of placeholder text In order to make the OPAC search bar's placeholder text easily distinguishable from regular text we should style it differently. To avoid using a lighter and thus less readable text color I propose to make the placeholder italic and right-aligned. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36651 [Bug 36651] Add placeholder text to the search bar in the OPAC -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 23776] New: API comparative documentation for tierce application
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23776 Bug ID: 23776 Summary: API comparative documentation for tierce application Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com Work in progess: https://wiki.koha-community.org/wiki/API_comparative_usages -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 17618] New: perl-modules Debian package name change
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17618 Bug ID: 17618 Summary: perl-modules Debian package name change 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: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The perl-modules package for Perl 5.22 is called perl-modules-5.22. Koha should know about it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 17712] New: Move availability calculation to the Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17712 Bug ID: 17712 Summary: Move availability calculation to the Koha namespace 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: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 57921 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57921&action=ed… Diagram to proposal for new classes and their relations Currently some availability-related calculations are scattered around in different modules (which alone is not bad) but also in Perl-scripts, like opac-reserve.pl that has some patron related checks, maxreserves and some other. With this problem I think it is confusing for someone to figure out how availability is calculated. This also makes it difficult to implement something new that needs to find out different levels of availabilities. An example of "anything new" would be REST API, which needs to be able to tell different availabilities (biblio/item holdability, checkout availability both anonymously and with patron restrictions etc). As of now, if we simply ask CanBookBeReserved in REST controller, we are completely ignoring patron debarments and fines, and maxreserves system preference. Another problem is that currently there is no unified way of reasoning unavailability between holds and checkouts. There are strings from CanItemBeReserved, then there are HASHrefs with additional parameters from CanBookBeIssued, then some simple checks that may be simply 1 or 0, like IsAvailableForItemLevelRequest. REST API should however return uniform error codes. Also CanItemBeReserved has the problem that it returns the first reason in case of unavailability, and not all of them, if there would be more. An end-user would probably want to know all problems at once instead of fixing one to only find out there is another. My proposal is to move availability-related calculation and checks into Koha namespace. I propose adding a class, Koha::Availability, that is able to contain availability-related information. It would contain methods to easily find out availability status and any reasons to unavailabilities. To represent reasons for unavailability/additional messages/needs for confirmation, I propose objects instead of strings or hashes. These objects could be Koha::Exceptions. Availability calculation could be categorized into Koha::Availability::Calculation's subclasses. Answers to item availability could be located in Koha::Item::Availability::Hold and Koha::Item::Availability::Checkout. This setup would let us have an unified way for handling availability the same way everywhere. How would it work in practice? I will describe my idea with "ingredients" and "recipes": - "ingredient": anything availability-related sub-check or sub-calculation (e.g. item withdrawn, reservesallowed in issuing rules, age restriction etc.) that returns a Koha::Exception::* if it spots a problem. These could be located in Koha::Availability::Calculation subclasses. - "recipe": a set of ingredients that cooks an answer to question "is something available in some way", for example: ** "Q: does an anonymous user see an item available in search result? -> A: no, unavailability reason: Koha::Exceptions::Item::NotForLoan" ** "Q: is an item available for hold for this patron? -> A: yes, additional note: Koha::Exceptions::Item::NotForLoan with parameter code => 'Ordered'" ** "Q: is an item available for checkout for this patron by a librarian -> A: possibly; librarian needs to confirm Koha::Exceptions::Patron::Debt, exception includes field max_outstanding => 10.00, current_outstanding => 15.00" These could be located in Koha::Item/Biblio::Availability::Hold/Checkout The ingredient would contain all logic to spot a problem. The recipe would use what ever ingredients it needs to, and decide if a problem is worth of unavailability, additional note or perhaps ask a confirmation. This is somewhat same as CanBookBeIssued, but the point is to move all calculations away from the recipe so that we can re-use the same logic in another availability recipe. Any thoughts on this idea and current availability in general? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 89

[Bug 16826] New: Add API routes for getting item availability and holdability
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16826 Bug ID: 16826 Summary: Add API routes for getting item availability and holdability Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org Add API routes for getting item availability and holdability. Holdability check requires a target borrower (either user himself or borrowernumber). I'm thinking of following endpoints: GET /api/v1/items/{itemnumber}/availability GET /api/v1/items/{itemnumber}/holdability For myself GET /api/v1/items/{itemnumber}/holdability?borrowernumber=X For X Terms: - availability: Does not require login or permissions. Makes a simple check if item is in a valid state for holdings. In other words, check "notforloan", "onloan", "itemlost", "withdrawn", "damaged". - holdability: Requires login and also catalogue permission if the request is made for another borrowernumber than myself. Item is holdable if it is available and if it satisfies IsAvailableForItemLevelRequest and CanItemBeReserved in C4::Reserves + (also debarments and fines?) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 83

[Bug 29805] New: Database update fails in MySQL 5.7 because it's missing REGEXP_REPLACE
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '25

16 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29805 Bug ID: 29805 Summary: Database update fails in MySQL 5.7 because it's missing REGEXP_REPLACE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It looks like this important database update is failing for MySql 5.7 because it lacks support of REGEXP_REPLACE. Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with additional_contents ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION koha.biblioteca.REGEXP_REPLACE does not exist at /usr/share/koha/lib/C4/Installer.pm line 738 Are we still supporting 5.7? If not, should we highlight that somewhere? We currently only list MariaDB versions on the wiki linked from release notes: https://wiki.koha-community.org/wiki/System_requirements_and_recommendations We are still listing MySQL here: https://koha-community.org/download-koha/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21