May 2015 - Koha-bugs - lists.koha-community.org

[Bug 14291] New: OpacExportOptions shouldn't say 'separated by |'
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14291 Bug ID: 14291 Summary: OpacExportOptions shouldn't say 'separated by |' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com OpacExportOptions is now a series of checkboxes so the preference description should be updated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 9234] New: Koha's search code needs to be rewritten
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9234 Bug ID: 9234 Summary: Koha's search code needs to be rewritten Classification: Unclassified Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: jcamins(a)cpbibliography.com Reporter: jcamins(a)cpbibliography.com Depends on: 9232, 9233 This is an umbrella bug to track all the bugs relating to the ongoing search rewrite discussed at http://wiki.koha-community.org/wiki/C_%26_P_Search_Rewrite_RFC -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 7978] New: Koha index-names have inconsistent CaPiTaLiSaTiOn
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7978 Priority: P5 - low Change sponsored?: --- Bug ID: 7978 Assignee: gmcharlt(a)gmail.com Summary: Koha index-names have inconsistent CaPiTaLiSaTiOn QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: mtj(a)kohaaloha.com Hardware: All Status: NEW Version: master Component: Searching Product: Koha i hope to send a patch to change all index-names to lowercase here's an example... ## @indexes: [ ### [ ### 'ab', ### 'Abstract', ### 'acqdate', ### 'allrecords', ### 'an', ### 'Any', ### 'at', ### 'au', ### 'aub', ### 'aud', ### 'audience', ### 'auo', ### 'aut', ### 'Author', ### 'Author-in-order ', ### 'Author-personal-bibliography', ### 'Authority-Number', ### 'authtype', [...] -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 14047] New: Sort z39.50 biblio servers by rank in derivate cataloguing doesn't work
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14047 Bug ID: 14047 Summary: Sort z39.50 biblio servers by rank in derivate cataloguing doesn't work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: z.tajoli(a)cineca.it QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you insert/modify a z39.50 server to use it in derivate cataloguing you can insert 'rank': [it] lets you enter where in the list you'd like this target to appear. If this is left blank the targets will be in alphabetical order. If you use authority servers it is OK. If you use bibliographic servers it doesn't work Now z39.50 bibliographic servers are sorted by id (insert order). This is because now we use DBIx in cataloguing/z3950_search.pl without an 'order_by'. The patch inserts 'order_by' instruction To test it: 1)Insert 3-4 z39.50 biblio servers and insert different values into 'rank' fields. 2)See the if you change 'rank', the order doesn't change 3)Apply the patch 4)See that now order is based on 'rank' and 'servername' -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 10900] New: Incorrect calling conventions accessing C4::Context
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10900 Bug ID: 10900 Summary: Incorrect calling conventions accessing C4::Context Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org While trying to write tests (bug 10895), I was frustrated for an excessively long time while trying to copy t/db_dependent/Members.t as a template. The problem became apparent when I actually stop to note the difference between a :: over a -> in the calling convention. C4::Context->method passes the object as the first parameter. C4::Context::function calls the routine in a purely functional way. C4::Context methods should be called in an object oriented manner, particularly things like C4::Context::set_userenv. Set/Get are very much OO things! As pieces get fixed, the patches will drop here. -- You are receiving this mail because: You are watching all bug changes.

1 68

[Bug 13664] New: Add password strength plugin
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13664 Bug ID: 13664 Summary: Add password strength plugin Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Add password strength plugin using complexify. This should be linked to system preferences, and apply to both staff and public logins. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 80

[Bug 13219] New: Add graphs to guided reports
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13219 Bug ID: 13219 Summary: Add graphs to guided reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: chris(a)bigballofwax.co.nz, fridolyn.somers(a)biblibre.com, gmcharlt(a)gmail.com, julien.sicot(a)gmail.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com, veron(a)veron.ch Depends on: 9915 Everybody likes a pretty graph ;) This patch adds the lightweight Charts.js javascript chart library and implements a couple of example charts on some guided reports. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 12820] New: SIP2 does not send rental charge fee!
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12820 Bug ID: 12820 Summary: SIP2 does not send rental charge fee! Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Koha's SIP2 implementation has facilities to send the fee amount ( BV ) for checking out a given item, but in our code, the fee amount is never set! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 14301] New: “No renewal before” does not accept 0 as parameter.
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14301 Bug ID: 14301 Summary: “No renewal before” does not accept 0 as parameter. Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: costalc(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com CIRCULATION AND FINE RULES: “No renewal before” does not accept 0 as parameter. Setting this parameter to 0 could enable issue due date as the only date to renew issues Explanation attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 14214] New: Automatic renewal to renew at end of due date
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '15

03 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14214 Bug ID: 14214 Summary: Automatic renewal to renew at end of due date Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fiona.borthwick(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is set to automatically renew, then there should be a straightforward way to set the value so that it will renew at the end of the due date. I have done substantial testing on this but cannot get it to do what I need. Setting the 'no renewals before' to 1 means that it will renew one day prior to due date. Setting it to -1 means that it will renew one day past due date - i.e. item is overdue. Setting the value to 0 in the Circulation Policies translates to null when saved and the 0 is removed. We established that we could get 0 into the database by entering 0.001. However this seems to be ignored as the automatic renewal is happening every day in the same way that it would if there was no value set in 'no renewal before'. We can change the timing of the automatic_renewal.pl script to run at a more convenient time (e.g. before the overdue processing) but we need the item to be able to be renewed at the end of its due date - not before and not after. This is especially important for items that have rental fees associated with them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5