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

Call for development news: May newsletter
by kohanews 15 May '15

15 May '15

Koha Development community ~ If you have any bugs or projects you'd like to highlight or promote in the May newsletter, please let me know. Maybe it'll attract some additional eyes, testers and sign-offs. k o h a news AT gmail dot com Thank you! -- Chad Roseburg Editor, Koha Newsletter

1 0

Call for news: May newsletter
by kohanews 15 May '15

15 May '15

Fellow Koha users ~ I'm collecting news for the May newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- * News items can be of any length. * Anything and everything Koha. * Submit by the 28th. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Newsletter

1 0

Learning Tools Interoperability
by Bob Birchall 14 May '15

14 May '15

Hi, I've been asked if Koha has support for LTI and if not, is it in a road map? I guess they mean this: http://en.wikipedia.org/wiki/Learning_Tools_Interoperability Its not something I have heard of before. Any thoughts? Thank you, Bob Birchall Calyx

2 3

LAST CALL - RFC for Bug 14048 - Change RefundLostItemFeeOnReturn to be branch specific
by Kyle Hall 12 May '15

12 May '15

Hey all, I posted this on April 22, and received no feedback. I just wanted to give everyone a second chance to post any feedback on the development plan for bug 14048. If you have any comments about it, please let me know! Otherwise, I'll assume everyone is ok with the development plan, and I can go ahead with writing this feature. Thanks! Kyle http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14048 Some library systems would like to be able to control the behavior of RefundLostItemFeeOnReturn Expected outcome: To make the RefundLostItemFeeOnReturn system preference branch specific Plan of Attack: 1) Add new field 'refund_lost_item_fee_on_return' to the 'branches' table 2) Pre-populate this field with the system preference value for RefundLostItemFeeOnReturn 3) Remove the system preference RefundLostItemFeeOnReturn 4) Replace uses of RefundLostItemFeeOnReturn with a lookup of the value of branches.refund_lost_item_fee_on_return 5) Use HomeOrHolding to control whether the home branch or the holding branch of the item is used to determine this. 6) Reveal the setting in the branches editor http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )

2 2

Field width for currency.currency is inadequate
by Indranil Das Gupta 11 May '15

11 May '15

Hi all, The database field currency.currency is defined as VARCHAR(10) NOT NULL. This needs to be increased e.g. set as VARCHAR(255) NOT NULL. The rationale: a) While it is possible to accomodate 'US Dollar' in that width, for many currencies this space is inadequate e.g. 'East Caribbean Dollar', 'Indian Rupee' or 'Tanzanian Shilling'. b) Further, in the 'New currency' addition form, the maxlength and size attributes are set as 50, and allows user to enter long names as examples above. While saving the record, it is truncated to VARCHAR(10). I propose the following: 1/ Alter the currency.currency field to VARCHAR(255) NOT NULL from VARCHAR(10) NOT NULL. 2/ Change the 'maxlength' attribute in the template to 255 (to match column property) The bug and the patches are here http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14179 cheers -idg -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

2 1

I think I just messed up on signing 13673
by Indranil Das Gupta 09 May '15

09 May '15

first timer mess-ups http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13673#c6 how do I revert this? thanks! -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

3 2

staff member responsible of loan/renewal recorded in issues?
by Giuseppe Angilella 08 May '15

08 May '15

Dear Kohaers, is the information concerning which staff member was responsible of a loan or renewal of a given item recorded anywhere in the database? I couldn't find it in the "issues" tables. Assuming it is not, it could be a relevant information to record, in cases where several staff members (or even all patrons) have issueing privileges. Many thanks, Giuseppe.

2 1

Re: [Koha-devel] [Koha] Jenkins & the Manual
by Bernardo Gonzalez Kriegel 07 May '15

07 May '15

It's strange, I have no problems with the repo, but Jenkins seems to have. Fetching upstream changes from git://git.koha-community.org/kohadocs.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress git://git.koha-community.org/kohadocs.git +refs/heads/*:refs/remotes/origin/* ERROR: Timeout after 10 minutesERROR <http://stacktrace.jenkins-ci.org/search?query=ERROR>: Error cloning remote repo 'origin'ERROR <http://stacktrace.jenkins-ci.org/search?query=ERROR>: Error cloning remote repo 'origin' -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com On Thu, Apr 30, 2015 at 7:29 PM, Nicole Engard <nengard(a)gmail.com> wrote: > Hi all, > > I don't know who manages this so I'm sorry to email everyone, but the > manual on Jenkins is a big screwy. > > http://jenkins.koha-community.org/ > > The 3.18 branch is missing and the master branch fails all the time > but it generates the HTML and PDFs a-ok and shows no errors when I > validate in Oxygen. Eventually the failures stop and it passes - so I > know nothing is wrong with the manual itself, I wonder if something is > screwy with the fact that the wrong branches are being checked. > > Nicole > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha >

3 2

Koha Community Newsletter: April 2015
by kohanews 06 May '15

06 May '15

Fellow Koha users: The Koha Community Newsletter for April 2015 is here: http://koha-community.org/koha-community-newsletter-april-2015/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! Chad Roseburg Editor, Koha Community Newsletter

1 0

Jenkins emails / explanation
by Tomas Cohen Arazi 06 May '15

06 May '15

We might have become used to not receiving Jenkins emails regarding regressions. So I decided to send this short explanation of what they are and what are the expected steps when you receive one. Jenkins sends emails to authors of patches that got pushed into the branch being tested, in the event of some tests starting to fail on that push. The expected behaviour from devs is to check the link provided, and browse to the 'Test results' section on the left (not sure the wording, mine is in spanish and didn't figure/look how to change it). There you'll see the failing tests. It is expected that you check if it is related to your patches, and in case it is, contact me or the release maintainer to talk about the problem introduced. This might yield to a followup on the bug, or a new bug. It will depend on the situation but I doesn't really matter. Right now some tests are failing randomly, and is consistent with us running the tests randomly too :-D (prove -s) It seems to mean that some of our tests do have side effects that change the scenario for the rest of the tests. Anyone interested in taking on this inter-test dependency please let me know. I don't have the time to do it right now, so close to the release. But fixing it (either the tests or the hidden bugs) would be great. It would make our tests and the product as a whole, just better. Kind regards -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

2 1