October 2014 - Koha-devel - lists.koha-community.org

3.18 Feature Freeze is near!
by Katrin Fischer 28 Oct '14

28 Oct '14

Hi all, just a reminder that the feature freeze is very close now: Halloween.... 31st October! This is the deadline for enhancements and new features to make it through QA and into the next 3.18 release. So if you can, make some time this week to help us clean the queues - sign off and QA! Katrin [http://meetings.koha-community.org/2014/general_irc_meeting_22_october_2014…]

3 2

KohaCon14 is over, welcome to KohaCon15 in Ibadan (Nigeria) !
by Paul Poulain 28 Oct '14

28 Oct '14

Hello, KohaCon14 is now done. We had a great time in Cordoba: lot of talks, lot of code, lot of (good) food and drink (beer). Every year, the next KohaCon location is announced at the end of the KohaCon. This year, we had only one candidate, so they win the deal ! Congratulation to Ibadan, Nigeria, that will host the KohaCon15. If you want more info, you can have a look at http://wiki.koha-community.org/wiki/KohaCon15_Proposals Note that we already have one candidate for KohaCon16, in the Philippines (http://wiki.koha-community.org/w/index.php?title=Kohacon16_proposals) (It's not time to vote for KohaCon16, we will do that in Q2/Q3 2015. We will call for candidate "officially" in april/may) -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

1 0

Conventions for CLI scripts
by Robin Sheat 23 Oct '14

23 Oct '14

There's been talk of making a few conventions for the parameters to command-line scripts. The initial discussion was dealing with "test mode" where it runs through all the actions but doesn't actually do anything, i.e. you know if it'll complete successfully. 1. There are two directions for this: I. By default the action will be performed, unless you add an argument (--dry-run for example.) II. By default the action will not be performed, unless you add an argument (--commit for example.) 2. What do we want to call the options, whichever way is picked? I. Keeping in mind that some things (-c for example) can conflict with other conventions. 3. Are there any other conventions we should deal with at the same time? While I have your attention, we should be more careful about how the dry run stuff is actually done. I've found one script that gives you a different count if you're in dry run mode (e.g. it'll say "0 actions done") which is strictly correct, but means you don't know if it's 0 because something's wrong, or because it's in dry run mode. Unless there's a good reason, it's best to do everything in a commit, so something like: $dbi->begin_work; ...do stuff... print "$count actions done.\n"; if ($dry_run) { $dbi->rollback; print "Changes NOT committed.\n"; } else { $dbi->commit; } This also has the side effect that if your program crashes in any mode, you're not left with an inconsistent result. But mostly it means that /everything/ will happen in exactly the same way no matter what, except the results just won't be saved. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

4 8

hea.koha-community.org
by Paul Poulain 22 Oct '14

22 Oct '14

Hello koha-devel, During previous Hackfest in Marseilles, some of us started to work on a tool to collect data from koha libraries, to have stats and feedback. A first version of http://hea.koha-community.org website is live. We (BibLibre) have started deploying the patch to our customers to retrieve informations, and see how things goes. Everything is OK as fas as we can see. Informations are interesting, imo. the hea website will have to be improved later, what is important is to gather data. We already get some informations like number of biblios, items, issues, as well as some syspref. In the next weeks, we will submit the patch to bugzilla, and I hope it will be quickly signed, QAed and pushed. What would really be great would be to have the feature in Koha 3.18. Note that this feature has no impact on Koha itself, it's only a syspref and a cronjob, so no side-effect to fear. -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

2 2

Hackfest in Marseille 2015, dates ?
by Paul Poulain 20 Oct '14

20 Oct '14

Hello ladies and gentlemen, The KohaCon14 hackfest is over, time to think about the next hackfest in Marseilles, in Q1 2015... A general question to anyone who would try to come: is there any date in February or March that would be impossible for you ? If yes, please say it (something like : "feb 10-15 => impossible for me, there's IFLA big conference in New York I'll attend" or "March 4-11 => impossible for me, I'll be skying". Or even "March 3-8, impossible for me", without any reason given ;-) ) Once I've collected "impossible dates", I'll try to find a date that pleases everybody ;-) -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

1 0

Call for development news - October Newsletter
by Koha News 16 Oct '14

16 Oct '14

Koha Development community ~ If you have any bugs or projects you'd like us to highlight or promote in the October newsletter, please let us 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 Joanne Dillon Editors, Koha Newsletter

1 0

Call for news: October 2014
by Koha News 16 Oct '14

16 Oct '14

Fellow Koha users ~ We're collecting news for the October 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 26th. If you are working on an interesting project or development related to Koha, please let us know and we'll include it in the development section. -- Chad Roseburg Joanne Dillon Editors, Koha Newsletter

1 0

Cataloging and linking to authorities subfield ORDER!
by Dhd Koha (grharry) 15 Oct '14

15 Oct '14

Hi, My librarian complains that when in cataloging and in particular when he links a biblio marc record to an authority existing record, he needs the order of the subfields copied from the authority to be intact and according to the authority record! For instance When he wishes to link to marc_field XXX subfields ($a, $y, $x, $z) then the subfields of the final marc record should be in the same order and *not* as the defined in the subfields of this marc framework for this TAG! Say there is a field 444 and subfields defined are a,y,x,z The tags and the RECORD Types are just example tags we need to link and copy fields from Authority record type "AN_AUTHORITY_TYPE_RECORD" but inside the Authority record the fields are saved with the order ( a, z, y, x ) So we need them also to be saved in the biblio marc record as tag 444 $a ..... $z ..... $y...... $x ......... So far when cataloging the subfields are stored with the same order as they appeared in the subfields definition of the MARC framework !! Problem 2 Also playing around and observing the js cataloging code we found that the perl function in the Authority.pm my $record=eval {MARC::Record->new_from_xml(StripNonXmlChars($marcxml),'UTF-8', (C4::Context->preference("marcflavour") eq "UNIMARC"?"UNIMARCAUTH":C4::Context->preference("marcflavour")))}; is not honoring any order at all, not the framework subfield definition and not the Authority record subfields existing order ! Is there a solution to this? Is there anybody else with the same issue in hand ??? Regards Harry!

1 0

Photos from KohaCon14
by Paul Poulain 15 Oct '14

15 Oct '14

Hi, I've added a chapter to the wiki page http://wiki.koha-community.org/wiki/KohaCon14, suggesting to add links to the photos you've published. I've put mine (with 100+ photos, more coming) -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

1 0

Proposed addition to the development-meetings:
by Brendan Gallagher 10 Oct '14

10 Oct '14

Hello All - I'd like at have an addition to the development-meeting. The idea is that, I would present some of the older bugs or even some new ones that really need to have a discussion that results in a solid agreed upon path forward. For example we have 2~3 methods for using DBIC for Koha code where we really need to decide on one path and move forward with that design. The method that I would like to add to the dev-meetings is that I will bring up certain topics at a development-meeting as a homework assign, so that we can all discuss that idea/bug/thought at the next meeting. Along with the first homework assign I will also be setting a date for us to vote on the (homework) bug/enh/thought at the meeting after a sufficient discussion has occurred. The main goal here is to set some deadlines for some of these larger discussions so that we can all move forward. Any meetings that I know I will miss I will find a representative to fulfill this role at the development-meetings. Thanks, Brendan Gallagher ByWater Solutions

1 0