December 2017 - Koha-bugs - lists.koha-community.org

[Bug 19562] New: Inventory: How can we skip convolutes marked as problematic with no_barcode?
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19562 Bug ID: 19562 Summary: Inventory: How can we skip convolutes marked as problematic with no_barcode? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org We have two biblio records, but one item. It is a convolute, a bound set of actually two items. We added one item to each biblio, added Convolute in the item notes and gave the bound set one barcode recorded in one of the items. When doing inventory and comparing with a barcode file, you can imagine that the item without the barcode (having the same callnumber as the item with the barcode) is reported as a problem (no_barcode). A simple custom solution is: $item->{problems}->{no_barcode} = 1 unless $item->{itemnotes} =~ /convolute/i; Do you have any suggestions or ideas to resolve similar problems with convolutes, if you have them ? How do you record this situation ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 19527] New: Alter Zebra indexing to sort by descending document ID
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19527 Bug ID: 19527 Summary: Alter Zebra indexing to sort by descending document ID 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: r.delahunty(a)arts.ac.uk We are receiving complaints about the sorting order of relevance ranked searches. One specific example was where the older edition of a work appears higher up the list than the more recent version. According to http://www.indexdata.com/zebra/doc/administration-ranking.html: “If one defines the staticrank:1 directive in the main core Zebra configuration file, the internal document keys used for ordering are augmented by a preceding integer, which contains the static rank of a given document, and the index lists are ordered first by ascending static rank, then by *** ascending *** document ID.” Would it not be better to have the secondary rank in terms of ** descending *** document ID? That way there is much better likelihood that the most recently published version of various editions will appear closer to the top of the OPAC list, and certainly (all else being equal) above the earlier edition(s) of the specific work. Ray Delahunty University of the Arts London -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 19779] New: Some notices not using Reply To email address
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19779 Bug ID: 19779 Summary: Some notices not using Reply To email address Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: rachel.dewar(a)cass.govt.nz QA Contact: testopia(a)bugs.koha-community.org If you specify a ReplyToDefault or a Branch ReplyTo email address some notices still do not use them. These are the ones that I have come across: - Holds - when a hold is placed on an item - Sharing a list - both the invitation to share a list and email confirming that the person has accepted the inviation - Overdue notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 18815] New: OpenLibrarySearch is broken
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18815 Bug ID: 18815 Summary: OpenLibrarySearch is broken 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When turning on OpenLibrarySearch the label OpenLibrarySearch will show last in all search result entries, but nothing will display after it. The web dev tools show an error: XML Parsing Error: not well-formed Location: https://openlibrary.org/search.json?q=de Line Number 1, Column 1: -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19591] New: Saving a system preference jumps to main page
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19591 Bug ID: 19591 Summary: Saving a system preference jumps to main page Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I don't know if this was intended or not. When saving a system preference, it jumps to the main page of the category, instead of staying on the searched system preference, like in 3.22. Test: 1. Search a system preference, i. e. Opaccredits. 2. Change something. 3. Save it. 4. It jumps to the "category subpage" on the left side. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 19147] New: Error when create new patron
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '18

30 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19147 Bug ID: 19147 Summary: Error when create new patron Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: j.jeyakumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Software error: Template process failed: undef error - DBIx::Class::Storage::DBI::_dbh_execute(): Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'koha_jeya.me.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by at /usr/share/koha/lib/Koha/Objects.pm line 120 For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19898] New: Koha 17.11 - Upload Local Cover Image Failed - " Cannot process file as an image"
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19898 Bug ID: 19898 Summary: Koha 17.11 - Upload Local Cover Image Failed - "Cannot process file as an image" Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbutosi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In Koha 17.11, I am trying to upload a .jpg image to a bibliographic record (as a local cover image). After uploading, then clicking "Process Images", I get the following error: "Cannot process file as an image. Cannot process file as an image. Please ensure you only upload GIF, JPEG, PNG, or XPM images." I've tried to upload the file as a .jpg, .png, and .gif. The error persists. I've also tried to upload a different .jpg file. The error still persists. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 18228] New: Working title
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '18

29 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18228 Bug ID: 18228 Summary: Working title Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 63

[Bug 17941] New: CanBookBeRenewed is very inefficient/slow
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '18

28 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17941 Bug ID: 17941 Summary: CanBookBeRenewed is very inefficient/slow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: boutrosboutrosboutros(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I started investigating why populating the checkout list in the patron view sometimes took ages (minutes), and on occations even causing the system to almost halt because of DB overload. It turned out that reason is calls to C4::Circulation::CanBookBeRenewed. The critical factor is whether an item has many holds on it, and if there are many items that can fill the hold. Briefly looking at the code it seems obvious that the time spent grows exponentially with the number of holds and items. As one example, checking if an item with 111 holds (and 12 items on the biblio) can be renewed takes around 25 sec and generates over 18,000 SQL queries. I can't help to think there must be some missed "early returns" opportunities in the loops somewhere. For example, if there are more unfulfilled holds than available items, can the item ever be renewed? If no, return before even begin to calculate.. However, I know holds are full of complexities and things I probably haven't thought about so I need to dig into the code more. I would be very gratefull if anyone knowledgeable about this part of the code could help me find some ways to optimize this! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 19468] New: Can't create basket in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '18

27 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19468 Bug ID: 19468 Summary: Can't create basket in acquisitions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 15685 When trying to create a new basket in acq, I get an internal server error: Can't call method "unblessed" on an undefined value at /home/vagrant/kohaclone/C4/Acquisition.pm line 829. I think this might be a side effect of the recently pushed bug 15685. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15685 [Bug 15685] Allow creation of items (AcqCreateItem) to be customizable per-basket -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5