November 2016 - Koha-bugs - lists.koha-community.org

[Bug 17255] New: Upgrade Elastic Search code to work with version 2.4+
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '17

20 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17255 Bug ID: 17255 Summary: Upgrade Elastic Search code to work with version 2.4+ Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Before building more things on Elastic (I have 3 things ready to go) We need to upgrade to work with the latest stable (2.4) This will involve getting a 2.4 cluster running, pointing Koha at it, and fixing any errors that occur. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 17519] New: Item editor handles clearing dateaccessioned and replacementpricedate inconsistently
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '17

18 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17519 Bug ID: 17519 Summary: Item editor handles clearing dateaccessioned and replacementpricedate inconsistently Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging 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 22

[Bug 17366] New: create patron list, software error
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '17

15 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17366 Bug ID: 17366 Summary: create patron list, software error Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: arunet(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When we try to create patron lists the getting software error cgi-bin/koha/patron_lists/add-modify.pl getting software error Software error: Can't call method "patron_list_id" on an undefined value at /usr/share/koha/intranet/cgi-bin/patron_lists/add-modify.pl line 55. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17533] New: Syncing private to public list or adding more specific permissions?
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17533 Bug ID: 17533 Summary: Syncing private to public list or adding more specific permissions? 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 I now have two lists: private list A (shared between some users), and public list B. A local custom cron job daily syncs changes from A to B. What I would like, is: Let this group of users that now share A, have permissions to add/delete entries from public list B (but no one else). The current permission strategy on public lists is all or nothing, but not just a group of selected users. What would be the best way to go to achieve this goal? What about giving staff users the right to add/delete entries from public lists? In my specific case the editors include a normal user ;) Redesign the whole permissions thing on lists? Aarg. Add a sync lists option? What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16961] New: Add the Koha::Objects->update method
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '17

08 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16961 Bug ID: 16961 Summary: Add the Koha::Objects->update method Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org In order to update several rows in a single query, we need this new method. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 17327] New: Item level holds no longer enforced
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '17

28 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17327 Bug ID: 17327 Summary: Item level holds no longer enforced 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Reported by Katrin: Example: - on shelf holds allowed - holds allowed 5 - holds on same record allowed 5 - FORCE item level holds On a record with only one item, you can only place a record level hold in OPAC now - which is against your circulation conditions. Another example: - record with 2 items - circulation rules as above, 1 hold allowed on the record - Item level holds: forced I can only place record level holds in OPAC and staff. At the moment, I am not able to place item level holds in any circumstances in my installation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 16984] New: Acquisitions broken
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16984 Bug ID: 16984 Summary: Acquisitions broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In acquisitions, even if AcqCreateItem is set to create an item at the time of ordering, the item creation form does not display. Instead, this JavaScript error shows in the console: additem.js:176 Uncaught TypeError: window[events[i]] is not a function I believe this regression was introduced by bug 15531. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 16115] New: JavaScript error on item search form
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16115 Bug ID: 16115 Summary: JavaScript error on item search form Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/catalogue/itemsearch.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In the template for the item search page there is this at line 290: { 'type': 'select', 'values': [% notforloans.json %] }, [% notforloans.json %] appears to be undefined, whether the search form has been submitted or not. Viewing source shows this: { 'type': 'select', 'values': }, ...and the Firebug console reports this error: SyntaxError: expected expression, got '}' /cgi-bin/koha/catalogue/itemsearch.pl Line 240 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 17487] New: Improper placement of select/clear all in Z39.50/ SRU search dialog
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '17

23 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17487 Bug ID: 17487 Summary: Improper placement of select/clear all in Z39.50/SRU search dialog Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Links allowing to select/clear all Z39.50 servers have icons next to the text. These links are improperly placed in the case the localized caption is a bit longer than English version, see picture: http://prntscr.com/cy0bey In addition, these links are placed in an <h2> header, but it's not semantically correct. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 17414] New: Add GIR codes added to Edifact since 1.2
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '17

21 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17414 Bug ID: 17414 Summary: Add GIR codes added to Edifact since 1.2 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org 4 new GIR codes have been added to Edifact since version 1.2 see http://www.editeur.org/files/EDIfact%20eancom%20pdfs/EDIfact%20library%20su… The following codes have been added to DE 7405: LHC Library Holding Code: may hold a combination of information i ncluding location , sequence, item type etc. as a single data string (contents defined by the library). LRP Library Rotation Plan: a code number assigned by a library to identify a rotation plan to which an item belongs. LSC Statistical category: a c ode used by a library to identify a statistical category (e.g. „605‟ or „Children‟s Picture Books‟) for management reporting purposes. RIC Reader Interest Category: code to identify stock at a lower level than LST (Stock Category) eg. Western, Science Fiction. These need to be added to list of recognized codes for future developments ( e.g. to include Stock Rotation intp in LRP ) to be able to utilize these -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11