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

[Bug 17371] New: REST API: add CRUD for biblios
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17371 Bug ID: 17371 Summary: REST API: add CRUD for biblios 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: benjamin.rokseth(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org This bug proposes to add full CRUD for biblios to the REST API, meaning a basic endpoint for managing records outside of Koha staff. It will make use of Koha Objects and largely replicate the /svc/biblios functionality, but from a RESTful perspective. Proposed routes : GET /api/v1/biblios/{biblionumber} Get a simple record GET /api/v1/biblios/{biblionumber}/items Get a record with items GET /api/v1/biblios/{biblionumber}/expanded Get a record with items and item statuses POST /api/v1/biblios/{biblionumber}/{frameworkcode} Create a record with items (and optional framework) PUT /api/v1/biblios/{biblionumber}/{frameworkcode} Update a record without touching items (and optional framework) DELETE /api/v1/biblios/{biblionumber} Delete a record with items POST and PUT will take marcxml as input -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 17354] New: Group By/Order By SQL mismatch in issues_stats.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17354 Bug ID: 17354 Summary: Group By/Order By SQL mismatch in issues_stats.pl Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: jcoehoorn(a)york.edu QA Contact: testopia(a)bugs.koha-community.org I'm looking in intranet/cgi-bin/reports/issues_stats.pl. I'm not sure of the exact line number, since I may have changed some white space earlier in the file on my system while tracking this down, but near line 350 in that file you'll see this: $colorder = ($colfield =~ /dayname/) ? "weekday($column)" : ($colfield =~ /^month/ ) ? " month($column)" : $colfield; The $colorder value will be used in the ORDER BY clause for the final SQL statement for the report. Contrast that with this code from earlier in the file, which will be used for the GROUP BY and SELECT clauses: $colfield = ($dsp == 1) ? " dayname($column)" : ($dsp == 2) ? "monthname($column)" : There's a clear mismatch here. The earlier snippet should be using "monthname()" instead of "month()", to match the GROUP BY syntax. I found this while playing with Ubunutu 16.04/MySql 5.7. I have turned strict mode off in MySql 5.7, but even with strict mode off the Circulation Report listed under "Statistics Wizards" was broken when I tried to group by month. I suspect grouping by day will be broken as well. The report works as expected for grouping by month after changing to use the monthname() function. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 17133] New: DE Startseite
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17133 Bug ID: 17133 Summary: DE Startseite Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net Übersetzung der Startseite -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 17004] New: REST API: add route to authenticate patron
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17004 Bug ID: 17004 Summary: REST API: add route to authenticate patron 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: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org Add API route to authenticate patron. This would be very useful for 3rd party applications, such as NCIP's LookupUser service or simpleSAMLphp IdP for eduGAIN. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 22833] New: Don't let users cancel holds connected with ILLs
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22833 Bug ID: 22833 Summary: Don't let users cancel holds connected with ILLs 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: magnus(a)libriotech.no Target Milestone: --- In the Swedish (Libris) ILL module, when a new ILL request is created, a record and an item (with a specific ILL itemtype) are also created. And a hold is created between the local patron that is waiting for the ILL and the local ILL item. This means that the ILL shows up as a regular hold when the patron logs into the OPAC. That in it self is OK, but the problematic thing is that patrons can cancel the holds connected with the ILL (maybe thinking that they are then also canceling the ILL request). Libraries would like to stop patrons from doing this. A couple of options come to mind: 1. Add a syspref that can take a list of itemtypes that should not be cancel'able by the patron in the OPAC 2. Add a boolean field like itetypes.let_patrons_cancel_holds_in_opac which defaults to 1 for existing itemtypes, but can be set to 0 to achieve the desired effect. 1 is more unobtrusive, 2 is probably cleaner in the long run? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 18770] New: No update between canceled orders and suggestions status create confusion
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18770 Bug ID: 18770 Summary: No update between canceled orders and suggestions status create confusion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Hi, me and some of my partners have seen a small bug on our systems. If an order made from a suggestion is canceled, it will stay in the suggestions management with the "ordered" status. We must delete the suggestion or change his status in a second step to correct the situation, if you forgot to do it and have many suggestions on your list, it can be very confusing. Therefore, it will be interesting to have a link between the canceled orders and suggestions management, some kind of an "Auto-changing status for suggestions that the order is canceled". Here is the path to check this bug : 1) Go in the Acquisitions 2) Create a suggestion that isn't in your library. 3) Select your new suggestion and mark it as "accepted". 4) Select a vendor and create a basket (or select an existing one). 5) Clic on "add to basket" and select "from a suggestion". 6) Find your suggestion and clic on "+Order" at the right 7) In the new order page, clic on "Add item", select a fund and save it. 8) Clic on "cancel order" at the right and clic on Ok. 9) Go to suggestions 10) Observe that in Suggestion management you will continue to see your suggestion in the "Ordered" tab... Back in 2012, a similar patch (see bug #5346) was proposed and tested to link them but it seems this was never incorporated into the master. (I must also admit that I'm not sure it will do the trick for me, but it's related.) Thanks for the help, Alexandre from CCSR -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 28278] New: Improve $KOHA_CONF parsing speed by using XML::LibXML
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '23

23 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28278 Bug ID: 28278 Summary: Improve $KOHA_CONF parsing speed by using XML::LibXML Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 25503] New: Add option to export items bundle contents in checkouts table
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '23

23 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25503 Bug ID: 25503 Summary: Add option to export items bundle contents in checkouts table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 24023 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24023 [Bug 24023] Add ability to create bundles of items -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 26354] New: Prevent submission of patron modification request unless changes are actually made
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26354 Bug ID: 26354 Summary: Prevent submission of patron modification request unless changes are actually made 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think there should be an preference to not be able to submit a request unless information has been changed. We frequently get modification requests with no changes made at all. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 25063] New: OPAC Renewal Option
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25063 Bug ID: 25063 Summary: OPAC Renewal Option 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I am seeing a strange thing with patron modification requests. I see requests come through asking for modification, but nothing has been changed. Looking closer at the accounts, I see that the accounts are up for renewal. I am thinking that people are checking their information and confirming that their information is up to date. I would like to propose two modifications to the modification requests. First, I think there should be an preference to not be able to submit a request unless information has been changed. Second, perhaps a preference tied in with the first suggestion, that allows the patron to select a check-box stating that they have reviewed all their information, and it is accurate and up to date. Perhaps this option only shows when their account is due for renewal. And perhaps the renewal reminder would include a link to the modification page, asking them to review their information and make any any necessary updates if necessary, but acknowledging that the information is up to date. I suggest this being an option, because some libraries might require fees or a view of a current ID before renewing. Third, even if all the patron is doing is renewing, we could have a preference set to notify or not in the modification requests of the acknowledgement and renewal. Fourth, if there are other steps necessary, like a patron category that requires a fee (that isn't automatically charged on renewal) or ID shown, another preference would give admin the ability to have the account self renew. If all they have done is checked the acknowledge box and submitted, the account renews. This option is tricky, since a person could do this, then go back and make changes. But, those changes, would of course, have to be reviewed. -- You are receiving this mail because: You are watching all bug changes.

1 13