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

[Bug 14481] New: Warns when setting permissions for patron
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14481 Bug ID: 14481 Summary: Warns when setting permissions for patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate warns, go to any patron and click More --> Set permissions (ie follow this link http://localhost:8081/cgi-bin/koha/members/member-flags.pl?member=1369) member-flags.pl: Use of uninitialized value $roadtype in concatenation (.) or string at /home/vagrant/kohaclone/members/member-flags.pl line 176 member-flags.pl: Use of uninitialized value $roadtype in concatenation (.) or string at /home/vagrant/kohaclone/members/member-flags.pl line 176 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 4041] Address Format as a I18N/L10N system preference
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4041 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |15542 Referenced Bugs: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15542 [Bug 15542] Patron's information are not always displayed the same way -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 15539] New: Create a ccl.properties alias for Identifier-other
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15539 Bug ID: 15539 Summary: Create a ccl.properties alias for Identifier-other Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl At the moment, the only way to access "Identifier-other" via CCL is to use "id-other" which is paired with 9012 in ccl.properties which is paired with "Identifier-other" in bib1.att. At a glance, it's not obvious that "id-other" is the qualifier for "Identifier-other", so I propose making an alias of "Identifier-other" which points to "id-other" or "1=9012". -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15536] New: Additional match check comparison operators
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15536 Bug ID: 15536 Summary: Additional match check comparison operators Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org When http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12586 is pushed, the "required match checks" will work for Bibliographic records once again. At the moment, match checks work on an "equal" comparison, but I'm thinking it might be useful to have additional comparisons like >, <, >=, <=, and !=. (Well, string and numeric comparison operators...) Example: - Record 1b 005 > Record 1a 005 Import only if the record's 005 is newer than the existing record's 005. Admittedly, that's the only feasible example I can think of off the top of my head at the moment. I suppose you might require that the 942$c be "not equal" before updating, if you only want to update a subset of records that are missing some information. I suppose you should have figured that out beforehand and only tried importing the records you actually want to change. You might try a match check where the 250 edition statement is > or < but since it's a free-text field, that would probably be a bad idea. I suppose most cases of using additional comparison operators might be in regards to arbitrary data. Like maybe you only want to update target records if the match result has a 999$c < 1000 or something like that, but that seems unlikely and unwieldy at best. Just throwing it out here as an idea. It could be useful for the 005 at least. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12366] New: Better handling of Zebra errors when searching empty indexes
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12366 Bug ID: 12366 Summary: Better handling of Zebra errors when searching empty indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, if you turn on "OpacSuppression" (i.e. Hide) or "dontmerge" (i.e. Do), Zebra will return errors, if the OpacSuppression index is empty or if the Koha-Auth-Number index is empty. You'll encounter the "dontmerge" problem if you try to merge together two authorities when there are no biblio records in the database that have already been linked to an authority. I suppose this could be an edge case, but getting a software error on the screen saying "ZOOM error 114 Unsupported Use attribute" (addinfo: Koha-Auth-Number") from diag-set 'Bib-1" isn't really that helpful. We should either add a warning on the system preference "dontmerge" (that says that you must have one biblio already attached to an authority if you don't want errors when set to "Do") or handle the error from Zebra more gracefully. Admittedly, handling the error generated by OpacSuppression is probably harder. At the moment, I think it'll say that there are no results (as Zebra will error out). I suppose that might be the best we can do...but it's still sub-optimal. Another idea is to populate OpacSuppression with a dummy record, although that's also sub-optimal. I suppose this might just be one of the downsides of using Zebra... But a warning is probably a good idea in any case for "dontmerge", although I suspect that most people probably use the "Don't" setting, or already have at least one biblio linked to an authority... -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 15531] New: Add support for standing orders
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '16

10 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15531 Bug ID: 15531 Summary: Add support for standing orders Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: nicole(a)bywatersolutions.com A new kind of standing order basket, with the following behavior: * Items can be received without the basket being closed. * Items can be received without their price being known in advance. * Creation of items upon receive customizable per-basket -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 15456] New: Fix tabs and inconsistent indentation in smart-rules.tt
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '16

10 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15456 Bug ID: 15456 Summary: Fix tabs and inconsistent indentation in smart-rules.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 4338] Consistent Interface To Currency
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '16

10 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4338 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think some of the problems have probably been addressed by the tax rewrite. This is a really old bug and there are no other bugs dependent on it. I think we will need more specific information about remaining issues to continue here. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 14571] New: using_https check for ssl connections doesn't work in some situations
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '16

10 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14571 Bug ID: 14571 Summary: using_https check for ssl connections doesn't work in some situations 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: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org This is especially problematic for Amazon images, since if the check fails the normal images are used, causing mixed content warnings. I think we should remove the checks from Amazon images in the OPAC and just use the https Amazon url's for images. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 14133] New: Print notices generated in special case do not use print template
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '16

08 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14133 Bug ID: 14133 Summary: Print notices generated in special case do not use print template Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10832, there are specific cases where print notices are generated (If a user don't have a smsalertnumber and a sms is required or if a user don't have an email defined and an email is required). But in this case, the template used is not print one, but sms or email. The pb is that in that case, there is no way to identify the borrower that should receive this message (especially for sms where the message is very brief) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18