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

[Bug 23734] New: Defaults set during patron imports throws warnings
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '19

19 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23734 Bug ID: 23734 Summary: Defaults set during patron imports throws warnings 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Create a small import file, with minimal columns, tail the logs, import and note warnings IN DBIX/Class/Row: elsif ($self->_is_column_numeric($col)) { # do a numeric comparison if datatype allows it return $old == $new; But in Koha/Patrons/Import.pm We assume "" for all defaults Even if we pass defaults of '0' for these columns elsif ( $defaults->{$key} ) { won't be triggered by a 0 value, it should be 'exists' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21465] New: Overlaying with Patron Imports cannot be done if user id and cardnumber are the same.
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '19

19 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21465 Bug ID: 21465 Summary: Overlaying with Patron Imports cannot be done if user id and cardnumber are the same. Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the Koha version of 18.05 using the patron import tool, if a patron has the same userid and cardnumber, and a library attempts of overlaying an updated file on patron information into Koha, an error will occur. Test Plan 1. Create patron csv according to the download starter CSV in Koha. 2. Patrons were assigned a card number by the library and this card number was also used for their User ID. 3. Import the Patron CSV into Koha. 4. Adjust this same Patron CSV file adding/updating an address, adding/updating a field of data. 5. Use this new file to import into Koha 6 Choose to match on the cardnumber 7. Choose to overwrite the existing one with this file. 8. Koha will produce an error saying that the userid already in use by another patron. Different Scenario Do Steps 1-5 the same 6. Choose to match on the User Id 7. Choose to overwrite the existing one with this file. 8. Koha will do the overwrite correctly. Libraries do tend to give patrons a cardnumber and also use that as the patron's userid. It would appear that matching on the userid works, however, this should not work this way, it should be able to match on either and produce same results- a successful overlay. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 23920] New: Add preference to allow consortia to turn off purchase suggestions for branches that don't use it
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23920 Bug ID: 23920 Summary: Add preference to allow consortia to turn off purchase suggestions for branches that don't use it Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Similar to the PatronSelfRegistrationLibraryList Enable the self registration for the following libraries: (separate branchcode with |). If empty, all libraries will be listed. Allow multi-branch libraries to turn on purchase suggestions only for libraries that will use the feature. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 19364] New: KOHA title search pulls documents with author matches
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19364 Bug ID: 19364 Summary: KOHA title search pulls documents with author matches Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: nikeshn(a)gmail.com Author results also appears when I limit my search to title only. I think it appears because KOHA indexing treats statement of responsibility as part of title. Other ILS systems pull only title matches from tag 245, 505 and 490 etc. We migrated from Millennium to KOHA and Millennium pulls only documents matches the word in title, series etc. For example : melm 245$a Title-cover:w,Title-cover:p,Title-cover:s,Title:w,Title:p,Title:s melm 245$c Author,Author-in-order:w,Author-in-order:p,Author-in-order:s melm 245$9 Cross-Reference:w,Koha-Auth-Number Here KOHA treats 245 $c (statement of responsibility ) as part of title. Live Example : I searched for Shakespeare in Title but document with Shakespeare as an Auhtor also appear in the search result. Please see the link below. https://opac.kustar.ac.ae/cgi-bin/koha/opac-search.pl?idx=ti&q=shakespeare -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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 23822] New: No warning is produced when trying to delete a patron with credit (patron is not deleted)
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23822 Bug ID: 23822 Summary: No warning is produced when trying to delete a patron with credit (patron is not deleted) Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When one tries to delete a patron that has a credit in his account, no warning is produced. The deletion is not performed (which is the proper behavior), however one would expect to see a warning similar to the one that is produced when the patron has an unpaid fine, a checked out item, a hold, etc. The following screencast was performed in ByWaters' sandboxes running 19.05 and shows the issue: https://screencast-o-matic.com/watch/cq6D6vu4YJ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[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