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

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

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

20 Sep '14

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

Introduction: Barton Chittenden, Bywater Solutions
by Barton 19 Sep '14

19 Sep '14

Hello, Koha-dev! A quick intro, per the mailing list welcome message. My name is Barton Chittenden, I do technical support for Bywater Solutions. I've been working there since November. Most of you probably recognize me as 'barton' on #koha. I wrote my first Perl script in 2000, and started doing ETL work (Extract/Transform/Load, aka data munging) around 2001 or 2002. I've been a Unix Weenie since 1995, and did my first Slackware Linux install in 1999. I've worked as a perl programmer in a Linux environment ever since. I tend to write perl and shell scripts in the course of trouble-shooting for Bywater, and I'm always looking for ways to automate the process of trouble-shooting. Koha is the first open source project that I've worked on. One of my goals over the next year or so is to get more involved with bug signoff, leading into QA. Eventually, I would like to do development. Thanks, --Barton

2 1

Re: [Koha-devel] Koha-devel Digest, Vol 106, Issue 23
by Vijaya Kumar 18 Sep '14

18 Sep '14

good morning koha users I am having our library bibliographic details above 2 lakhs records in iso 2709 format. please explain in details how to convert records iso2709 format in to koha software. thanking you, your sincerely dr.j.Vijaya Kumar Click here to Reply or Forward 1.7 GB (11%) of 15 GB used Manage <https://accounts.google.com/ManageStorage?hl=en> ©2014 Google - Terms & Privacy <https://www.gmail.com/intl/en/mail/help/terms.html> Powered by Last account activity: 35 minutes ago Details Azure StorSimple Solution <https://mail.google.com/mail/?tab=wm&pli=1#ad/273922/CLHi4Z6b6sACFSKaTAodlk…> On Wed, Sep 17, 2014 at 9:37 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: Koha and DBIC (Kyle Hall) > 2. Re: Koha and DBIC (Colin Campbell) > 3. Re: Koha and DBIC (Marcel de Rooy) > 4. Re: Koha and DBIC (Mark Tompsett) > 5. Re: Koha and DBIC (Colin Campbell) > 6. Re: Koha and DBIC (Chris Cormack) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 17 Sep 2014 06:40:09 -0400 > From: Kyle Hall <kyle.m.hall(a)gmail.com> > To: Jonathan Druart <jonathan.druart(a)biblibre.com>, Kyle Hall > <kyle.m.hall(a)gmail.com>, Koha Devel > <koha-devel(a)lists.koha-community.org> > Subject: Re: [Koha-devel] Koha and DBIC > Message-ID: > < > CACpVHfyZnF9jpWKW5hGcmXtG4eZFf+YpCzkJGiqEwhm11XkoEA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Chris, I'm a bit lost here. The idea behind Koha::Object is that we have a > common base class from which to derive Koha::Biblio, Koha::Serial and so > forth. That is, this class would be used as the base for classes that have > a simple 1 to 1 table mapping to encapsulate DBIC while maintaining a > consistent set of methods across our many classes. ObjectSet would give us > set iterators, set operations, and be a better place to have methods that > return a set ( e.g. Koha::Issue::Set::GetOverdues would return a collection > of overdue checkouts ). > > I'm not sure why you disagree with this idea. Could you expand a bit? > > Kyle > > > > -1 for DBIx::Class calls in the .pl > > -1 for Koha::Object and Koha::Object::Set > > +1 for proper objects like Koha::Biblio, Koha::Account, Koha::Serial etc > > > > Chris >

1 0

Re: [Koha-devel] Koha-devel Digest, Vol 106, Issue 20
by Vijaya Kumar 18 Sep '14

18 Sep '14

good morning koha users I am having our library bibliographic details of our library collection above 2 lakhs records in iso 2709 format please explain indetails how to convert in iso2709 from in to koha software. thanking you, your sincerely dr.j.Vijaya Kumar On Wed, Sep 17, 2014 at 4:02 AM, < 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: problem to perform a simple query (Adnier Rosello) > (Adnier Rosell? Carrazana) > 2. Dom indexing operational with a fresh install? > (Francois Charbonnier) > 3. Re: Dom indexing operational with a fresh install? > (Tomas Cohen Arazi) > 4. Re: Koha and DBIC (Kyle Hall) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Sep 2014 16:15:13 -0400 (CDT) > From: Adnier Rosell? Carrazana <arosello(a)uci.cu> > To: koha-devel(a)lists.koha-community.org > Subject: Re: [Koha-devel] problem to perform a simple query (Adnier > Rosello) > Message-ID: > <1412455981.134123159.1410898513042.JavaMail.zimbra(a)uci.cu> > Content-Type: text/plain; charset=utf-8 > > Robin: > apology not specify in my previous mail that my koha version is 3.0.6, > which has a preference variable to not use the zebra (NoZebra), so the > search of bibliographic records are handled directly by MySQL, grateful by > the response, I hope to clarify the problem, Greetings > > Ad > ----- Mensaje original ----- > 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: Koha and DBIC (Marcel de Rooy) > 2. Re: problem to perform a simple query (Robin Sheat) > 3. VIAF and Koha 3.16.x (Partha Mukhopadhyay) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Sep 2014 19:11:35 +0000 > From: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl> > To: Koha Devel <koha-devel(a)lists.koha-community.org> > Subject: Re: [Koha-devel] Koha and DBIC > Message-ID: > > <809BE39CD64BFD4EB9036172EBCCFA31423D34C8(a)S-MAIL-1B.rijksmuseum.intra> > Content-Type: text/plain; charset="iso-8859-1" > > > I am troubled by the idea that we should wrap all our dbic classes in > yet more classes. Every example I've seen of this has more code by a factor > of almost 10. I don't know if Koha is so complex that it requires a > repository pattern. > I think that it would require rewriting Koha. This changeover might just > be too complex for us. > > > How much more difficult will this be for developers, and how much more > overhead will it require if we wrap our objects in more objects? We'd have > to fetch the Row objects, wrap them in KohaRow objects, wrap those in a > KohaRowSet, and return them. Certainly, but far more complicated. > I would say: Leave all storage related actions in Koha::Schema. KohaRow > does not make sense to me. > Furthermore, define the objects that actually have 'real' business logic > and put that in some Koha::Object. > > Marcel >

1 0

Call for development news - September Newsletter
by Koha News 18 Sep '14

18 Sep '14

Koha Development community ~ If you have any bugs or projects you'd like us to highlight or promote in the September 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: September Newsletter
by Koha News 18 Sep '14

18 Sep '14

Fellow Koha users ~ We're collecting news for the September 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

Rebase after passing QA?
by Holger Meissner 17 Sep '14

17 Sep '14

Dear Koha devs, a few weeks ago one of my patches passed QA. By now it doesn't auto-merge with master anymore. I suspect the conflicts can be resolved without too much trouble. Should I rebase, keeping the Passed QA status? Or should I rebase and set back to Signed Off? Or leave it to the RM to rebase? Thanks Holger

3 2