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

Presentation to mailing list: akafred
by akafred 02 Oct '14

02 Oct '14

Hi! Just a short intro as per the welcome mail: I am contracted by the Oslo Public Library (Deichmanske bibliotek) in Norway to help out in their efforts to build systems for their new library that will open in Oslo in a few years. Koha has been chosen as a cornerstone in this effort. I have been working as a consultant for 15+ years, developing business critical systems for clients in and around Oslo. I LOVE programming, but I also have a passion for quality and a certain disdain for repetitive tasks, and error prone, manual, routines - so I am very into Test-Driven Development (London-style), automation (e g using provisioning tools like Ansible, SaltStack, Puppet, Chef) and prefer properly tested deployment units (like a jar, war, Docker image or, if all else fails, a virtual machine image). Generally, I think learning is what all development efforts should optimize their efforts for, and that transparency, collaboration and rapid feedback are key ingredients in achieving that. The better we are at learning the better we will be at creating awesome stuff that works for our end users. We are in an early phase in our efforts but if you are curious a lot of what we do will be publicly available on our github profile: https://github.com/digibib These days we are looking into how to deploy Koha in Docker. My real name is impossible for non-Norwegians to parse, remember and pronounce so on the interwebs I mostly go by a nickname I chose in a moment of general unclarity and confusion: "Fred" ... so I am a.k.a Fred .... akafred. I try to stop by #koha as akafred, but not always 'there' even if it looks like it - koha(a)akafred.com works though. See ya :-) Regards, - Kjetil a.k.a. "Fred"

4 3

Dom indexing operational with a fresh install?
by Francois Charbonnier 02 Oct '14

02 Oct '14

