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

[Bug 17131] New: Zebra index for Title is too broad
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17131 Bug ID: 17131 Summary: Zebra index for Title is too broad Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 54482 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54482&action=ed… Test file One of the zebra index definitions in marc21/biblios/biblio-koha-indexdefs.xml for Title includes the entire 245 tag:  <index_data_field tag="245"> <target_index>Title:w</target_index> <target_index>Title:p</target_index> </index_data_field> Since 245$c can contain Author, this means that author names will show up in Title searches. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 20366] New: More information about orders linked to subscriptions on "Acquisition details" tab
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20366 Bug ID: 20366 Summary: More information about orders linked to subscriptions on "Acquisition details" tab 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: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org On the 'Acquisition detail' tab on bibliographic record, we cant' know if orders are placed on bibliographic or subscription level. It is quite complicated when several subscriptions are attached to this record to have a clear history of the acquisitions. It would be great for order managers if we could have 2 more columns on this tab, one with the 'aqorders.subsciptionid' and one with 'subscription.callnumber'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 23689] New: Terminology: Branches limitations should be libraries limitations - Authorised Values
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23689 Bug ID: 23689 Summary: Terminology: Branches limitations should be libraries limitations - Authorised Values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the authorized value administration pages we should use 'libraries limitations' instead of 'branches limitations'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 19490] New: Add a 'holds' column to the Batch Item Modification Tool
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19490 Bug ID: 19490 Summary: Add a 'holds' column to the Batch Item Modification Tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some librarians would like to know the holds activity for items when using the batch modification tool. We should display a holds count column to the batch item modification tool that will show the number of holds on an item / holds for entire record -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 18723] New: Dot not recognized as decimal separator
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18723 Bug ID: 18723 Summary: Dot not recognized as decimal separator Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org Since we work on 16.11, we can't use dot when we receive orders but only comma (for example : a price 11.25€ will be changed in 1125,00€ after receiving the order). It seems linked to syspref "Currencyformat" because the behaviour is different when we change it from FR to US format (a price 15,43€ will be changed in 15,430.00€). When we worked on 3.20 until this april, we could use both dot and comma when receiving books. This is quite disturbing for staff users because a dot is required when adding an order to a basket, whereas a comma must be used when receiving the book but there is no warning like it exist in the basket. I don't know if it's a similar problem to the "Bug 18186 - Amounts with decimal comma instead of decimal dot breaking payments" about the circulation module. We also work with plack, but even without it, we still have this bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 74

[Bug 23529] New: Interlibrary loan javascript is broken
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23529 Bug ID: 23529 Summary: Interlibrary loan javascript is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com This was caused by an overzealous fix in Bug 23229. A fix was appended as a follow-up patch on 23229 but Katrin advised that it should be a new bug, hence this one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 23467] New: BlockExpiredPatronOpacActions is causing screen to duplicate
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23467 Bug ID: 23467 Summary: BlockExpiredPatronOpacActions is causing screen to duplicate Change sponsored?: --- Product: Koha Version: 18.11 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 92249 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=92249&action=ed… Screenshot of the duplicated screen At 18.11, if the BlockExpiredPatronOpacActions system preference is set to block, when an expired patron attempts to place a hold in the OPAC, the screen duplicates with a cookies error in the middle of the screen. See screenshot attached. I can't reproduce this at 17.11. To reproduce at 18.11. 1) Ensure that BlockExpiredPatronOpacActions is set to Block, and ensure that this is not be overridden by the Patron Category policy. 2) Log into the OPAC as an expired user. 3) Search for an item to hold 4) Click Place Hold Setting the BlockExpiredPatronOpacActions system preference means the hold gets placed normally. I also notice that the lower half of the screen (i.e. the duplicated portion) ignores any jQuery configuration. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 17359] New: Patron import results use wrong encoding
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17359 Bug ID: 17359 Summary: Patron import results use wrong encoding Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org When using the patron import tool, the summary at the end uses wrong character encoding. Upload a csv with a few fields and include some ü ö ä. To trigger an error, not providing a surname in the file should work, or a non numeric cardnumber. You will see broken Umlauts on the results page. (The imported data is ok, only the summary is not) -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 20919] New: A Zebra query is done for each item when opening a record detail page
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20919 Bug ID: 20919 Summary: A Zebra query is done for each item when opening a record detail page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have figured out that koha launch a zebra query for each item of a record, if the record have few items no problem, but if the record has hundreds of items, the time to display goes easily over 30 seconds. we have checked on a fresh install on debian jessie 8 with koha 17.11.6 and 18.05 the file zebra-output.log becomes huge We have checked from intranet interface -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 23398] New: Exporting/Reimporting frameworks in XML format will give incomplete results
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23398 Bug ID: 23398 Summary: Exporting/Reimporting frameworks in XML format will give incomplete results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: System Administration 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 Michael Kuhn reported on the mailing list: As usual when creating a new framework I did export the standard framework in XML format, created a new framework ABC and the imported the XML file into the new framework ABC. I tried to do this in virgin installations of Koha 18.11.04 and Koha 19.05.00 but instead of importing all 345 MARC fields, only 102 were actually imported. I've verified this on master with the same result: - Pick any framwork, I used Kit - Export it using the XML format - Create a new framework, name it as you want - Import using the downloaded XML file - Compare both frameworks - Verify that the number of fields is different -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18