March 2018 - Koha-bugs - lists.koha-community.org

[Bug 17514] New: Record details page uses incorrect class "results_summary "
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17514 Bug ID: 17514 Summary: Record details page uses incorrect class "results_summary" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The record details page re-uses the class results_summary which is semantically incorrect and causes unwanted interactions with the styling of the actual results page which also uses the results_summary class. We should change the instances of the results_summary class to details_summary on this page. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 17474] New: Make possible to create fee after hold is filled and checked out to patron
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17474 Bug ID: 17474 Summary: Make possible to create fee after hold is filled and checked out to patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17463] New: Wrong recipient for suggestion' s notice in branch specific
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17463 Bug ID: 17463 Summary: Wrong recipient for suggestion's notice in branch specific 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Hi, There is test plan to understand the problem: Branch A with borrower A and librarian A, Branch B with librarian B Notice ACCEPTED, ORDERED, AVAILABLE set to each branch - borrower A done a suggestion A - librarian from branch A accepted suggestion A - email for suggestion ACCEPTED sent to borrower A - librarian from branch A ordered suggestion A, a biblio is created (biblio A) - email for suggestion ORDERED sent to borrower A - librarian from branch B ordered an other copy from the same biblio A (not from suggestion A, really from biblio A) - Order from librarian B is also related to suggestion A : this is the problem. - librarian B received his item before librarian A - email for suggestion AVAILABLE sent to borrower A while item for branch A is not arrived yet. Do you understand me? Order from an other branch for the same biblio should not be related to the initial suggestion. Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 17440] New: Checkout notes ignores OPAC description in OPAC
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17440 Bug ID: 17440 Summary: Checkout notes ignores OPAC description in OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 56416 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=56416&action=ed… Screenshot of how message displays in OPAC If a user sets up a BOR_NOTES authorised value with a staff and OPAC description, and then uses the Add messages option in the /cgi-bin/koha/circ/circulation.pl screen, when the message is viewed in the OPAC only the staff description displays. If a message in the messages database table is given a message_type of B, then the OPAC description should display. -- You are receiving this mail because: You are watching all bug changes.

1 3

[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 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 19716] New: Add option to send header line for CSV output
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19716 Bug ID: 19716 Summary: Add option to send header line for CSV output 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, if outputting a CSV file using runreport.pl, you need to look at the report used to know what each column means. It would be nice if we could include column headers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12