Hello, Yesterday, I bumped into an indexing bug. The 008 language code is not indexed. I can't find the records using this value. I checked on bugzilla and found this old bug : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7586. This bug changed "ln:n" by "ln:w" in record.abs . It works with grs-1 indexing. On Katrin advice, I checked if the installation is using dom or grs-1 indexing. I'm on 3.14.07. So it should use dom. koha-conf.xml says "dom" but zebra-biblios.cfg seems to say "grs"... So, I checked "zebra-biblios.cfg" on master and the default values are : * iso2709.recordType:grs.marcxml.record * marcxml.recordType:grs.sgml * recordType:grs.xml Shouldn't we have a reference to dom for these parameters? I also checked biblio-zebra-indexdefs.xsl and biblio-koha-indexdefs.xml and the language index is "ln:n". I tried to change it by "ln:w", restarted zebra server, reindexed but it didn't work. I followed the wiki instruction (http://wiki.koha-community.org/wiki/Switching_to_dom_indexing) to change the "zebra-biblios.cfg" values as well but didn't work either. Any ideas? Thanks! -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

3 5

OPAC items location (shelf)
by Paul A 02 Oct '14

02 Oct '14

I've looked through the wiki and bugs.koha... but can't seem to find anything relevant. opac-search.pl (if it finds more than one result) produces a line that reads e.g. "Availability: Copies available: 2nd floor rare (2)," using opac-results.tt which relies on data 'available_items_loo.location' The 'location' that it uses is the one that is defined in the *default* framework (952$c "Other options/Authorized value") (and, by the way, appears to use the raw "auth. value" strings, not the "Description (OPAC)" strings.) It appears that if you define, say for videos, a different set of "Auth. values" (LOC2 instead of LOC) for the "video framework 952$c", this is not picked up by opac-search.pl (for the Main OPAC search page which now reads "Availability: Copies available:(2), "), but is picked up by opac-detail.pl in the proper place in the holdings tab. If you change the "default framework" to use LOC2, it works for "videos", but "book" locations disappear. Maybe I've missed something very obvious, if not I'll try and delve deeper. We have literally hundreds of "locations" and to avoid very long lists in the admin item cataloguing drop down boxes, I've been asked to subdivide them... (LOC2 is fully functional per item type, but introduces the above "loss of functionality" in the OPAC.) The only "work around" that I can quickly find is to put *all* possible locations into LOC, and use LOC2, LOC3 etc for item types -- but this leads to a very ugly page in the "Shelving location" tab at advanced search <http://opac.navalmarinearchive.com/cgi-bin/koha/opac-search.pl>. Thanks and best regards, Paul

1 0

Koha 3.14.10 released
by Fridolin SOMERS 02 Oct '14

02 Oct '14

The Koha community is proud to announce the release of 3.14.10. This is a maintenance release and contains some enhancements and several bugfixes. As always you can download the release from http://download.koha-community.org. Have a look at release post : http://koha-community.org/koha-3-14-10-released "Get the pie while it's hot" Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

2 2

Re: [Koha-devel] Regarding SMS Integration with Koha
by Jonathan Druart 25 Sep '14

25 Sep '14

The driver module is on the cpan: http://search.cpan.org/~nobull/SMS-Send-Clickatell-0.02/lib/SMS/Send/Clicka… You just have to fill the pref SMSSendUsername SMSSendDriver with Clickatell. The driver needs 3 values: api_id, user and password. Only the password can be filled by one of the Koha sms pref (SMSSendPassword). I developed a patch to permit to pass more than the "login" and "password" parameter to the driver. It has not been submitted on bugzilla. You can find it on the BibLibre repository: https://git.biblibre.com/biblibre/kohac/commit/49644ebf043c92ed0665388d1d29… The short version is: it won't work out of the box. Regards, Jonathan PS: Please answer to the list. 2014-09-25 9:29 GMT+02:00 Dp Tripathi <dptnitrkl(a)gmail.com>: > Dear Sir, > > Clickatell is company which provides the script to send the SMS. The same > name is recommended in Koha manual also to start sms, integrate anyone of > the following such as > > Clickatell > > Wadja > > ipipi > > Sir, if you have driver, please help me and send me the script and also > guide me to integrate. I will be highly thankful to you. > > Thanks, > > On Thu, Sep 25, 2014 at 3:25 AM, Jonathan Druart > <jonathan.druart(a)biblibre.com> wrote: >> >> Hello D.P., >> >> What is the "Clickatell perl script"? >> You need to write a driver based on SMS::Send::Driver. >> >> Regards, >> Jonathan >> >> 2014-09-25 6:13 GMT+02:00 DP Tripathi <dptkvs(a)gmail.com>: >> > Dear Friends, >> > >> > I am trying to integrate Clickatell Perl Script in order to send SMS >> > through >> > Koha in India but failed to do so. >> > >> > If anyone please help me how to set this? >> > >> > Thanks >> > >> > -- >> > ********************* >> > D. P. Tripathi >> > Assistant Librarian >> > Biju Patnaik Central Library >> > NIT Rourkela >> > Odisha - 769008 >> > ********************** >> > >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel(a)lists.koha-community.org >> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> > website : http://www.koha-community.org/ >> > git : http://git.koha-community.org/ >> > bugs : http://bugs.koha-community.org/ > > > > > -- > ************************************************************ > Dhanwantari Prakash Tripathi > Assistant Librarian > Biju Patnaik Central Library > National Institute of Technology > Rourkela, Odisha - INDIA > 769008 > e-mail: tripathidp(a)nitrkl.ac.in, dptnitrkl(a)gmail.com > mobile: +91-8895296796 > URL: www.librarianguide.co.in > URL: www.koha.librarianguide.co.in > URL: www.forum.librarianguide.co.in > ************************************************************

1 0

Regarding SMS Integration with Koha
by DP Tripathi 25 Sep '14

25 Sep '14

Dear Friends, I am trying to integrate Clickatell Perl Script in order to send SMS through Koha in India but failed to do so. If anyone please help me how to set this? Thanks -- ********************* D. P. Tripathi Assistant Librarian Biju Patnaik Central Library NIT Rourkela Odisha - 769008 **********************

2 1

Reminder: Koha general IRC meeting 24 September at 14:00 UTC
by Owen Leonard 24 Sep '14

24 Sep '14

The next Koha general IRC meeting will be taking place in just a couple of hours! http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… The agenda is here: http://wiki.koha-community.org/wiki/General_IRC_meeting_24_September_2014 -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

1 0

Koha Developer IRC meeting 23 September 2014 at 15:00 and 22:00 UTC
by Tomas Cohen Arazi 22 Sep '14

22 Sep '14

I'm calling for a dev meeting next week, dedicated to DBIC discussions. We'll have DBIC's Peter Rabbitson on the IRC channel to hear his POV too. He can attend 15:00 UTC only though. I'll be happy to have all positions explicitly stated, and discussed. If we can make a decision, that's bonus points. Please send me your POV so I can put that on the wiki to sumarize what we already discussed. Otherwise, i'll do my best to be impartial. -- 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

Sign-off request for Bug 12162 - Add class="branchcode" to body tag to make OPAC CSS-styleable per branch
by Marc Véron 20 Sep '14

20 Sep '14

Hi Koha community, A couple of weeks ago I submitted a patch that makes the OPAC CSS-styleable per branch: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12162 It would be great if somebody would have time to for a sign-off. Thanks and regards Marc

1 0

Re: [Koha-devel] Koha-devel Digest, Vol 106, Issue 27
by indradg 20 Sep '14

20 Sep '14

The easiest option usually involves engaging a Koha consultant or consulting company. There is a list on the website - Paid Support. Sent from Samsung Mobile -------- Original message -------- From: Vijaya Kumar <kumarjammala(a)gmail.com> Date:20/09/2014 11:36 (GMT+05:30) To: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] Koha-devel Digest, Vol 106, Issue 27 GOOD MORNING KOHA USERS, KINDLY ARRANGE TO SEND EASY METHOD RELATAED TO HOW TO INSTALL KOHA SOFTWARE ON LINUX PLATFORM. THANKING YOU YOU, YOURS SINCERELY DR.J.VIJAYA KUMAR On Fri, Sep 19, 2014 at 3:30 PM, <koha-devel-request(a)lists.koha-community.org> wrote: Send Koha-devel mailing list submissions to koha-devel(a)lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request(a)lists.koha-community.org You can reach the person managing the list at koha-devel-owner(a)lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Re: Conventions for CLI scripts (Mark Tompsett) 2. Re: Conventions for CLI scripts (Owen Leonard) 3. Koha Developer IRC meeting 23 September 2014 at 15:00 and 22:00 UTC (Tomas Cohen Arazi) 4. Re: Conventions for CLI scripts (Robin Sheat) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Sep 2014 09:29:42 -0400 From: "Mark Tompsett" <mtompset(a)hotmail.com> To: "Koha Devel" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Conventions for CLI scripts Message-ID: <BLU172-DS12DBBBF2EE72A0544E626FC6B70(a)phx.gbl> Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Greetings, > 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.) If you run a script called DestroyTheDatabase, you would expect the default action to be complete and utter deletion. I think a dry-run flag would make sense for this type of script. The problem is those scripts whose name is not indicative of DB modifications. I suspect you are thinking about checkNonIndexedBiblios.pl which only runs if you include -c, much like point 1 subsection II. The name doesn't suggest default modifications. In this case, you have to add the -z which will then insert the non-indexed Biblios into the zebra queue. This is like the second method. Can we have a mix? Does a mix make any sense? This kind of reminds me of the help for scripts issues I was wondering about. I see a script name, other than reading the code, how do I get a sample use page? Do we force help on users if no parameters are passed? Do we expect a particular letter or phrase? --help -h --usage --examples --something-else? checkNonIndexedBiblios.pl does it both ways. > 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. Are there different conventions to choose from? How does Debian (Ubuntu, etc.) do it? > 3. Are there any other conventions we should deal with at the same > time? None of which I am aware. [SNIP] +1 on the turning off auto-commit, so dry runs do the same as actual runs. +1 on the explicit rollback or commit. > $dbi->begin_work; Actually, I guess that is a nicer way of doing this? # Start transaction $dbh->{AutoCommit} = 0; $dbh->{RaiseError} = 1; GPML, Mark Tompsett ------------------------------ Message: 2 Date: Thu, 18 Sep 2014 09:37:33 -0400 From: Owen Leonard <oleonard(a)myacpl.org> To: Koha Devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Conventions for CLI scripts Message-ID: <CAO4qe2PLYna57wQqeFX56KXK=rS_235Bdf2YSVnd03wO063h9g(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 > Do we force help on users if no parameters are passed? As a non-expert in command line things, this is what I would expect. At the very least a brief help, with the suggestion that passing --help would give more. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ------------------------------ Message: 3 Date: Thu, 18 Sep 2014 12:05:23 -0300 From: Tomas Cohen Arazi <tomascohen(a)gmail.com> To: koha-devel <koha-devel(a)lists.koha-community.org> Subject: [Koha-devel] Koha Developer IRC meeting 23 September 2014 at 15:00 and 22:00 UTC Message-ID: <CABZfb=X94ca854xgq0enhSj+4iemD1ez1zm3S_99nrU2B8S96A(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" I'm calling for a dev meeting next week, dedicated to DBIC discussions. We'll have DBIC's Peter Rabbitson on the IRC channel to hear his POV too. He can attend 15:00 UTC only though. I'll be happy to have all positions explicitly stated, and discussed. If we can make a decision, that's bonus points. Please send me your POV so I can put that on the wiki to sumarize what we already discussed. Otherwise, i'll do my best to be impartial. -- 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

1 0