From mtompset at hotmail.com Fri Apr 1 02:52:16 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Thu, 31 Mar 2016 20:52:16 -0400 Subject: [Koha-devel] Fw: Jenkins build is still unstable: Koha_Master_D7 #680 Message-ID: Greetings, I know that bugs 16173, 16174, 16176, and 16178 would solve 6 (I think) of the 9 remaining problems. They just need QA and pushing. GPML, Mark Tompsett -----Original Message----- [SNIP] Subject: Jenkins build is still unstable: Koha_Master_D7 #680 See From mtompset at hotmail.com Fri Apr 1 15:50:07 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Fri, 1 Apr 2016 09:50:07 -0400 Subject: [Koha-devel] Testing follow up... Message-ID: Greetings, So, I figured I?d look at the failing tests more. Has anyone worked on solving the Guided Reports failure from http://jenkins.koha-community.org/view/Koha%20master/job/Koha_Master_D7/680/testReport/? If not, check out 16185 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16185) Thanks to those who QA?d bugs 16173, 16174, 16176, and 16178. GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtompset at hotmail.com Fri Apr 1 16:54:59 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Fri, 1 Apr 2016 10:54:59 -0400 Subject: [Koha-devel] Last failing test fixed... Message-ID: Greetings, I continued looking at the failing tests more. Has anyone worked on solving the Circulation_Issuingrule test failure from http://jenkins.koha-community.org/view/Koha%20master/job/Koha_Master_D7/680/testReport/? If not, check out 16186 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16186) 16185 and 16186 should be the last of the problems that need sign off. GPML, Mark Tompsett From M.de.Rooy at rijksmuseum.nl Fri Apr 1 17:51:31 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Fri, 1 Apr 2016 15:51:31 +0000 Subject: [Koha-devel] Last failing test fixed... In-Reply-To: References: Message-ID: <809BE39CD64BFD4EB9036172EBCCFA315B05BFA5@S-MAIL-1B.rijksmuseum.intra> Great ! Saw some passing QA this morning :) ________________________________________ Van: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] namens Mark Tompsett [mtompset at hotmail.com] Verzonden: vrijdag 1 april 2016 16:54 Aan: koha-devel at lists.koha-community.org Onderwerp: [Koha-devel] Last failing test fixed... Greetings, I continued looking at the failing tests more. Has anyone worked on solving the Circulation_Issuingrule test failure from http://jenkins.koha-community.org/view/Koha%20master/job/Koha_Master_D7/680/testReport/? If not, check out 16186 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16186) 16185 and 16186 should be the last of the problems that need sign off. GPML, Mark Tompsett _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From dcook at prosentient.com.au Mon Apr 4 03:34:07 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 4 Apr 2016 11:34:07 +1000 Subject: [Koha-devel] NorwegianPatronDB Message-ID: <057e01d18e12$149cf040$3dd6d0c0$@prosentient.com.au> Hi Blou, The Debian package version should be fine. It?s the CPAN version which is not fine. While this isn?t a problem for Debian users, it is a problem for those of us who don?t use Debian. I?ve tried contacting the CPAN author but they?ve ignored or not received my messages. I see Martin has emailed as well though, so I?ll look at that now? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Philippe Blouin [mailto:philippe.blouin at inlibro.com] Sent: Tuesday, 16 February 2016 12:50 AM To: David Cook ; 'Tomas Cohen Arazi' ; 'Manos PETRIDIS' Cc: koha-devel at lists.koha-community.org Subject: [***SPAM*** Score/Req: 05.5/5.0] Re: [Koha-devel] NorwegianPatronDB Actually, I did fix it using the debian package on debian 7.5. Not sure if the module worked, but the warning disappeared (which then prompted my original email) Philippe Blouin, Responsable du d?veloppement informatique T?l. : (888) 604-2627 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 02/14/2016 05:20 PM, David Cook wrote: FYI, if you?re using the Crypt::GCrypt module from CPAN (ie you?re not using a Debian-based system with libcrypt-gcrypt-perl), Koha is probably going to be unable to load Koha::NorwegianPatronDB. The CPAN module has issues which the Debian team have patched, and the CPAN author appears to have zero interest in patching the CPAN version (or talking about it at all). I wonder what CPAN?s policy is on abandoned modules? My point is that if you?re not using the Debian package, you?re that Crypt::GCrypt dependency appears to always fail now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Saturday, 13 February 2016 2:52 AM To: Manos PETRIDIS Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] NorwegianPatronDB I think we should ship with all the dependencies. We cannot make people's Koha break if they enable some feature. 2016-02-11 17:47 GMT-03:00 Manos PETRIDIS >: Apparently libsoap-lite-perl, libcrypt-gcrypt-perl and libconvert-basen-perl should be/remain mandatory in 3.22, as they are required by a non-optional module, even if the functionality it provides is not used. 2016-02-11 5:06 GMT+02:00 Mark Tompsett >: Greetings, It seems that ?$debug && warn? is a popular style used in C4/Member already. I don?t think a system preference is needed. Just a $debug prepend, perhaps? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15795 Sign it off, kill it, suggest a counter-patch, whatever. I do think this addresses the issue. GPML, Mark Tompsett From: David Cook Sent: Wednesday, February 10, 2016 6:40 PM To: 'Philippe Blouin' Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] NorwegianPatronDB I think you?re right, Philippe. I?ve noticed the same thing. In fact, the ?Unable to load Koha::NorwegianPatronDB? was added after the fact to stop the absence of those libraries causing Koha to die. I don?t necessarily see the point of having that warning there though, as most Koha users probably aren?t going to use the NorwegianPatronDB. Maybe that could have a system preference? so the warns (or the dying) only happens when the system preference is set? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org ] On Behalf Of Philippe Blouin Sent: Thursday, 11 February 2016 8:47 AM To: koha-devel at lists.koha-community.org Subject: [Koha-devel] NorwegianPatronDB Hi! I'm working on 3.22.02 and my logs are FILLED with the following warnings: Members.pm: Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/acqui/booksellers.pl admin-home.pl : Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/admin/preferences.pl I look at the code, and beside wondering why that custom feature is so profoundly imbricated into master Koha, I was wondering what is not working. So I hacked the code to add verbose => 1 on the can_load call, and found that NorwegianPatronDB was not compiling because it was missing the following libraries: apt-get -y install libsoap-lite-perl apt-get -y install libcrypt-gcrypt-perl apt-get -y install libconvert-basen-perl Those modules are specified as NOT mandatory in 3.22. As such, I should not be flooded with Norwegian errors because they are not available, for a module which I and most do not care for. Or am I getting it wrong? Thanks Philippe _____ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Tom?s Cohen Arazi Theke Solutions (http://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Apr 4 03:35:52 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 4 Apr 2016 11:35:52 +1000 Subject: [Koha-devel] NorwegianPatronDB In-Reply-To: References: <56BBAFB6.40805@inlibro.com> <000201d1645c$74768bf0$5d63a3d0$@prosentient.com.au> <017401d16775$e1041230$a30c3690$@prosentient.com.au> Message-ID: <058301d18e12$53535220$f9f9f660$@prosentient.com.au> Hi Martin, Thanks for that info! I have a pause account already, so maybe I should look at tracking down one of those people? I probably won?t have time to work on this for a while, but a long-term fix might be to take over maintenance of that module? I suppose I?m not a bad option as I find encryption interesting and who doesn?t want to maintain a CPAN module? :p David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Renvoize, Martin [mailto:martin.renvoize at ptfs-europe.com] Sent: Monday, 22 February 2016 7:22 PM To: David Cook Subject: Re: [Koha-devel] NorwegianPatronDB One can request to take over maintenence of abandoned cpan modules. You need a pause account obviously to start with, then need to find someone to add your commit bit to the repository for the abandoned module. There are a few such people around in the various perl irc channels. On 14 Feb 2016 10:21 pm, "David Cook" > wrote: FYI, if you?re using the Crypt::GCrypt module from CPAN (ie you?re not using a Debian-based system with libcrypt-gcrypt-perl), Koha is probably going to be unable to load Koha::NorwegianPatronDB. The CPAN module has issues which the Debian team have patched, and the CPAN author appears to have zero interest in patching the CPAN version (or talking about it at all). I wonder what CPAN?s policy is on abandoned modules? My point is that if you?re not using the Debian package, you?re that Crypt::GCrypt dependency appears to always fail now. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org ] On Behalf Of Tomas Cohen Arazi Sent: Saturday, 13 February 2016 2:52 AM To: Manos PETRIDIS > Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] NorwegianPatronDB I think we should ship with all the dependencies. We cannot make people's Koha break if they enable some feature. 2016-02-11 17:47 GMT-03:00 Manos PETRIDIS >: Apparently libsoap-lite-perl, libcrypt-gcrypt-perl and libconvert-basen-perl should be/remain mandatory in 3.22, as they are required by a non-optional module, even if the functionality it provides is not used. 2016-02-11 5:06 GMT+02:00 Mark Tompsett >: Greetings, It seems that ?$debug && warn? is a popular style used in C4/Member already. I don?t think a system preference is needed. Just a $debug prepend, perhaps? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15795 Sign it off, kill it, suggest a counter-patch, whatever. I do think this addresses the issue. GPML, Mark Tompsett From: David Cook Sent: Wednesday, February 10, 2016 6:40 PM To: 'Philippe Blouin' Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] NorwegianPatronDB I think you?re right, Philippe. I?ve noticed the same thing. In fact, the ?Unable to load Koha::NorwegianPatronDB? was added after the fact to stop the absence of those libraries causing Koha to die. I don?t necessarily see the point of having that warning there though, as most Koha users probably aren?t going to use the NorwegianPatronDB. Maybe that could have a system preference? so the warns (or the dying) only happens when the system preference is set? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org ] On Behalf Of Philippe Blouin Sent: Thursday, 11 February 2016 8:47 AM To: koha-devel at lists.koha-community.org Subject: [Koha-devel] NorwegianPatronDB Hi! I'm working on 3.22.02 and my logs are FILLED with the following warnings: Members.pm: Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/acqui/booksellers.pl admin-home.pl : Unable to load Koha::NorwegianPatronDB at /blurred/C4/Members.pm line 46., referer: http://blurred/cgi-bin/koha/admin/preferences.pl I look at the code, and beside wondering why that custom feature is so profoundly imbricated into master Koha, I was wondering what is not working. So I hacked the code to add verbose => 1 on the can_load call, and found that NorwegianPatronDB was not compiling because it was missing the following libraries: apt-get -y install libsoap-lite-perl apt-get -y install libcrypt-gcrypt-perl apt-get -y install libconvert-basen-perl Those modules are specified as NOT mandatory in 3.22. As such, I should not be flooded with Norwegian errors because they are not available, for a module which I and most do not care for. Or am I getting it wrong? Thanks Philippe _____ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Tom?s Cohen Arazi Theke Solutions (http://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer.83 at web.de Tue Apr 5 20:53:28 2016 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Tue, 5 Apr 2016 20:53:28 +0200 Subject: [Koha-devel] Reminder: General IRC Meeting - 6 April 2016 Message-ID: <570409A8.5000008@web.de> Hi all, just a quick reminder about the next General IRC Meeting being in less than a day: https://wiki.koha-community.org/wiki/General_IRC_meeting_6_April_2016 Hope to see you there, Katrin From M.de.Rooy at rijksmuseum.nl Thu Apr 7 14:34:57 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 7 Apr 2016 12:34:57 +0000 Subject: [Koha-devel] Benchmarking (continued) Message-ID: Apache Benchmarking 7-4-2016 Time per request (same server, same Zebra, few records, no Plack, no Cache, no further load) Version opac-search catalogue/search cataloguing/addbiblio 3.14.4 1087 766 743 3.20.10 1792 1263 1211 3.22.5 1204 1184 1854 3.23.00.045 1225 1208 1358 What made addbiblio drop again in current master? Current master does not look bad against 3.20/3.22 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Thu Apr 7 18:02:32 2016 From: oleonard at myacpl.org (Owen Leonard) Date: Thu, 7 Apr 2016 12:02:32 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: References: Message-ID: > I have filed a new bug with a plan for how to move forward on an > upgrade of jQuery in the staff client. > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 This is stuck, so I need to ask for suggestions on how to proceed. Jonathan and I have two different proposals. Mine: - Create a new include file which uses new version of jQuery and jQueryUI. Name that include file according to the version of jQuery it includes ("doc-head-close-jquery-1.12.0.inc"). - Gradually (page by page or in batches) submit patches which add use of the new include file while making any changes to the affected page(s) to update relevant JavaScript to work with the new versions. Advantages to this method: Small manageable patches, nothing breaks without warning. Disadvantages to this method: We introduce duplicate versions of doc-head-close.inc which must be kept in sync. There could end up being many many patches. Jonathan suggests that we update jQuery and jQueryUI without creating a new include file and fixing bugs as we find them. Advantages to this method: One patch, and we don't have to deal with include file renaming. Disadvantages to this method: It is not known what pages will break because of the new versions of jQuery and jQueryUI. Jonathan please correct me if I have mis-characterized your proposal. What does everyone think? Should I bring this up for a vote at the next dev meeting? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From julian.maurice at biblibre.com Thu Apr 7 21:23:55 2016 From: julian.maurice at biblibre.com (Julian Maurice) Date: Thu, 7 Apr 2016 21:23:55 +0200 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: References: Message-ID: <5706B3CB.4080203@biblibre.com> jQuery 1.12 seems to be the last release of the 1.x branch. What's next ? Should we upgrade to 2.x ? 3.x ? I have a preference for the "upgrade all at once / fix as it breaks" method. With the other method I think we will end up with several versions of jQuery and doc-head-close-* Moreover, the upgrade path from 1.7 to 1.12 seems not too hard, according to https://jquery.com/upgrade-guide/1.9 and we can use the jQuery Migrate plugin. Le 07/04/2016 18:02, Owen Leonard a ?crit : >> I have filed a new bug with a plan for how to move forward on an >> upgrade of jQuery in the staff client. >> >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 > > This is stuck, so I need to ask for suggestions on how to proceed. > Jonathan and I have two different proposals. Mine: > > - Create a new include file which uses new version of jQuery and > jQueryUI. Name that include file according to the version of jQuery it > includes ("doc-head-close-jquery-1.12.0.inc"). > > - Gradually (page by page or in batches) submit patches which add use > of the new include file while making any changes to the affected > page(s) to update relevant JavaScript to work with the new versions. > > Advantages to this method: Small manageable patches, nothing breaks > without warning. > Disadvantages to this method: We introduce duplicate versions of > doc-head-close.inc which must be kept in sync. There could end up > being many many patches. > > Jonathan suggests that we update jQuery and jQueryUI without creating > a new include file and fixing bugs as we find them. > > Advantages to this method: One patch, and we don't have to deal with > include file renaming. > Disadvantages to this method: It is not known what pages will break > because of the new versions of jQuery and jQueryUI. > > Jonathan please correct me if I have mis-characterized your proposal. > > What does everyone think? Should I bring this up for a vote at the > next dev meeting? > > -- Owen > -- Julian Maurice BibLibre From info at bywatersolutions.com Thu Apr 7 23:52:54 2016 From: info at bywatersolutions.com (Brendan Gallagher) Date: Thu, 7 Apr 2016 14:52:54 -0700 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) Message-ID: Hello All - I am hoping that we could have a day next week where we are in irc channel #koha and do some testing of Elastic. Ideally target that to be Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The idea is that we'll have Chris (rangi) in channel to look at problems and fix problems that day as we bring them up to him. Nick (kidclamp) from ByWater will also be present as he has done the most testing on our side. Ideally we'll have some ES installs setup - hopefully (we bywater will have 2 identical datasets - 1 running ES and 1 running zebra (but with the ES code installed))... More setups are welcome. We could hopefully get everything set well so that we could get a sign-off that day and get this into QA. Also another thought is that we edit a wiki-page so that we can list things that ES is doing already - what system preferences effect it etc. Thanks, Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a at navalmarinearchive.com Fri Apr 8 02:12:37 2016 From: paul.a at navalmarinearchive.com (Paul A) Date: Thu, 07 Apr 2016 20:12:37 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: <5706B3CB.4080203@biblibre.com> References: Message-ID: <5.2.1.1.2.20160407201143.0712b1a0@pop.navalmarinearchive.com> At 09:23 PM 4/7/2016 +0200, Julian Maurice wrote: >jQuery 1.12 seems to be the last release of the 1.x branch. >What's next ? Should we upgrade to 2.x ? 3.x ? > >I have a preference for the "upgrade all at once / fix as it breaks" >method. With the other method I think we will end up with several >versions of jQuery and doc-head-close-* >Moreover, the upgrade path from 1.7 to 1.12 seems not too hard, >according to https://jquery.com/upgrade-guide/1.9 and we can use the >jQuery Migrate plugin. I used the "migrate plugin" for another project and had no problems. Best -- Paul >Le 07/04/2016 18:02, Owen Leonard a ?crit : > >> I have filed a new bug with a plan for how to move forward on an > >> upgrade of jQuery in the staff client. > >> > >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 > > > > This is stuck, so I need to ask for suggestions on how to proceed. > > Jonathan and I have two different proposals. Mine: > > > > - Create a new include file which uses new version of jQuery and > > jQueryUI. Name that include file according to the version of jQuery it > > includes ("doc-head-close-jquery-1.12.0.inc"). > > > > - Gradually (page by page or in batches) submit patches which add use > > of the new include file while making any changes to the affected > > page(s) to update relevant JavaScript to work with the new versions. > > > > Advantages to this method: Small manageable patches, nothing breaks > > without warning. > > Disadvantages to this method: We introduce duplicate versions of > > doc-head-close.inc which must be kept in sync. There could end up > > being many many patches. > > > > Jonathan suggests that we update jQuery and jQueryUI without creating > > a new include file and fixing bugs as we find them. > > > > Advantages to this method: One patch, and we don't have to deal with > > include file renaming. > > Disadvantages to this method: It is not known what pages will break > > because of the new versions of jQuery and jQueryUI. > > > > Jonathan please correct me if I have mis-characterized your proposal. > > > > What does everyone think? Should I bring this up for a vote at the > > next dev meeting? > > > > -- Owen > > > > >-- >Julian Maurice >BibLibre >_______________________________________________ >Koha-devel mailing list >Koha-devel at 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/ --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. and From laurent.ducos at biblibre.com Fri Apr 8 10:16:45 2016 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Fri, 08 Apr 2016 08:16:45 +0000 Subject: [Koha-devel] just for test Message-ID: <04a0666e698a8d6484855dae836faff9@webmail.biblibre.com> Please ignore this message. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Fri Apr 8 15:40:38 2016 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 8 Apr 2016 09:40:38 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: <5706B3CB.4080203@biblibre.com> References: <5706B3CB.4080203@biblibre.com> Message-ID: On Thu, Apr 7, 2016 at 3:23 PM, Julian Maurice wrote: > jQuery 1.12 seems to be the last release of the 1.x branch. > What's next ? Should we upgrade to 2.x ? 3.x ? We can assume that we will upgrade it to something. I don't think we should complicate this conversation by talking about what the next version will be. If we do this right the next upgrade might be not so complicated. > I have a preference for the "upgrade all at once / fix as it breaks" > method. With the other method I think we will end up with several > versions of jQuery and doc-head-close-* I realize having several versions of doc-head-close-*.inc is complicated because we have to keep them in sync. Is there another reason to avoid it? It's certainly not something the user will care about. > Moreover, the upgrade path from 1.7 to 1.12 seems not too hard, > according to https://jquery.com/upgrade-guide/1.9 and we can use the > jQuery Migrate plugin. I think it would be nice to not add another JS dependency. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From oleonard at myacpl.org Fri Apr 8 16:53:14 2016 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 8 Apr 2016 10:53:14 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: References: <5706B3CB.4080203@biblibre.com> Message-ID: I think all your points are good ones. I do want to clarify one thing: > You are actually talking about adding another dependency. > Koha will depend on jQuery 1.7 and 1.12, and later 2.2 and 3.0. In this case when I talk about a dependency I mean for the end user, not for those of us managing files. I would prefer that there not be another file download slowing down the page. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From paul.a at navalmarinearchive.com Fri Apr 8 17:38:58 2016 From: paul.a at navalmarinearchive.com (Paul A) Date: Fri, 08 Apr 2016 11:38:58 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: References: <5706B3CB.4080203@biblibre.com> Message-ID: <5.2.1.1.2.20160408112408.0efe6e40@pop.navalmarinearchive.com> At 10:53 AM 4/8/2016 -0400, Owen Leonard wrote: >I think all your points are good ones. I do want to clarify one thing: > > > You are actually talking about adding another dependency. > > Koha will depend on jQuery 1.7 and 1.12, and later 2.2 and 3.0. > >In this case when I talk about a dependency I mean for the end user, >not for those of us managing files. I would prefer that there not be >another file download slowing down the page. A very good point. The minified jquery-migrate-1.3.0.min.js is less than 10kb, so the download (here) is only 20ms (nothing cached), and wait time / latency would (most probably) be concurrent with the 13 other .js files (opac search.) I have no feeling one way or the other whether that trades off equitably with the ease of backwards compatibility... Best -- Paul From oleonard at myacpl.org Fri Apr 8 18:08:56 2016 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 8 Apr 2016 12:08:56 -0400 Subject: [Koha-devel] Plan for upgrading jQuery in the staff client In-Reply-To: References: Message-ID: >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 I have attached a new patch which is ready for testing. It upgrades jQuery to 2.2.3, which does not support Internet Explorer 6, 7, or 8. The patch adds the jQuery migrate plugin in order to prevent existing scripts from breaking. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From mtompset at hotmail.com Fri Apr 8 23:31:33 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Fri, 8 Apr 2016 17:31:33 -0400 Subject: [Koha-devel] Failing tests Message-ID: Greetings, I?m not understanding why http://jenkins.koha-community.org/job/Koha_Master_D7/695/#showFailuresLink is so large. Granted, I?m on Debian 8, but only my TestBuilder failed last time I checked. I?ve been drop?ing my DB and creating a basic every sample installed DB for several tests lately. Any thoughts as to the cause? GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bigballofwax.co.nz Fri Apr 8 23:44:19 2016 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Sat, 9 Apr 2016 09:44:19 +1200 Subject: [Koha-devel] Failing tests In-Reply-To: References: Message-ID: On 9 April 2016 at 09:31, Mark Tompsett wrote: > Greetings, > > I?m not understanding why > http://jenkins.koha-community.org/job/Koha_Master_D7/695/#showFailuresLink > is so large. Granted, I?m on Debian 8, but only my TestBuilder failed last > time I checked. I?ve been drop?ing my DB and creating a basic every sample > installed DB for several tests lately. Any thoughts as to the cause? > 10 failing, the easiest way to find it is read the console output http://jenkins.koha-community.org/job/Koha_Master_D7/695/console You can spot stuff like this DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails (`koha_master`.`edifact_messages`, CONSTRAINT `emfk_basketno` FOREIGN KEY (`basketno`) REFERENCES `aqbasket` (`basketno`)) [for Statement "DELETE FROM `aqbasket` WHERE ( `basketno` = ? )" with ParamValues: 0='9'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1593 Chris From Katrin.Fischer.83 at web.de Sun Apr 10 11:58:39 2016 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Sun, 10 Apr 2016 11:58:39 +0200 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: References: Message-ID: <570A23CF.8000906@web.de> Hi Brendan, could you share some link as we have on the agendas for the meetings to define the time window? Have a nice weekend, Katrin Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: > Hello All - > > I am hoping that we could have a day next week where we are in irc > channel #koha and do some testing of Elastic. Ideally target that to be > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The idea is > that we'll have Chris (rangi) in channel to look at problems and fix > problems that day as we bring them up to him. Nick (kidclamp) from > ByWater will also be present as he has done the most testing on our side. > > Ideally we'll have some ES installs setup - hopefully (we bywater will > have 2 identical datasets - 1 running ES and 1 running zebra (but with > the ES code installed))... More setups are welcome. > > We could hopefully get everything set well so that we could get a > sign-off that day and get this into QA. Also another thought is that we > edit a wiki-page so that we can list things that ES is doing already - > what system preferences effect it etc. > > Thanks, > Brendan > > -- > --------------------------------------------------------------------------------------------------------------- > Brendan A. Gallagher > ByWater Solutions > CEO > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From mtompset at hotmail.com Mon Apr 11 05:58:13 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Sun, 10 Apr 2016 23:58:13 -0400 Subject: [Koha-devel] *smirk* Funny but bad, bug 16233 Message-ID: Greetings, My sign off of 16233 with in the title has triggered a strong open tag in effect on the dashboard. GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Apr 11 12:50:50 2016 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 11 Apr 2016 11:50:50 +0100 Subject: [Koha-devel] Final stretch before the next release (3.24 | 16.05) Message-ID: Hi devs, The next Koha release will arrive soon and the feature freeze is coming in 2 weeks! I'd like to mention some works we really should have in this release: 1/ Speed improvements * Koha::Cache Interesting ideas have been implemented recently, but only few have been pushed. We can expect a real gain of performances, our cache system (Koha::Cache) has been improved with bug 11998 and 16044 but is not perfect yet. To make it great, we absolutely need patches from 16221 (Use Storable::dclone() instead of Clone::clone() for L1 cache deep-copying mode), and then 16140 (Only clear L1 cache when needed) and 16166 (Improve L1 cache performance). Bug 16105 (Cache::Memory is loaded even if memcache is used) is also cache-related. * Search There are 3 bug reports blocking bug 15262 (Run Koha Run. Koha search should be fast again) : bug 15263 (XSLT display fetches sysprefs for every result processed) is waiting for QA but 16041 is waiting for signoff. Note that I have opened 16167 to discuss about the possible removal of authorised value images. If you know someone using them, please add a comment on the bug report. To have an overview of what has been done around the performance optimisation during the last months or still need to be done, have a look at the bug 15342 (Performance 3.22 - Omnibus). 2/ Elastic Search A testing day is organised soon (today and tomorrow), stay tuned! 3/ Rewrite/refactoring I have worked a lot on refactoring some parts of Koha the last months. There are 5 left waiting for love: Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] - part 2 Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4 Bug 15407 - Move the patron categories related code to Koha::Patron::Categories - part 2 Bug 15498 - Replace ExportWithCsvProfile with ExportCircHistory Bug 15451 - Move the CSV related code to Koha::CsvProfile[s] I really would like to see them included into the next release. For the first 3, it's the continuation of parts already pushed, it would make sense to have them too. 4/ jQuery upgrade Owen suggested to upgrade our jQuery on bug 15883, it is a nice to have for the next release. 5/ Bug fixes * CGI->multi_param You have certainly notice the "CGI::param called in list context" warnings in the logs. We are going to get rid of them with bug 16154 - Replace CGI->param with CGI->multi_param in list context * Regression on currency This will become a blocker if not signed off soon. See bug 16227 - The currencies of vendor and order do not display correctly * The OPAC is not accessible if JS is disabled (blocker)! See bug 16210 (Bug 15111 breaks the OPAC if JavaScript is disabled) for a fix 6/ Versioning change It seems that we voted [1] for changing the versioning to be date based. Does someone work on that? There are adjustments to do to the codebase to make it work. But we also need to decide how to number the 2 annual major versions and the minors. Feel free to add more if you think about something. Note: please sort by severity when you are searching for a bug to sign off [2], blocker, critical and major have to be signoff before cosmetic bugs ;) Cheers, Jonathan PS: Note that there are 5 points before the 6th! [1] http://meetings.koha-community.org/2016/genereal_irc_meeting_9_march_2016.2016-03-09-20.00.log.html) [2] https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Signoff&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&list_id=160792&order=bug_severity%2Cassigned_to%2Cbug_id%20DESC&query_based_on=Needs%20Signoff&query_format=advanced From barton at bywatersolutions.com Mon Apr 11 14:45:49 2016 From: barton at bywatersolutions.com (Barton Chittenden) Date: Mon, 11 Apr 2016 08:45:49 -0400 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: <570A23CF.8000906@web.de> References: <570A23CF.8000906@web.de> Message-ID: Leading in to the testing -- is there any documentation on * Adding indexes for ES? * Support for unicode/i18n in ES? * Understanding how ES handles relevance (and how this is configured in Koha) On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer wrote: > Hi Brendan, > > could you share some link as we have on the agendas for the meetings to > define the time window? > > Have a nice weekend, > > Katrin > > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: > > Hello All - > > > > I am hoping that we could have a day next week where we are in irc > > channel #koha and do some testing of Elastic. Ideally target that to be > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The idea is > > that we'll have Chris (rangi) in channel to look at problems and fix > > problems that day as we bring them up to him. Nick (kidclamp) from > > ByWater will also be present as he has done the most testing on our side. > > > > Ideally we'll have some ES installs setup - hopefully (we bywater will > > have 2 identical datasets - 1 running ES and 1 running zebra (but with > > the ES code installed))... More setups are welcome. > > > > We could hopefully get everything set well so that we could get a > > sign-off that day and get this into QA. Also another thought is that we > > edit a wiki-page so that we can list things that ES is doing already - > > what system preferences effect it etc. > > > > Thanks, > > Brendan > > > > -- > > > --------------------------------------------------------------------------------------------------------------- > > Brendan A. Gallagher > > ByWater Solutions > > CEO > > > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Mon Apr 11 18:29:57 2016 From: info at bywatersolutions.com (Brendan Gallagher) Date: Mon, 11 Apr 2016 09:29:57 -0700 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: <570A23CF.8000906@web.de> References: <570A23CF.8000906@web.de> Message-ID: Hi - Well I didn't want to put times in there exactly - I was sort of hoping for a day of work. So that being Wednesday for the New Zealand types and Tuesday for the rest of us. Nick (kidclamp) will have two identical servers up (one ES and one Zebra) by the end of the day (today - Monday for him). So anyone and everyone will be able to test. Ideally Chris will be ready for patches or answering questions on his Wednesday morning (9am New Zealand time). HTH Cheers, Brendan On Sun, Apr 10, 2016 at 2:58 AM, Katrin Fischer wrote: > Hi Brendan, > > could you share some link as we have on the agendas for the meetings to > define the time window? > > Have a nice weekend, > > Katrin > > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: > > Hello All - > > > > I am hoping that we could have a day next week where we are in irc > > channel #koha and do some testing of Elastic. Ideally target that to be > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The idea is > > that we'll have Chris (rangi) in channel to look at problems and fix > > problems that day as we bring them up to him. Nick (kidclamp) from > > ByWater will also be present as he has done the most testing on our side. > > > > Ideally we'll have some ES installs setup - hopefully (we bywater will > > have 2 identical datasets - 1 running ES and 1 running zebra (but with > > the ES code installed))... More setups are welcome. > > > > We could hopefully get everything set well so that we could get a > > sign-off that day and get this into QA. Also another thought is that we > > edit a wiki-page so that we can list things that ES is doing already - > > what system preferences effect it etc. > > > > Thanks, > > Brendan > > > > -- > > > --------------------------------------------------------------------------------------------------------------- > > Brendan A. Gallagher > > ByWater Solutions > > CEO > > > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbraum at nekls.org Mon Apr 11 18:34:24 2016 From: hbraum at nekls.org (Heather Braum (NEKLS)) Date: Mon, 11 Apr 2016 10:34:24 -0600 Subject: [Koha-devel] NEKLS Job opportunity for NExpress Coordinator and ILS Systems Manager Message-ID: Last call for applicants. NEKLS will begin reviewing applications after April 15. The Northeast Kansas Library System (NEKLS) in Lawrence, KS , has an opening and we?re looking for a diplomatic applicant with lots of energy, enthusiasm, and excellent custom service skills to come work with us! *NExpress Coordinator and ILS Systems Manager*: Opportunity for a creative librarian who will enjoy the challenge of managing a large regional shared consortia catalog, with 42 public libraries and 1 school district (public catalog ). The system runs on the Koha ILS , an open source ILS used all over the world. Responsibilities include: - Providing overall management, support, and coordination of the NExpress ILS and consortia, including balancing needs of consortia with local library needs - Coordinating operations of NExpress team - Maintaining data quality of NExpress records and database - Coordinating with participating libraries and ILS support vendor regarding system features and bugs, migrations, upgrades, and software developments - Providing NExpress training to participating libraries, including planning & leading quarterly NExpress users group meetings - Participating in the international Koha community Qualified candidates will meet the following: - MLS degree preferred and 3 or more years of prior library experience is required. - Experience with integrated library automation system software is required. - Knowledge of cataloging best practices, database management (MySQL), web languages (HTML, CSS, JQuery), web CMS platforms (WordPress and LibGuides) is highly preferred. See the full job description, including qualification list , for more information ( http://nekls.org/wp-content/uploads/2016/03/NExpress-Coordinator-Job-Description.pdf ). Excellent salary ($50,000-$53,000) and benefits package, including complete health, dental, and vision coverage (single and family), short-term and long-term disability insurance, and retirement options. Position is open until filled. Evaluation of applications will begin on April 15, 2016 and will continue until position is filled. Estimated start date is on or around July 1, 2016. For questions, please contact Laura DeBaun, NEKLS Director, at ldebaun at nekls.org. Apply with cover letter, resume and references list by emailing Carolyn Little, Courier Coordinator, at clittle at nekls.org. Please use the subject line NExpress Coordinator Job Application. NEKLS is an equal opportunity employer. Heather Braum NExpress Coordinator Resource Sharing Librarian Northeast Kansas Library System hbraum at nekls.org "The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future* -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Mon Apr 11 22:09:46 2016 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Tue, 12 Apr 2016 08:09:46 +1200 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: References: <570A23CF.8000906@web.de> Message-ID: <20160411200946.GP15241@rorohiko.wgtn.cat-it.co.nz> * Barton Chittenden (barton at bywatersolutions.com) wrote: > Leading in to the testing -- is there any documentation on > > * Adding indexes for ES? See bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 > * Support for unicode/i18n in ES? You can read the ES documentation for that > * Understanding how ES handles relevance (and how this is configured in Koha) > As above. Basically I don't want people to spend time focusing on these things tomorrow. We want to be sure that all the scaffolding code and the basic ES support does not break current functionality. Once it is in master there are already other bugs to enhance and extend it. But it gets harder and harder to get in the more we try to add to it first. Chris > On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer > wrote: > > Hi Brendan, > > could you share some link as we have on the agendas for the meetings to > define the time window? > > Have a nice weekend, > > Katrin > > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: > > Hello All - > > > > I am hoping that we could have a day next week where we are in irc > > channel #koha and do some testing of Elastic.? Ideally target that to be > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me.? The idea is > > that we'll have Chris (rangi) in channel to look at problems and fix > > problems that day as we bring them up to him.? Nick (kidclamp) from > > ByWater will also be present as he has done the most testing on our side. > > > > Ideally we'll have some ES installs setup - hopefully (we bywater will > > have 2 identical datasets - 1 running ES and 1 running zebra (but with > > the ES code installed))...? More setups are welcome. > > > > We could hopefully get everything set well so that we could get a > > sign-off that day and get this into QA.? Also another thought is that we > > edit a wiki-page so that we can list things that ES is doing already - > > what system preferences effect it etc. > > > > Thanks, > > Brendan > > > > -- > > > --------------------------------------------------------------------------------------------------------------- > > Brendan A. Gallagher > > ByWater Solutions > > CEO > > > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From nick at bywatersolutions.com Tue Apr 12 04:08:19 2016 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 12 Apr 2016 02:08:19 +0000 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: <20160411200946.GP15241@rorohiko.wgtn.cat-it.co.nz> References: <570A23CF.8000906@web.de> <20160411200946.GP15241@rorohiko.wgtn.cat-it.co.nz> Message-ID: Hello All, I hit some snags in getting a running elastic server up, but I do have a working zebra site up. Turning on elastic here will not work. One main goal of the testing is to confirm that the patches break nothing if Zebra is selected as the search engine with the ES code present, so testing on this branch and ensuring that everything works as it should is an important part of the work. Staff interface: http://staff-elastic.bwsdev.bywatersolutions.com/ OPAC interface: http://elastic.bwsdev.bywatersolutions.com/ user/pass: zebra/zebra I will keep working on getting a working elastic installation going and will update asap. -Nick (kidclamp) On Mon, Apr 11, 2016 at 4:10 PM Chris Cormack wrote: > * Barton Chittenden (barton at bywatersolutions.com) wrote: > > Leading in to the testing -- is there any documentation on > > > > * Adding indexes for ES? > > See bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 > > > * Support for unicode/i18n in ES? > > You can read the ES documentation for that > > > * Understanding how ES handles relevance (and how this is configured in > Koha) > > > As above. > > Basically I don't want people to spend time focusing on these things > tomorrow. > We want to be sure that all the scaffolding code and the basic ES support > does > not break current functionality. > > Once it is in master there are already other bugs to enhance and extend > it. But > it gets harder and harder to get in the more we try to add to it first. > > Chris > > > > On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer < > Katrin.Fischer.83 at web.de> > > wrote: > > > > Hi Brendan, > > > > could you share some link as we have on the agendas for the meetings > to > > define the time window? > > > > Have a nice weekend, > > > > Katrin > > > > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: > > > Hello All - > > > > > > I am hoping that we could have a day next week where we are in irc > > > channel #koha and do some testing of Elastic. Ideally target that > to be > > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The > idea is > > > that we'll have Chris (rangi) in channel to look at problems and > fix > > > problems that day as we bring them up to him. Nick (kidclamp) from > > > ByWater will also be present as he has done the most testing on > our side. > > > > > > Ideally we'll have some ES installs setup - hopefully (we bywater > will > > > have 2 identical datasets - 1 running ES and 1 running zebra (but > with > > > the ES code installed))... More setups are welcome. > > > > > > We could hopefully get everything set well so that we could get a > > > sign-off that day and get this into QA. Also another thought is > that we > > > edit a wiki-page so that we can list things that ES is doing > already - > > > what system preferences effect it etc. > > > > > > Thanks, > > > Brendan > > > > > > -- > > > > > > --------------------------------------------------------------------------------------------------------------- > > > Brendan A. Gallagher > > > ByWater Solutions > > > CEO > > > > > > > > > > > > > > > _______________________________________________ > > > Koha-devel mailing list > > > Koha-devel at 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/ > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Tue Apr 12 08:10:16 2016 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 12 Apr 2016 08:10:16 +0200 Subject: [Koha-devel] Final stretch before the next release (3.24 | 16.05) In-Reply-To: References: Message-ID: <570C9148.4090604@biblibre.com> Le 11/04/2016 12:50, Jonathan Druart a ?crit : > 6/ Versioning change > It seems that we voted [1] for changing the versioning to be date > based. Does someone work on that? There are adjustments to do to the > codebase to make it work. But we also need to decide how to number the > 2 annual major versions and the minors. Is there really something to change in the code for this to work ? We will jump from 3.24 to 16.05, but it's still the same format (\d+\.\d+) For minor versions I was (naively) thinking we will continue to use the same scheme (that is 16.05.YY.ZZZ). Am I missing something ? > > Feel free to add more if you think about something. > I think those 6 points are really important, but I would like to add a 7th point : the REST API hasn't moved since its introduction in 3.22. Bugs 15126 and 13903 are signed off, and it would be great to have them pushed in 16.05, just to see some movement here :) -- Julian Maurice BibLibre From nick at bywatersolutions.com Tue Apr 12 18:07:37 2016 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 12 Apr 2016 16:07:37 +0000 Subject: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday) In-Reply-To: References: <570A23CF.8000906@web.de> <20160411200946.GP15241@rorohiko.wgtn.cat-it.co.nz> Message-ID: Tomas has updated kohadevbox/ansible and you should now get a running elasticsearch instance by adding KOHA_ELASTICSEARCH=1 to your vagrant up as below KOHA_ELASTICSEARCH=1 vagrant up The wiki page for getting started has also been updated for those not using kohadevbox: https://wiki.koha-community.org/wiki/Elasticsearch#Configuration I will be in channel and Chris will be in later -Nick On Mon, Apr 11, 2016 at 10:08 PM Nick Clemens wrote: > Hello All, > > I hit some snags in getting a running elastic server up, but I do have a > working zebra site up. Turning on elastic here will not work. > > One main goal of the testing is to confirm that the patches break nothing > if Zebra is selected as the search engine with the ES code present, so > testing on this branch and ensuring that everything works as it should is > an important part of the work. > > > Staff interface: > http://staff-elastic.bwsdev.bywatersolutions.com/ > > OPAC interface: > http://elastic.bwsdev.bywatersolutions.com/ > > user/pass: zebra/zebra > > > I will keep working on getting a working elastic installation going and > will update asap. > > -Nick (kidclamp) > > > On Mon, Apr 11, 2016 at 4:10 PM Chris Cormack > wrote: > >> * Barton Chittenden (barton at bywatersolutions.com) wrote: >> > Leading in to the testing -- is there any documentation on >> > >> > * Adding indexes for ES? >> >> See bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 >> >> > * Support for unicode/i18n in ES? >> >> You can read the ES documentation for that >> >> > * Understanding how ES handles relevance (and how this is configured in >> Koha) >> > >> As above. >> >> Basically I don't want people to spend time focusing on these things >> tomorrow. >> We want to be sure that all the scaffolding code and the basic ES support >> does >> not break current functionality. >> >> Once it is in master there are already other bugs to enhance and extend >> it. But >> it gets harder and harder to get in the more we try to add to it first. >> >> Chris >> >> >> > On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer < >> Katrin.Fischer.83 at web.de> >> > wrote: >> > >> > Hi Brendan, >> > >> > could you share some link as we have on the agendas for the >> meetings to >> > define the time window? >> > >> > Have a nice weekend, >> > >> > Katrin >> > >> > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher: >> > > Hello All - >> > > >> > > I am hoping that we could have a day next week where we are in irc >> > > channel #koha and do some testing of Elastic. Ideally target >> that to be >> > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The >> idea is >> > > that we'll have Chris (rangi) in channel to look at problems and >> fix >> > > problems that day as we bring them up to him. Nick (kidclamp) >> from >> > > ByWater will also be present as he has done the most testing on >> our side. >> > > >> > > Ideally we'll have some ES installs setup - hopefully (we bywater >> will >> > > have 2 identical datasets - 1 running ES and 1 running zebra (but >> with >> > > the ES code installed))... More setups are welcome. >> > > >> > > We could hopefully get everything set well so that we could get a >> > > sign-off that day and get this into QA. Also another thought is >> that we >> > > edit a wiki-page so that we can list things that ES is doing >> already - >> > > what system preferences effect it etc. >> > > >> > > Thanks, >> > > Brendan >> > > >> > > -- >> > > >> > >> --------------------------------------------------------------------------------------------------------------- >> > > Brendan A. Gallagher >> > > ByWater Solutions >> > > CEO >> > > >> > > >> > > >> > > >> > > _______________________________________________ >> > > Koha-devel mailing list >> > > Koha-devel at 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/ >> > > >> > >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel at 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/ >> > >> > >> >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel at 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/ >> >> >> -- >> Chris Cormack >> Catalyst IT Ltd. >> +64 4 803 2238 >> PO Box 11-053, Manners St, Wellington 6142, New Zealand >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer.83 at web.de Tue Apr 12 22:16:05 2016 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Tue, 12 Apr 2016 22:16:05 +0200 Subject: [Koha-devel] Reminder: Development IRC meeting 13 April 2016 Message-ID: <570D5785.1020700@web.de> Hi all, just the usual quick reminder that there is a developer meeting scheduled in a bit less than 24 hours: https://wiki.koha-community.org/wiki/Development_IRC_meeting_13_April_2016 Hope to see you there, Katrin From info at bywatersolutions.com Wed Apr 13 01:11:31 2016 From: info at bywatersolutions.com (Brendan Gallagher) Date: Tue, 12 Apr 2016 16:11:31 -0700 Subject: [Koha-devel] Final stretch before the next release (3.24 | 16.05) In-Reply-To: References: Message-ID: On Mon, Apr 11, 2016 at 3:50 AM, Jonathan Druart < jonathan.druart at bugs.koha-community.org> wrote: > Hi devs, > > The next Koha release will arrive soon and the feature freeze is > coming in 2 weeks! > I'd like to mention some works we really should have in this release: > > 1/ Speed improvements > * Koha::Cache > Interesting ideas have been implemented recently, but only few have been > pushed. > We can expect a real gain of performances, our cache system > (Koha::Cache) has been improved with bug 11998 and 16044 but is not > perfect yet. To make it great, we absolutely need patches from 16221 > (Use Storable::dclone() instead of Clone::clone() for L1 cache > deep-copying mode), and then 16140 (Only clear L1 cache when needed) > and 16166 (Improve L1 cache performance). > Bug 16105 (Cache::Memory is loaded even if memcache is used) is also > cache-related. > > * Search > There are 3 bug reports blocking bug 15262 (Run Koha Run. Koha search > should be fast again) : bug 15263 (XSLT display fetches sysprefs for > every result processed) is waiting for QA but 16041 is waiting for > signoff. Note that I have opened 16167 to discuss about the possible > removal of authorised value images. If you know someone using them, > please add a comment on the bug report. > > To have an overview of what has been done around the performance > optimisation during the last months or still need to be done, have a > look at the bug 15342 (Performance 3.22 - Omnibus). > Very important stuff here. This should be priority for everyone. > > 2/ Elastic Search > A testing day is organised soon (today and tomorrow), stay tuned! > > 3/ Rewrite/refactoring > I have worked a lot on refactoring some parts of Koha the last months. > There are 5 left waiting for love: > Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] - > part 2 > Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4 > Bug 15407 - Move the patron categories related code to > Koha::Patron::Categories - part 2 > Bug 15498 - Replace ExportWithCsvProfile with ExportCircHistory > Bug 15451 - Move the CSV related code to Koha::CsvProfile[s] > > I really would like to see them included into the next release. > For the first 3, it's the continuation of parts already pushed, it > would make sense to have them too. > > 4/ jQuery upgrade > Owen suggested to upgrade our jQuery on bug 15883, it is a nice to > have for the next release. > > 5/ Bug fixes > * CGI->multi_param > You have certainly notice the "CGI::param called in list context" > warnings in the logs. We are going to get rid of them with bug 16154 - > Replace CGI->param with CGI->multi_param in list context > * Regression on currency > This will become a blocker if not signed off soon. See bug 16227 - The > currencies of vendor and order do not display correctly > * The OPAC is not accessible if JS is disabled (blocker)! > See bug 16210 (Bug 15111 breaks the OPAC if JavaScript is disabled) for a > fix > > 6/ Versioning change > It seems that we voted [1] for changing the versioning to be date > based. Does someone work on that? There are adjustments to do to the > codebase to make it work. But we also need to decide how to number the > 2 annual major versions and the minors. > I was thinking 2 majors would be 16.05 and 16.11 minors would be 16.05.01 (for first RMaint of 16.05) and increase incrementally. Dev (unstable) would be 16.06 and then 17.00 I am and was willing to work on the patches for the version changes but was waiting until after the Freeze to do that. If you have any comments for me Jonathan that's great - I'll always take them. > > Feel free to add more if you think about something. > > Note: please sort by severity when you are searching for a bug to sign > off [2], blocker, critical and major have to be signoff before > cosmetic bugs ;) > > Cheers, > Jonathan > > PS: Note that there are 5 points before the 6th! > > [1] > http://meetings.koha-community.org/2016/genereal_irc_meeting_9_march_2016.2016-03-09-20.00.log.html > ) > [2] > https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Signoff&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&list_id=160792&order=bug_severity%2Cassigned_to%2Cbug_id%20DESC&query_based_on=Needs%20Signoff&query_format=advanced > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From long_sam.tw at yahoo.com.tw Wed Apr 13 02:24:57 2016 From: long_sam.tw at yahoo.com.tw (long_sam.tw) Date: Wed, 13 Apr 2016 00:24:57 +0000 (UTC) Subject: [Koha-devel] koha ldap for AD (ref) References: <1077772595.326914.1460507097771.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <1077772595.326914.1460507097771.JavaMail.yahoo@mail.yahoo.com> Dear all,? koha ldap for AD (config & test) ref?https://koha.wikispaces.com/koha_ldap_en -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtompset at hotmail.com Thu Apr 14 00:45:26 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Wed, 13 Apr 2016 18:45:26 -0400 Subject: [Koha-devel] Biblio level visibility Message-ID: Greetings, Thanks to those who helped get bug 15870 into master. What I was hoping was to get biblio level filtering for MARC working better in the OPAC, particularly bug 11592. This will let me turn my attention back to OpacHiddenItems as a filter, so that the expected visibility of things will be correct across the board, and make overrides (bug 10589) easier. GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-smile[1].png Type: image/png Size: 1046 bytes Desc: not available URL: From kohanews at gmail.com Thu Apr 14 03:29:59 2016 From: kohanews at gmail.com (kohanews) Date: Wed, 13 Apr 2016 18:29:59 -0700 Subject: [Koha-devel] Call for News: April 2016 Newsletter Message-ID: <570EF297.9010909@gmail.com> Fellow Koha users ~ I'm collecting news for the April newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: * - Please include dates for past events. If I can't find dates I may not add it. * - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon * - For past events -- **** one month back is the cut-off ***. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. 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 Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Fri Apr 15 18:48:55 2016 From: barton at bywatersolutions.com (Barton Chittenden) Date: Fri, 15 Apr 2016 12:48:55 -0400 Subject: [Koha-devel] Improving Zebra logging In-Reply-To: <00a801d12182$8684f2e0$938ed8a0$@prosentient.com.au> References: <003901d120e6$b993c090$2cbb41b0$@prosentient.com.au> <00a801d12182$8684f2e0$938ed8a0$@prosentient.com.au> Message-ID: Just because I remembered this conversation, and ended up looking this up, Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15714 enhancement, P5 - low, ---, m.de.rooy, Pushed to Master , Remove zebra.log from debian scripts and add optional log levels This should be released in 16.05, and adds the ability to set the zebra log level via the directive in $KOHA_CONF. Thanks to all involved. --Barton On Tue, Nov 17, 2015 at 4:54 PM, David Cook wrote: > Agreed. I think that would make a lot of sense. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St, Ultimo, NSW 2007 > > > > *From:* Tomas Cohen Arazi [mailto:tomascohen at gmail.com] > *Sent:* Wednesday, 18 November 2015 12:11 AM > *To:* David Cook > *Cc:* Koha-devel > *Subject:* Re: [Koha-devel] Improving Zebra logging > > > > The koha-*-zebra scripts should be merged into koha-zebra with several > option switches, just as koha-indexer works... Same for SIP-related scripts. > > > > 2015-11-17 0:19 GMT-03:00 David Cook : > > Hi all: > > > > As if you weren?t all sick of me going on and on about Zebra. > > > > So you may or may not know that the Zebra logs are fairly useless in a > package install of Koha. > > > > At Prosentient, we don?t use package installs much, so I haven?t noticed > this until now, but here?s a tip: > > > > If you want to see what requests are being made to Zebra, you can do the > following: > > > > 1) vi /usr/sbin/koha-start-zebra > > 2) Under start_zebra_instance, you can change ?-v none,fatal,warn? > to ?-v none,fatal,warn,request? (note that ?request? is an undocumented log > level but it should work? alternately remove none and requests should > appear in the log) > > 3) sudo koha-zebra-stop > > 4) sudo koha-zebra-start > > 5) profit (or at least see the PQF which is sent to the server and > whether you?re getting errors or OK query responses) > > > > This is the kind of additional output you should expect to see: > > 14:15:00-17/11 zebrasrv(2) [request] Auth idPass kohauser - > > 14:15:00-17/11 zebrasrv(2) [request] Init OK - ID:81 Name:ZOOM-C/YAZ > Version:4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031 > > 14:15:00-17/11 zebrasrv(2) [request] Search biblios OK 0 1 1+0 RPN > @attrset Bib-1 @attr 1=1016 @attr 4=6 @attr 5=1 test > > > > Anyway, I wouldn?t **actually** recommend changing > /usr/sbin/koha-start-zebra since that?s part of the koha-common package? > but maybe someone would be interested in making change to the Zebra > commands to allow for different logging levels. > > > > Other things to note: > > > > koha-zebra-restart isn?t the same thing as koha-zebra-stop && > koha-zebra-start. If you restart Zebra after changing the flags for daemon > or zebrasrv, the changes won?t be brought across?it?s necessary to stop and > start it again? even though the process is actually restarted? it seems to > be restarted using the original configuration used when launching daemon in > the first place. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St, Ultimo, NSW 2007 > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > > > > > -- > > Tom?s Cohen Arazi > > Theke Solutions (http://theke.io) > ? +54 9351 3513384 > GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Sun Apr 17 18:23:27 2016 From: info at bywatersolutions.com (Brendan Gallagher) Date: Sun, 17 Apr 2016 09:23:27 -0700 Subject: [Koha-devel] Update on RM Message-ID: Hi All - I had a really busy week last week and was not able to dedicate time towards testing and pushing code. I have a busy Monday morning, but then after that I will get that PQA low again. We have about 2 weeks until the freeze, just a reminder, not a rallying call yet. Hoping the final month after the freeze we can get Master wicked stable. :). Cheers, Brendan -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Apr 18 06:29:55 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 14:29:55 +1000 Subject: [Koha-devel] How is relevance weighted in zebra search? In-Reply-To: <56F01085.5050401@inlibro.com> References: <56F01085.5050401@inlibro.com> Message-ID: <011401d1992a$f54dfc60$dfe9f520$@prosentient.com.au> I think that Bywater post from 2012 is actually quite misleading and downright wrong in some cases but Ian?s comments in the listserv are good. Koha?s C4::Search code needs to die in a fire Fran?ois is right about QueryAutoTruncate. If I recall correctly, it actually silently turns off relevance searching. 1) The most important thing to remember is that C4::Search::_build_weighted_query() adds a bunch of stuff to the mix. The query the user makes is very very different from the one that is sent to Zebra. Add some debugging logging to Koha or monitor your Zebra server to see what queries are ?actually? being sent to Zebra. That ByWater post says that some MARC tags are more relevant than others. That?s not really true per se. However, Koha adds several title indexes to the query and gives them high ranking weights, I believe. So it?s not that some MARC fields are ranked higher than others in general. Rather, Search.pm just loads up the query to favour title indexes (which are not the same thing as MARC tags anyway ) 2) I?d review http://www.indexdata.com/zebra/doc/administration-ranking.html. The query is broken down into atomic parts, those atomic queries are run, hit lists are created for these atomic parts, the documents in the hit lists are scored, and then all the atomic queries are merged together to create a master hit list and the total document score is calculated. As far I know, it just uses term frequency, and not proximity (unless you tell it to also use proximity). What query did you use in yaz-client? I suspect that you didn?t include ranking? If you did, it probably wasn?t the same query used by Koha, unless the query weighting was being turned off (say by QueryAutoTruncate). When in doubt, figure out what Koha is sending to Zebra. That should almost always indicate what?s actually going on. Check the search results to see if they?re actually in relevance order. Just look at the biblionumbers for the first 5 results. If they?re in perfect ascending/descending order, chances are that your relevance is silently turned off. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Francois Charbonnier Sent: Tuesday, 22 March 2016 2:17 AM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] How is relevance weighted in zebra search? Hi, I'll suggest you to read this and that : http://bywatersolutions.com/2012/11/27/a-little-bit-about-relevance-in-koha/ https://lists.katipo.co.nz/public/koha/2012-February/031909.html Both helped me to understand a bit more how relevance works in Koha. And, try to desactivate the QueryAutoTruncate system preferences. It doesn't mix well with the relevance ranking. Fran?ois Charbonnier, Bibl. prof. / Chef de produits T?l. : (888) 604-2627 francois.charbonnier at inLibro.com inLibro | pour esprit libre | www.inLibro.com Le 2016-03-21 09:06, Barton Chittenden a ?crit : Hi, We just upgraded a library from Koha 3.0 to 3.22. After the upgrade, the library complained that the title "Golden Age" was at the bottom of their OPAC search results. I checked the obvious first: OPACdefaultSortField had been set to 'relevance' with OPACdefaultSortOrder set to 'ascending', which would definitely be backwards (least relevant first)... I changed to to 'ascending', and got exactly the same results. Restarting memcache didn't help. When I searched using yaz-client, I found that the results that were coming first in the list had the phrase "golden age" in 520$a. Here's the version of zebra: $ idzebra-config --version 2.0.59 At this point, I have two major questions: 1) Where do I check which fields are ranked more highly in a relevance search? (I would think that title should be ranked higher than 520$a -- summary). 2) Why didn't the sort order change when I changed OPACdefaultSortOrder from ascending to descending? _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Apr 18 06:35:46 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 14:35:46 +1000 Subject: [Koha-devel] Who all are purposing Koha as an Union Catalog? In-Reply-To: References: Message-ID: <011901d1992b$c663d590$532b80b0$@prosentient.com.au> We put together a proof of concept using my original OAI-PMH harvester, but I wasn't a huge fan of it, as it was very simple. It didn't deduplicate biblios, and it didn't include items (although we had the OAI-PMH server inject a URL pointing back to the original Koha instance with the number of items attached to the biblio). I don't think anyone ever used it. There is talk from some people about using my new OAI-PMH harvester for making Koha a union catalogue... but I think that will be difficult and require more development in Koha. The OAI-PMH harvester works great for adding/updating/deleting bibliographic records, but adding/updating/deleting items becomes very difficult depending on what's going on in your union catalogue... although I guess we could do what EBSCO and VuFind do and just provide live item info via an API... that's actually probably the way to do it. Otherwise, your union catalogue will be stale... and it's difficult to convey item state via item metadata... at least without changing how we use that item metadata currently I think. Anyway, just my 2 cents. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Indranil Das Gupta > Sent: Monday, 21 March 2016 2:46 PM > To: koha-devel at lists.koha-community.org > Subject: [Koha-devel] Who all are purposing Koha as an Union Catalog? > > Hi all, > > At a recent conference here, there was discussions about utilizing Koha as an > Union catalog. > > I would like to know how many / if anyone here is using Koha in that manner. > And what is the experience so far, the extent of custom development etc > > 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 > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From dcook at prosentient.com.au Mon Apr 18 07:10:46 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 15:10:46 +1000 Subject: [Koha-devel] Interface consistency: The buttons edition In-Reply-To: References: Message-ID: <012401d19930$aa97cc90$ffc765b0$@prosentient.com.au> I'm loving these emails! I think my web design skills leave a lot to be desired, so I'm happy to conform to any front-end guidelines you give me! I'm going to put the interface patterns page on my bookmarks bar. I've been thinking a lot about this lately as I try to make a UI for managing incoming OAI-PMH records. What I'd love is a convention for paging! The staged marc management seems to use one set of code, I think search results use one set, sometimes we use the DataTables with an AJAX source. I'd love to know the best way to do this. There is some DBIC code for paging, but I haven't quite looked into it yet. Rather than re-inventing the wheel, I rather just use the project standard. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Owen Leonard > Sent: Saturday, 12 March 2016 3:09 AM > To: koha-devel at lists.koha-community.org > Subject: [Koha-devel] Interface consistency: The buttons edition > > Sorry for being the guy who thinks way too much about buttons. > > I have added a section to the interface guidelines in the wiki all about > buttons: > > https://wiki.koha-community.org/wiki/Interface_patterns#Buttons > > I think it's an accurate description of how we're doing things now. > Please let me know if you have comments, disagree, or have a proposal for > updating any of the de-facto standards we are working with. > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From dcook at prosentient.com.au Mon Apr 18 07:37:20 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 15:37:20 +1000 Subject: [Koha-devel] Kohacon16 Program Message-ID: <012c01d19934$602ebd40$208c37c0$@prosentient.com.au> Looks like an interesting Kohacon program at http://kohacon2016.lib.auth.gr/?page_id=2417! I'd heard that EBSCO was developing their own LSP (http://kohacon2016.lib.auth.gr/?events=a-new-open-source-library-platform-b uilding-and-integrating-microservices), but I hadn't heard many details. I'm surprised to see a "BIBFRAME and Koha" talk by Joy and Jesse from Bywater, but very interested to hear about it. Alas, I won't be going to Kohacon this year, as my spawn is a bit too small to leave at the moment. If Bywater are offering a sneak preview though, I'd be delighted to hear it : ). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Apr 18 07:46:35 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 15:46:35 +1000 Subject: [Koha-devel] [Koha] HTTP::OAI Message-ID: <013101d19935$ab586b30$02094190$@prosentient.com.au> If you're not on a Debian-based system, I'd try the following: cpan install App::Minus cpanm HTTP::OAI at 3.28 Version 4.03 of HTTP::OAI is very broken, if I recall correctly. More info at https://rt.cpan.org/Public/Bug/Display.html?id=102010 David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > Date: Tue, 22 Mar 2016 10:36:14 +0000 > From: Jonathan Druart > To: regina kivuyo > Cc: "koha at lists.katipo.co.nz" > Subject: Re: [Koha] HTTP::OAI > Message-ID: > mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Try install it using the debian package: `sudo apt-get install libhttp-oai-perl` > > 2016-03-22 10:15 GMT+00:00 regina kivuyo : > > sorry for disturbance i tried to install HTTP::OAI > > root at library-HP-Pro-3400-Series-MT:/home/koha-3.10.02# cpan force > install > > HTTP::OAI > > Reading '/root/.cpan/Metadata' > > Database was generated on Mon, 21 Mar 2016 16:17:02 GMT > > Warning: Cannot install force, don't know what it is. > > Try the command > > > > i /force/ > > > > to find objects with matching identifiers. > > install is up to date (0.01). > > Running install for module 'HTTP::OAI' > > Checksum for > > /root/.cpan/sources/authors/id/T/TI/TIMBRODY/HTTP-OAI-4.03.tar.gz ok > > Configuring T/TI/TIMBRODY/HTTP-OAI-4.03.tar.gz with Makefile.PL > > Checking if your kit is complete... > > Warning: the following files are missing in your kit: > > MYMETA.json > > MYMETA.yml > > Please inform the author. > > Warning: NAME must be a package name > > Generating a Unix-style Makefile > > Writing Makefile for HTTP-OAI > > Writing MYMETA.yml and MYMETA.json > > TIMBRODY/HTTP-OAI-4.03.tar.gz > > /usr/bin/perl Makefile.PL INSTALLDIRS=site -- OK > > Running make for T/TI/TIMBRODY/HTTP-OAI-4.03.tar.gz > > cp lib/HTTP/OAI/Verb.pm blib/lib/HTTP/OAI/Verb.pm > > cp lib/HTTP/OAI/UserAgent.pm blib/lib/HTTP/OAI/UserAgent.pm > > cp lib/HTTP/OAI/Metadata/OAI_Identifier.pm > > blib/lib/HTTP/OAI/Metadata/OAI_Identifier.pm > > cp lib/HTTP/OAI/SAXHandler.pm blib/lib/HTTP/OAI/SAXHandler.pm > > cp lib/HTTP/OAI/Harvester.pm blib/lib/HTTP/OAI/Harvester.pm > > cp lib/HTTP/OAI/Header.pm blib/lib/HTTP/OAI/Header.pm > > cp lib/HTTP/OAI/ListRecords.pm blib/lib/HTTP/OAI/ListRecords.pm > > cp lib/HTTP/OAI/SAX/Driver.pm blib/lib/HTTP/OAI/SAX/Driver.pm > > cp lib/HTTP/OAI/MemberMixin.pm blib/lib/HTTP/OAI/MemberMixin.pm > > cp lib/HTTP/OAI/Response.pm blib/lib/HTTP/OAI/Response.pm > > cp lib/HTTP/OAI/ResumptionToken.pm > blib/lib/HTTP/OAI/ResumptionToken.pm > > cp lib/HTTP/OAI/Metadata/OAI_DC.pm > blib/lib/HTTP/OAI/Metadata/OAI_DC.pm > > cp lib/HTTP/OAI/Metadata/METS.pm > blib/lib/HTTP/OAI/Metadata/METS.pm > > cp lib/HTTP/OAI/SAX/Base.pm blib/lib/HTTP/OAI/SAX/Base.pm > > cp lib/HTTP/OAI/Repository.pm blib/lib/HTTP/OAI/Repository.pm > > cp lib/HTTP/OAI/ListIdentifiers.pm blib/lib/HTTP/OAI/ListIdentifiers.pm > > cp lib/HTTP/OAI/Debug.pm blib/lib/HTTP/OAI/Debug.pm > > cp lib/HTTP/OAI/PartialList.pm blib/lib/HTTP/OAI/PartialList.pm > > cp lib/HTTP/OAI/Set.pm blib/lib/HTTP/OAI/Set.pm > > cp lib/HTTP/OAI/Record.pm blib/lib/HTTP/OAI/Record.pm > > cp lib/HTTP/OAI/Error.pm blib/lib/HTTP/OAI/Error.pm > > cp lib/HTTP/OAI/Metadata/OAI_Eprints.pm > > blib/lib/HTTP/OAI/Metadata/OAI_Eprints.pm > > cp lib/HTTP/OAI/GetRecord.pm blib/lib/HTTP/OAI/GetRecord.pm > > cp lib/HTTP/OAI/Metadata.pm blib/lib/HTTP/OAI/Metadata.pm > > cp lib/HTTP/OAI.pm blib/lib/HTTP/OAI.pm > > cp lib/HTTP/OAI/ListMetadataFormats.pm > > blib/lib/HTTP/OAI/ListMetadataFormats.pm > > cp lib/HTTP/OAI/Encapsulation.pm blib/lib/HTTP/OAI/Encapsulation.pm > > cp lib/HTTP/OAI/Identify.pm blib/lib/HTTP/OAI/Identify.pm > > cp lib/HTTP/OAI/SAX/Text.pm blib/lib/HTTP/OAI/SAX/Text.pm > > cp lib/HTTP/OAI/ListSets.pm blib/lib/HTTP/OAI/ListSets.pm > > cp lib/HTTP/OAI/MetadataFormat.pm > blib/lib/HTTP/OAI/MetadataFormat.pm > > cp lib/HTTP/OAI/SAX/Trace.pm blib/lib/HTTP/OAI/SAX/Trace.pm > > cp bin/oai_pmh.pl blib/script/oai_pmh.pl > > "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/ > > oai_pmh.pl > > cp bin/oai_browser.pl blib/script/oai_browser.pl > > "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/ > > oai_browser.pl > > Manifying 2 pod documents > > Manifying 25 pod documents > > TIMBRODY/HTTP-OAI-4.03.tar.gz > > /usr/bin/make -- OK > > Running make test > > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" > > "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, > > 'blib/lib', 'blib/arch')" t/*.t > > t/000xml_sax.t ........... ok > > t/00static.t ............. ok > > t/01parse.t .............. ok > > t/02token.t .............. ok > > t/03badbytes.t ........... ok > > t/50mets.t ............... ok > > t/80network.t ............ ok > > t/error.t ................ ok > > t/getrecord.t ............ 1/8 Can't call method "start_element" on an > > undefined value at > > /root/.cpan/build/HTTP-OAI-4.03-UQClDl/blib/lib/HTTP/OAI/Verb.pm line > 53. > > # Looks like you planned 8 tests but ran 7. > > # Looks like your test exited with 255 just after 7. > > t/getrecord.t ............ Dubious, test returned 255 (wstat 65280, 0xff00) > > Failed 1/8 subtests > > t/identify.t ............. ok > > t/listidentifiers.t ...... ok > > t/listmetadataformats.t .. ok > > > > Test Summary Report > > ------------------- > > t/getrecord.t (Wstat: 65280 Tests: 7 Failed: 0) > > Non-zero exit status: 255 > > Parse errors: Bad plan. You planned 8 tests but ran 7. > > Files=12, Tests=78, 8 wallclock secs ( 0.04 usr 0.02 sys + 1.43 cusr > > 0.11 csys = 1.60 CPU) > > Result: FAIL > > Failed 1/12 test programs. 0/78 subtests failed. > > make: *** [test_dynamic] Error 255 > > TIMBRODY/HTTP-OAI-4.03.tar.gz > > /usr/bin/make test -- NOT OK > > //hint// to see the cpan-testers results for installing this module, try: > > reports TIMBRODY/HTTP-OAI-4.03.tar.gz > > root at library-HP-Pro-3400-Series-MT:/home/koha-3.10.02# > > > > help me > > > > -- > > regina > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > ************************************* From indradg at gmail.com Mon Apr 18 08:06:53 2016 From: indradg at gmail.com (Indranil Das Gupta) Date: Mon, 18 Apr 2016 11:36:53 +0530 Subject: [Koha-devel] Who all are purposing Koha as an Union Catalog? In-Reply-To: <011901d1992b$c663d590$532b80b0$@prosentient.com.au> References: <011901d1992b$c663d590$532b80b0$@prosentient.com.au> Message-ID: Hi David, On Mon, Apr 18, 2016 at 10:05 AM, David Cook wrote: > We put together a proof of concept using my original OAI-PMH harvester, but > I wasn't a huge fan of it, as it was very simple. It didn't deduplicate > biblios, and it didn't include items (although we had the OAI-PMH server > inject a URL pointing back to the original Koha instance with the number of > items attached to the biblio). Thanks for the reply. You have touched upon several of the concerns I had. My biggest concern is de-duplication and how to go about - how to match, but even before that how to curate the data that one is receiving from participating libraries as MARC exports, so that we can maximize the maximum number of matches. Is there any set standards, rules (even rule of thumb) in these? I mean beyond matching (a) ISBN or (b) Title + Author + edition? This is what i want to hear about and learn from people like you and others who have already ventured into these areas. Brooke have replied earlier and pointed me to masscat done by Bywater. thanks in advance. -- 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 From dcook at prosentient.com.au Mon Apr 18 08:36:25 2016 From: dcook at prosentient.com.au (David Cook) Date: Mon, 18 Apr 2016 16:36:25 +1000 Subject: [Koha-devel] Who all are purposing Koha as an Union Catalog? In-Reply-To: References: <011901d1992b$c663d590$532b80b0$@prosentient.com.au> Message-ID: <014701d1993c$a1b69500$e523bf00$@prosentient.com.au> Hi Indranil: I just had another thought. You could also have 1 Koha instance as the master catalogue and have people catalogue there. Individual libraries could then pull down their bibliographic records and maybe authority records via specific OAI-PMH sets. There would still be the problem of item records of course... David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Indranil Das Gupta [mailto:indradg at gmail.com] > Sent: Monday, 18 April 2016 4:07 PM > To: David Cook > Cc: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] Who all are purposing Koha as an Union Catalog? > > Hi David, > > On Mon, Apr 18, 2016 at 10:05 AM, David Cook > wrote: > > We put together a proof of concept using my original OAI-PMH > > harvester, but I wasn't a huge fan of it, as it was very simple. It > > didn't deduplicate biblios, and it didn't include items (although we > > had the OAI-PMH server inject a URL pointing back to the original Koha > > instance with the number of items attached to the biblio). > > Thanks for the reply. You have touched upon several of the concerns I had. > My biggest concern is de-duplication and how to go about - how to match, > but even before that how to curate the data that one is receiving from > participating libraries as MARC exports, so that we can maximize the > maximum number of matches. Is there any set standards, rules (even rule of > thumb) in these? I mean beyond matching (a) ISBN or (b) Title + Author + > edition? > > This is what i want to hear about and learn from people like you and others > who have already ventured into these areas. Brooke have replied earlier and > pointed me to masscat done by Bywater. > > thanks in advance. > > > > -- > 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 From tomascohen at gmail.com Tue Apr 19 16:34:32 2016 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 19 Apr 2016 11:34:32 -0300 Subject: [Koha-devel] Frameworks / DB constraints Message-ID: Hi fellows, I noticed (in a production server) that a cataloguing framework was deleted by a user. This raised a problem with records that used that framework: trying to look at the record's detail page ended up in a fatal error. Currently, the framework code is not a FK, so we don't enforce it at DB level. A possible solution is to just add it as a FK, another option would be to fallback to the default framework in the relevant function. Jesse proposed on IRC creating the foreign key with ON DELETE SET NULL. We need to fix this, so: ideas? preferences? vote? -- Tom?s Cohen Arazi Theke Solutions (http://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Tue Apr 19 17:16:26 2016 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Tue, 19 Apr 2016 17:16:26 +0200 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: References: Message-ID: <57164BCA.9030004@cineca.it> Hi to all, Il 19/04/2016 16:34, Tomas Cohen Arazi ha scritto: > Hi fellows, I noticed (in a production server) that a cataloguing > framework was deleted by a user. This raised a problem with records that > used that framework: trying to look at the record's detail page ended up > in a fatal error. [...] > Jesse proposed on IRC creating the foreign key with ON DELETE SET NULL. I'm agree on solution proposed by Jesse: creating the foreign key with ON DELETE SET NULL. Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From tomascohen at gmail.com Tue Apr 19 19:29:46 2016 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 19 Apr 2016 14:29:46 -0300 Subject: [Koha-devel] kohadevbox:ansible update: custom repositories Message-ID: I have updated kohadevbox:ansible so it can be set to use custom repositories. This is really important when it comes to testing package-related patches. This way the patch creator can build a package on a repo and ease testers' lives. Regards -- Tom?s Cohen Arazi Theke Solutions (http://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From indradg at gmail.com Tue Apr 19 19:50:28 2016 From: indradg at gmail.com (Indranil Das Gupta) Date: Tue, 19 Apr 2016 23:20:28 +0530 Subject: [Koha-devel] kohadevbox:ansible update: custom repositories In-Reply-To: References: Message-ID: On Apr 19, 2016 11:00 PM, "Tomas Cohen Arazi" wrote: > > This way the patch creator can build a package on a repo and ease testers' lives. Tomas++ -idg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer.83 at web.de Tue Apr 19 21:12:04 2016 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Tue, 19 Apr 2016 21:12:04 +0200 Subject: [Koha-devel] Reminder: Koha Developer Meeting - 20 April 2016, 15 UTC Message-ID: <57168304.5070003@web.de> Hello all, it's me again - sending another meeting reminder: https://wiki.koha-community.org/wiki/Development_IRC_meeting_20_April_2016 Please add the topics you want to talk about to the meeting agenda on the wiki. This will also be the last developer meeting before feature freeze on April 28! Hope to see you there, Katrin From Katrin.Fischer.83 at web.de Tue Apr 19 21:29:27 2016 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Tue, 19 Apr 2016 21:29:27 +0200 Subject: [Koha-devel] Nominations and elections for the 16.11 release team Message-ID: <57168717.5060501@web.de> Hi all, time flies and while the release of 16.05 comes close, we need to start planning for 16.11! So a nomination page has been added to the wiki: https://wiki.koha-community.org/wiki/Roles_for_16.11 Please add your name on the wiki page if you are interested in taking on one of the roles. We aim to hold elections at the next general IRC meeting which is scheduled for May 4, 20 UTC: https://wiki.koha-community.org/wiki/General_IRC_meeting_4_May_2016 Katrin From gmc at esilibrary.com Wed Apr 20 04:03:23 2016 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 19 Apr 2016 22:03:23 -0400 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: <57164BCA.9030004@cineca.it> References: <57164BCA.9030004@cineca.it> Message-ID: Hi, On Tue, Apr 19, 2016 at 11:16 AM, Tajoli Zeno wrote: > I'm agree on solution proposed by Jesse: creating the foreign key with ON > DELETE SET NULL. At the moment, biblio.frameworkcode doesn't permit NULL values, and InnoDB doesn't support ON DELETE SET DEFAULT. That doesn't mean that we couldn't do more work so that frameworkcode IS NULL is fully supported, but it's not *just* a matter of adding the FK. I'm more in favor of either: - adding a FK that does ON DELETE RESTRICT. For most databases, this would require adding a row to biblio_framework whose frameworkcode is the empty string. - having the business logic take care of falling back to the default framework when necessary. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org From dcook at prosentient.com.au Wed Apr 20 06:07:03 2016 From: dcook at prosentient.com.au (David Cook) Date: Wed, 20 Apr 2016 14:07:03 +1000 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: References: <57164BCA.9030004@cineca.it> Message-ID: <022301d19aba$18a07ae0$49e170a0$@prosentient.com.au> I agree with Galen. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Galen Charlton > Sent: Wednesday, 20 April 2016 12:03 PM > To: Tajoli Zeno > Cc: koha-devel > Subject: Re: [Koha-devel] Frameworks / DB constraints > > Hi, > > On Tue, Apr 19, 2016 at 11:16 AM, Tajoli Zeno wrote: > > I'm agree on solution proposed by Jesse: creating the foreign key with > > ON DELETE SET NULL. > > At the moment, biblio.frameworkcode doesn't permit NULL values, and > InnoDB doesn't support ON DELETE SET DEFAULT. That doesn't mean that we > couldn't do more work so that frameworkcode IS NULL is fully supported, but > it's not *just* a matter of adding the FK. > > I'm more in favor of either: > > - adding a FK that does ON DELETE RESTRICT. For most databases, this would > require adding a row to biblio_framework whose frameworkcode is the > empty string. > - having the business logic take care of falling back to the default framework > when necessary. > > Regards, > > Galen > -- > Galen Charlton > Infrastructure and Added Services Manager Equinox Software, Inc. / Open > Your Library > email: gmc at esilibrary.com > direct: +1 770-709-5581 > cell: +1 404-984-4366 > skype: gmcharlt > web: http://www.esilibrary.com/ > Supporting Koha and Evergreen: http://koha-community.org & > http://evergreen-ils.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From dcook at prosentient.com.au Wed Apr 20 09:00:21 2016 From: dcook at prosentient.com.au (David Cook) Date: Wed, 20 Apr 2016 17:00:21 +1000 Subject: [Koha-devel] Updating Koha manual documenation Message-ID: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> Hey all, What's the procedure for updating Koha manual documentation? I'd like to expand on http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see there is a kohadocs.git to which Nicole contributes (http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but do those changes still go through Bugzilla? Does one clone the repository and just post the patches to Bugzilla and mark it as documentation? And then Nicole/RM does the merging from there? I basically just want to add that searching "title" will use "index.dc.title" because the default set in pqf.properties is "dc", and that you can use other sets by adding the prefix like "f bath.keyTitle=test" in yaz-client when using "querytype cql". But there's heaps of other search documentation that I'd like to edit, so I figure I may as well get up to speed on the procedure! I've been saying for years that I should contribute to the documentation, so maybe I should put my words where my... words are! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed Apr 20 14:59:34 2016 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 20 Apr 2016 09:59:34 -0300 Subject: [Koha-devel] Updating Koha manual documenation In-Reply-To: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> References: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> Message-ID: I think it should follow the regular BZ workflow. 2016-04-20 4:00 GMT-03:00 David Cook : > Hey all, > > > > What?s the procedure for updating Koha manual documentation? > > > > I?d like to expand on > http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see there > is a kohadocs.git to which Nicole contributes ( > http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but do > those changes still go through Bugzilla? > > > > Does one clone the repository and just post the patches to Bugzilla and > mark it as documentation? And then Nicole/RM does the merging from there? > > > > I basically just want to add that searching ?title? will use > ?index.dc.title? because the default set in pqf.properties is ?dc?, and > that you can use other sets by adding the prefix like ?f > bath.keyTitle=test? in yaz-client when using ?querytype cql?. > > > > But there?s heaps of other search documentation that I?d like to edit, so > I figure I may as well get up to speed on the procedure! I?ve been saying > for years that I should contribute to the documentation, so maybe I should > put my words where my... words are! > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tom?s Cohen Arazi Theke Solutions (http://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Wed Apr 20 15:00:18 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 20 Apr 2016 13:00:18 +0000 Subject: [Koha-devel] Signoff request Message-ID: Hi all, In view of the coming freeze date, I could also use a signoff on a few reports, mentioning two devs : Bug 16155 Changes to TestBuilder Bug 14834/Bug 15543 Extensions to membership expiry feature This runs fine in our production environment. Thanks, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Wed Apr 20 15:33:30 2016 From: barton at bywatersolutions.com (Barton Chittenden) Date: Wed, 20 Apr 2016 09:33:30 -0400 Subject: [Koha-devel] Updating Koha manual documenation In-Reply-To: References: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> Message-ID: Agreed. There is a 'Documentation' category in bugzilla. The documentation is in docbook format; I'm sure that you could supply patches, or I'm sure that Nicole would be happy to make edits if you supply the text. --Barton On Wed, Apr 20, 2016 at 8:59 AM, Tomas Cohen Arazi wrote: > I think it should follow the regular BZ workflow. > > 2016-04-20 4:00 GMT-03:00 David Cook : > >> Hey all, >> >> >> >> What?s the procedure for updating Koha manual documentation? >> >> >> >> I?d like to expand on >> http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see >> there is a kohadocs.git to which Nicole contributes ( >> http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but do >> those changes still go through Bugzilla? >> >> >> >> Does one clone the repository and just post the patches to Bugzilla and >> mark it as documentation? And then Nicole/RM does the merging from there? >> >> >> >> I basically just want to add that searching ?title? will use >> ?index.dc.title? because the default set in pqf.properties is ?dc?, and >> that you can use other sets by adding the prefix like ?f >> bath.keyTitle=test? in yaz-client when using ?querytype cql?. >> >> >> >> But there?s heaps of other search documentation that I?d like to edit, so >> I figure I may as well get up to speed on the procedure! I?ve been saying >> for years that I should contribute to the documentation, so maybe I should >> put my words where my... words are! >> >> >> >> David Cook >> >> Systems Librarian >> >> >> >> Prosentient Systems >> >> 72/330 Wattle St >> >> Ultimo, NSW 2007 >> >> >> >> Office: 02 9212 0899 >> >> Direct: 02 8005 0595 >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > > > > -- > Tom?s Cohen Arazi > Theke Solutions (http://theke.io) > ? +54 9351 3513384 > GPG: B2F3C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Wed Apr 20 16:49:08 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 20 Apr 2016 14:49:08 +0000 Subject: [Koha-devel] Signoff request In-Reply-To: References: , Message-ID: Thanks a lot. Will have a look at 16155 very soon.. ________________________________ Van: Bernardo Gonzalez Kriegel Verzonden: woensdag 20 april 2016 16:46 Aan: Marcel de Rooy Onderwerp: Re: [Koha-devel] Signoff request Hi Marcel, 14834 and 15543 are done. 16155 has some problems. Bernardo -- Bernardo Gonzalez Kriegel bgkriegel at gmail.com On Wed, Apr 20, 2016 at 10:00 AM, Marcel de Rooy > wrote: Hi all, In view of the coming freeze date, I could also use a signoff on a few reports, mentioning two devs : Bug 16155 Changes to TestBuilder Bug 14834/Bug 15543 Extensions to membership expiry feature This runs fine in our production environment. Thanks, Marcel _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Apr 21 05:22:57 2016 From: dcook at prosentient.com.au (David Cook) Date: Thu, 21 Apr 2016 13:22:57 +1000 Subject: [Koha-devel] Understanding Zebra SRU Message-ID: <02a401d19b7d$19c87580$4d596080$@prosentient.com.au> Hi all, Who all is using SRU with Zebra? I know that Marcel has been interested in Zebra's SRU since at least 2009, but information is a bit bare out there. I recently received an off-list email asking about Zebra and SRU, especially relevance searching and sorting. I admitted that I only knew about Zebra's Z39.50 functionality, so naturally I started looking into SRU and CQL. I found this webpage to be extremely helpful (alas I only found it after a day or two of experimentation): https://www.loc.gov/standards/sru/cql/spec.html I started by experimenting with CQL in yaz-client. That's as simple as "querytype cql" and "set_cqlfile /home/koha/koha-dev/etc/zebradb/pqf.properties". It took a few minutes to get me head around pqf.properties and that it defaults to using the "dc" set. For all other sets like "bath", you have to prefix with the set name (e.g. bath.name). Z> find title=brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 1 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.019602 Z> find bath.name=randy Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 2, setno 2 SearchResult-1: term=randy cnt=2 records returned: 0 Elapsed: 0.020180 I seem to be able to get relevance ranking with the following (= is the relation, and relevant is the relation modifier): Z> find title=/relevant brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 9 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001049 Then a A-Z title sort with the following: Z> find title=brand sortby title/sort.ascending Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 11 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001210 So that's CQL in yaz-client, and you can use SRU or Z39.50 for the same result there. So I made the following change to my koha-conf.xml: tcp:@:9999 Restarted Zebra and started making SRU requests: wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq brand&startRecord=1&maximumRecords=10&recordSchema=marcxml" Records in ascending order by biblionumber wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq brand sortBy dc.title/sort.ascending&startRecord=1&maximumRecords=10&recordSchema=marcxml " Records in ascending order by dc.title wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq/relevant brand&startRecord=1&maximumRecords=10&recordSchema=marcxml" Records in descending order by relevance. This one can be harder to test at a glance. but "format xml" and "elements zebra::meta" will reveal the relevance score of our records in yaz-client! Z> find any=/relevant brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 10 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001298 Z> format xml Z> elements zebra::meta Z> show 1 Sent presentRequest (1+1). Records: 1 Record type: XML nextResultSetPosition = 2 Elapsed: 0.028276 Z> Sent presentRequest (2+1). Records: 1 Record type: XML nextResultSetPosition = 3 Elapsed: 0.000612 You'd think that "rank" would provide useful info, but I think that just relates to static rank (see http://www.indexdata.com/zebra/doc/special-retrieval.html). Score is what we want here. Note that score appears to only appear for relevance queries. Anyway. I hope that info is useful to some of you, and I'd be curious if others have any neat tips for using SRU. I don't know if I'll be using it any time soon, but it's interesting to think about, even in anticipation of ElasticSearch. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Thu Apr 21 08:39:35 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 21 Apr 2016 06:39:35 +0000 Subject: [Koha-devel] Understanding Zebra SRU In-Reply-To: <02a401d19b7d$19c87580$4d596080$@prosentient.com.au> References: <02a401d19b7d$19c87580$4d596080$@prosentient.com.au> Message-ID: > Who all is using SRU with Zebra? I know that Marcel has been interested in Zebra's SRU since at least 2009, but information is a bit bare out there. Yes, I am. Both IN and OUT. Under Z39.50 admin you can also add SRU servers to import marc records. We do. > Anyway... I hope that info is useful to some of you, and I'd be curious if others have any neat tips for using SRU. I don't know if I'll be using it any time soon, but it's interesting to think about, even in anticipation of ElasticSearch... BTW If Elastic Search does not offer SRU, I would say that the job is not complete yet. (Zebra does out of the box.) Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From magnus at enger.priv.no Thu Apr 21 09:39:31 2016 From: magnus at enger.priv.no (Magnus Enger) Date: Thu, 21 Apr 2016 09:39:31 +0200 Subject: [Koha-devel] Updating Koha manual documenation In-Reply-To: References: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> Message-ID: Hiya! The description of the koha-docs mailing list says "This list will be used to send patches to the documentation manager. Please send all documentation patches to this list for review." I know I have sent documentation patches to this before, and Nicole has pushed them. http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs The easiest thing might be to ask Nicole on IRC, I guess. Best regards, Magnus On 20 April 2016 at 15:33, Barton Chittenden wrote: > Agreed. > > There is a 'Documentation' category in bugzilla. The documentation is in > docbook format; I'm sure that you could supply patches, or I'm sure that > Nicole would be happy to make edits if you supply the text. > > --Barton > > On Wed, Apr 20, 2016 at 8:59 AM, Tomas Cohen Arazi > wrote: >> >> I think it should follow the regular BZ workflow. >> >> 2016-04-20 4:00 GMT-03:00 David Cook : >>> >>> Hey all, >>> >>> >>> >>> What?s the procedure for updating Koha manual documentation? >>> >>> >>> >>> I?d like to expand on >>> http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see there is >>> a kohadocs.git to which Nicole contributes >>> (http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but do >>> those changes still go through Bugzilla? >>> >>> >>> >>> Does one clone the repository and just post the patches to Bugzilla and >>> mark it as documentation? And then Nicole/RM does the merging from there? >>> >>> >>> >>> I basically just want to add that searching ?title? will use >>> ?index.dc.title? because the default set in pqf.properties is ?dc?, and that >>> you can use other sets by adding the prefix like ?f bath.keyTitle=test? in >>> yaz-client when using ?querytype cql?. >>> >>> >>> >>> But there?s heaps of other search documentation that I?d like to edit, so >>> I figure I may as well get up to speed on the procedure! I?ve been saying >>> for years that I should contribute to the documentation, so maybe I should >>> put my words where my... words are! >>> >>> >>> >>> David Cook >>> >>> Systems Librarian >>> >>> >>> >>> Prosentient Systems >>> >>> 72/330 Wattle St >>> >>> Ultimo, NSW 2007 >>> >>> >>> >>> Office: 02 9212 0899 >>> >>> Direct: 02 8005 0595 >>> >>> >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at 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/ >> >> >> >> >> -- >> Tom?s Cohen Arazi >> Theke Solutions (http://theke.io) >> ? +54 9351 3513384 >> GPG: B2F3C15F >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From Andreas.Hedstrom.Mace at sub.su.se Thu Apr 21 11:23:25 2016 From: Andreas.Hedstrom.Mace at sub.su.se (=?utf-8?B?QW5kcmVhcyBIZWRzdHLDtm0gTWFjZQ==?=) Date: Thu, 21 Apr 2016 09:23:25 +0000 Subject: [Koha-devel] Final stretch before the next release (3.24 | 16.05) In-Reply-To: <570C9148.4090604@biblibre.com> References: <570C9148.4090604@biblibre.com> Message-ID: <1CAB4169-1962-430B-B244-8D0C8608A731@sub.su.se> Hi all! >> >I think those 6 points are really important, but I would like to add a >7th point : the REST API hasn't moved since its introduction in 3.22. >Bugs 15126 and 13903 are signed off, and it would be great to have them >pushed in 16.05, just to see some movement here :) I want to echo this sentiment that Julian wrote two weeks ago. It would be very good to see more REST API patches get pushed so that there is some progress on this front! Apart from the ones mentioned above there are a number of others that would benefit from some attention (like 16271, 16213 and 15165). Best regards, Andreas ____________________________________ Andreas Hedstr?m Mace Librarian Stockholm University Library Stockholm University 106 91 Stockholm Tel: +46 (0) 8-16 49 17 www.su.se/english/library/ ____________________________________ From nengard at gmail.com Thu Apr 21 14:35:25 2016 From: nengard at gmail.com (Nicole Engard) Date: Thu, 21 Apr 2016 07:35:25 -0500 Subject: [Koha-devel] Updating Koha manual documenation In-Reply-To: References: <022f01d19ad2$4e304150$ea90c3f0$@prosentient.com.au> Message-ID: Sorry for my delay all. Here's the wiki page on this: https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual Patches are submitted to the Docs list. Thanks Nicole On Thu, Apr 21, 2016 at 2:39 AM, Magnus Enger wrote: > Hiya! > > The description of the koha-docs mailing list says "This list will be > used to send patches to the documentation manager. Please send all > documentation patches to this list for review." I know I have sent > documentation patches to this before, and Nicole has pushed them. > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs > > The easiest thing might be to ask Nicole on IRC, I guess. > > Best regards, > Magnus > > On 20 April 2016 at 15:33, Barton Chittenden > wrote: > > Agreed. > > > > There is a 'Documentation' category in bugzilla. The documentation is in > > docbook format; I'm sure that you could supply patches, or I'm sure that > > Nicole would be happy to make edits if you supply the text. > > > > --Barton > > > > On Wed, Apr 20, 2016 at 8:59 AM, Tomas Cohen Arazi > > > wrote: > >> > >> I think it should follow the regular BZ workflow. > >> > >> 2016-04-20 4:00 GMT-03:00 David Cook : > >>> > >>> Hey all, > >>> > >>> > >>> > >>> What?s the procedure for updating Koha manual documentation? > >>> > >>> > >>> > >>> I?d like to expand on > >>> http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see > there is > >>> a kohadocs.git to which Nicole contributes > >>> (http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but > do > >>> those changes still go through Bugzilla? > >>> > >>> > >>> > >>> Does one clone the repository and just post the patches to Bugzilla and > >>> mark it as documentation? And then Nicole/RM does the merging from > there? > >>> > >>> > >>> > >>> I basically just want to add that searching ?title? will use > >>> ?index.dc.title? because the default set in pqf.properties is ?dc?, > and that > >>> you can use other sets by adding the prefix like ?f > bath.keyTitle=test? in > >>> yaz-client when using ?querytype cql?. > >>> > >>> > >>> > >>> But there?s heaps of other search documentation that I?d like to edit, > so > >>> I figure I may as well get up to speed on the procedure! I?ve been > saying > >>> for years that I should contribute to the documentation, so maybe I > should > >>> put my words where my... words are! > >>> > >>> > >>> > >>> David Cook > >>> > >>> Systems Librarian > >>> > >>> > >>> > >>> Prosentient Systems > >>> > >>> 72/330 Wattle St > >>> > >>> Ultimo, NSW 2007 > >>> > >>> > >>> > >>> Office: 02 9212 0899 > >>> > >>> Direct: 02 8005 0595 > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Koha-devel mailing list > >>> Koha-devel at 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/ > >> > >> > >> > >> > >> -- > >> Tom?s Cohen Arazi > >> Theke Solutions (http://theke.io) > >> ? +54 9351 3513384 > >> GPG: B2F3C15F > >> > >> _______________________________________________ > >> Koha-devel mailing list > >> Koha-devel at 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/ > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Thu Apr 21 16:02:47 2016 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Fri, 22 Apr 2016 02:02:47 +1200 Subject: [Koha-devel] Understanding Zebra SRU In-Reply-To: References: <02a401d19b7d$19c87580$4d596080$@prosentient.com.au> Message-ID: <061256D0-1BA4-423F-B440-656F9DF67B48@catalyst.net.nz> On 21 April 2016 6:39:35 pm NZST, Marcel de Rooy wrote: >> Who all is using SRU with Zebra? I know that Marcel has been >interested in Zebra's SRU since at least 2009, but information is a bit >bare out there. > >Yes, I am. Both IN and OUT. Under Z39.50 admin you can also add SRU >servers to import marc records. We do. > >> Anyway... I hope that info is useful to some of you, and I'd be >curious if others have any neat tips for using SRU. I don't know if >I'll be using it any time soon, but it's interesting to think about, >even in anticipation of ElasticSearch... > >BTW If Elastic Search does not offer SRU, I would say that the job is >not complete yet. (Zebra does out of the box.) Elasticsearch is not replacing Zebra. Not in the near future anyway. Even if you have Elasticsearch turned on the Zebra indexes are still kept up to date. Chris > >Marcel > > > >------------------------------------------------------------------------ > >_______________________________________________ >Koha-devel mailing list >Koha-devel at 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/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From mirko at abunchofthings.net Fri Apr 22 17:12:06 2016 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 22 Apr 2016 16:12:06 +0100 Subject: [Koha-devel] Debian packaging workshop Message-ID: <571A3F46.9090106@abunchofthings.net> Hello everyone, I made a tiny survey to get an idea of how many people might want to take part in a Debian packaging workshop at the hackfests in Berlin or Thessaloniki. Please donate 30 seconds of your time. Please just answer for yourself, don't invite your facebook friends and tweet about it. I'm only looking for the number of active Koha devs interested right now and it's not a binding vote or anything. I won't publish your names of course. http://abunchofthings.net/limesurvey/index.php/396251?lang=en Thanks! -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From mtompset at hotmail.com Fri Apr 22 17:38:27 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Fri, 22 Apr 2016 11:38:27 -0400 Subject: [Koha-devel] Debian packaging workshop In-Reply-To: <571A3F46.9090106@abunchofthings.net> References: <571A3F46.9090106@abunchofthings.net> Message-ID: Greetings, Might I suggest another question which I'd place first? "I would like to take part in a Debian packaging workshop." "Definitely, just tell me where." "Maybe, depending on where it is." "Not sure, but maybe in the future." "I am not interested at all." Because I have no ability to travel (unless people want to donate airfare, etc.), but I would love to go to one. GPML, Mark Tompsett From mirko at abunchofthings.net Fri Apr 22 17:48:40 2016 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 22 Apr 2016 16:48:40 +0100 Subject: [Koha-devel] Debian packaging workshop In-Reply-To: References: <571A3F46.9090106@abunchofthings.net> Message-ID: <571A47D8.4040902@abunchofthings.net> Hi Mark, I am sure that is the case for quite a few people. Unfortunately that would be another survey, because it's not really relevant for what I am working on at the moment. So I tried to keep it as short as possible. Sorry! -- Mirko -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From mirko at abunchofthings.net Fri Apr 22 18:14:29 2016 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 22 Apr 2016 17:14:29 +0100 Subject: [Koha-devel] Debian packaging workshop In-Reply-To: References: <571A3F46.9090106@abunchofthings.net> Message-ID: <571A4DE5.8090700@abunchofthings.net> > Because I have no ability to travel (unless people want to donate > airfare, etc.), but I would love to go to one. Another thought: that is a perfect starting point for organizing such a workshop in your area! :) -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From jonathan.druart at bugs.koha-community.org Sat Apr 23 08:08:41 2016 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Sat, 23 Apr 2016 07:08:41 +0100 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: References: Message-ID: Just a note: From 16.05 it won't be possible to delete a framework in used from the interface. See bug 15790. 2016-04-19 15:34 GMT+01:00 Tomas Cohen Arazi : > Hi fellows, I noticed (in a production server) that a cataloguing framework > was deleted by a user. This raised a problem with records that used that > framework: trying to look at the record's detail page ended up in a fatal > error. > > Currently, the framework code is not a FK, so we don't enforce it at DB > level. A possible solution is to just add it as a FK, another option would > be to fallback to the default framework in the relevant function. Jesse > proposed on IRC creating the foreign key with ON DELETE SET NULL. > > We need to fix this, so: ideas? preferences? vote? > > -- > Tom?s Cohen Arazi > Theke Solutions (http://theke.io) > ? +54 9351 3513384 > GPG: B2F3C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From wosch at freebsd.org Mon Apr 25 13:30:09 2016 From: wosch at freebsd.org (Wolfram Schneider) Date: Mon, 25 Apr 2016 13:30:09 +0200 Subject: [Koha-devel] Koha Calendar Message-ID: On the Koha web site is a link "Calendar" https://koha-community.org/calendar/ There are only entries for "Koha Bugfix Release" I miss the KohaConf, Koha Hackfest, IRC meeting etc... I'm wondering if the calendar is still maintained? -Wolfram -- Wolfram Schneider http://wolfram.schneider.org From mirko at abunchofthings.net Mon Apr 25 23:21:38 2016 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Mon, 25 Apr 2016 22:21:38 +0100 Subject: [Koha-devel] Debian packaging workshop In-Reply-To: <571A3F46.9090106@abunchofthings.net> References: <571A3F46.9090106@abunchofthings.net> Message-ID: <571E8A62.2010904@abunchofthings.net> Still open, please take 30 seconds to answer if you are going to Berlin or Thessaloniki. I doubt we only have a handful of Koha devs in Europe in a few weeks? > http://abunchofthings.net/limesurvey/index.php/396251?lang=en -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From mtompset at hotmail.com Tue Apr 26 02:59:45 2016 From: mtompset at hotmail.com (Mark Tompsett) Date: Mon, 25 Apr 2016 20:59:45 -0400 Subject: [Koha-devel] Sign off request... Message-ID: Greetings, A pretty simple sign off: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15086 GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry at opengeek.cl Wed Apr 27 07:09:02 2016 From: larry at opengeek.cl (Larry Letelier) Date: Wed, 27 Apr 2016 02:09:02 -0300 Subject: [Koha-devel] Invalid local time for date in time zone: America/Santiago Message-ID: Hi people, We have a 'little' issue with the overdue aka notifications process. # pwd /usr/share/koha/bin/cronjobs # ./overdue_notices.pl -t Invalid local time for date in time zone: America/Santiago perl -d overdue_notices.pl -t Loading DB routines from perl5db.pl version 1.33 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(overdue_notices.pl:278): my $dbh = C4::Context->dbh(); DB<1> c Invalid local time for date in time zone: America/Santiago at /usr/share/perl5/DateTime/TimeZone.pm line 198 DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'local', 'DateTime=HASH(0x617e938)') called at /usr/share/perl5/DateTime/TimeZone.pm line 157 DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 375 DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 263 DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at /usr/lib/perl5/DateTime.pm line 299 DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, 'minute', 0, 'second', 0, 'month', 9, ...) called at /usr/lib/perl5/DateTime.pm line 1933 DateTime::truncate(undef, 'to', 'day') called at /usr/share/koha/lib/Koha/Calendar.pm line 214 Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm line 290 Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at overdue_notices.pl line 538 Debugged program terminated. Use q to quit or R to restart, use o inhibit_exit to avoid stopping after program termination, h q, h R or h o to get additional info. DB<1> q This is a Koha 3.2008000 In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. Any idea with this ? Thanks for read this, -Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed Apr 27 16:50:50 2016 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 27 Apr 2016 11:50:50 -0300 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: References: Message-ID: So it's fixed. Thanks Jonathan, again :-D 2016-04-23 3:08 GMT-03:00 Jonathan Druart < jonathan.druart at bugs.koha-community.org>: > Just a note: From 16.05 it won't be possible to delete a framework in > used from the interface. > See bug 15790. > > 2016-04-19 15:34 GMT+01:00 Tomas Cohen Arazi : > > Hi fellows, I noticed (in a production server) that a cataloguing > framework > > was deleted by a user. This raised a problem with records that used that > > framework: trying to look at the record's detail page ended up in a fatal > > error. > > > > Currently, the framework code is not a FK, so we don't enforce it at DB > > level. A possible solution is to just add it as a FK, another option > would > > be to fallback to the default framework in the relevant function. Jesse > > proposed on IRC creating the foreign key with ON DELETE SET NULL. > > > > We need to fix this, so: ideas? preferences? vote? > > > > -- > > Tom?s Cohen Arazi > > Theke Solutions (http://theke.io) > > ? +54 9351 3513384 > > GPG: B2F3C15F > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tom?s Cohen Arazi Theke Solutions (http://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Apr 28 04:53:35 2016 From: dcook at prosentient.com.au (David Cook) Date: Thu, 28 Apr 2016 12:53:35 +1000 Subject: [Koha-devel] Invalid local time for date in time zone: America/Santiago In-Reply-To: References: Message-ID: <018201d1a0f9$28a3a850$79eaf8f0$@prosentient.com.au> Oh, that?s interesting. I?ve seen this happen on other Perl projects during daylight savings time changes. For instance, try the following Perl code: use DateTime; my $dt = DateTime->new( year => 2015, month => 10, day => 4, hour => 2, minute => 0, second => 0, time_zone => 'Australia/Sydney', ); You?ll get the message: ?Invalid local time for date in time zone: Australia/Sydney? If I recall correctly, it?s because 4 October 2015 2:00am Australia/Sydney didn?t exist. When that time was reached, the clock actually skipped forward, and it became 4 October 2015 3:00am Australia/Sydney. In effect, local time went from 1:59:59 to 3:00:00. 2:00:00 through 2:59:59 never existed. Fascinating, no? Wikipedia says that Chile stopped observing DST in 2015: https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_Americas#Chile. However, I?m guessing that perhaps your server/the Perl module doesn?t know that? ?Chile currently observes Daylight Saving Time (DST). Instead of turning the clocks back one hour on Sunday, April 26, 2015 as previously planned, the Chilean Government has decided to make no further changes to the clock in future years.? ( http://www.timeanddate.com/news/time/chile-abolishes-dst-2015.html). Hmm? I don?t know what date is the problem? Could you run ?perl -d overdue_notices.pl -t" again, but use ?n? instead of ?c?? That way, you?ll be able to see what exact call is generating this error. I?m guessing it might be one of the lines: my $today = DateTime->now(time_zone => C4::Context->tz ); But that?s just a guess. What happens if you try running your overdues again? You might have had the misfortune of the overdues just running at the wrong time on the wrong day. Curious to hear how you go! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Larry Letelier Sent: Wednesday, 27 April 2016 3:09 PM To: koha-devel at lists.koha-community.org Subject: [Koha-devel] Invalid local time for date in time zone: America/Santiago Hi people, We have a 'little' issue with the overdue aka notifications process. # pwd /usr/share/koha/bin/cronjobs # ./overdue_notices.pl -t Invalid local time for date in time zone: America/Santiago perl -d overdue_notices.pl -t Loading DB routines from perl5db.pl version 1.33 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(overdue_notices.pl:278 ): my $dbh = C4::Context->dbh(); DB<1> c Invalid local time for date in time zone: America/Santiago at /usr/share/perl5/DateTime/TimeZone.pm line 198 DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'local', 'DateTime=HASH(0x617e938)') called at /usr/share/perl5/DateTime/TimeZone.pm line 157 DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 375 DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 263 DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at /usr/lib/perl5/DateTime.pm line 299 DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, 'minute', 0, 'second', 0, 'month', 9, ...) called at /usr/lib/perl5/DateTime.pm line 1933 DateTime::truncate(undef, 'to', 'day') called at /usr/share/koha/lib/Koha/Calendar.pm line 214 Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm line 290 Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at overdue_notices.pl line 538 Debugged program terminated. Use q to quit or R to restart, use o inhibit_exit to avoid stopping after program termination, h q, h R or h o to get additional info. DB<1> q This is a Koha 3.2008000 In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. Any idea with this ? Thanks for read this, -Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry at opengeek.cl Thu Apr 28 05:05:19 2016 From: larry at opengeek.cl (Larry Letelier) Date: Thu, 28 Apr 2016 00:05:19 -0300 Subject: [Koha-devel] Invalid local time for date in time zone: America/Santiago In-Reply-To: <018201d1a0f9$28a3a850$79eaf8f0$@prosentient.com.au> References: <018201d1a0f9$28a3a850$79eaf8f0$@prosentient.com.au> Message-ID: Hi David, Thanks for you reply, yes your are right, Chile abolished dst, we have a minister with many earthquakes in him head. So, Here is the ?perl -d overdue_notices.pl -t" using "n": http://pastebin.com/ZxHkNCK3 If i run again : perl overdue_notices.pl -t Invalid local time for date in time zone: America/Santiago Thanks in advance guys, *-- Larry Letelier N.* *F: **+56 2 3205 2737* *F: **+56 9 7589 6842* 2016-04-27 23:53 GMT-03:00 David Cook : > Oh, that?s interesting. > > > > I?ve seen this happen on other Perl projects during daylight savings time > changes. > > > > For instance, try the following Perl code: > > > > use DateTime; > > my $dt = DateTime->new( > > year => 2015, > > month => 10, > > day => 4, > > hour => 2, > > minute => 0, > > second => 0, > > time_zone => 'Australia/Sydney', > > ); > > > > You?ll get the message: > > > > ?Invalid local time for date in time zone: Australia/Sydney? > > > > If I recall correctly, it?s because 4 October 2015 2:00am Australia/Sydney > didn?t exist. When that time was reached, the clock actually skipped > forward, and it became 4 October 2015 3:00am Australia/Sydney. In effect, > local time went from 1:59:59 to 3:00:00. 2:00:00 through 2:59:59 never > existed. Fascinating, no? > > > > Wikipedia says that Chile stopped observing DST in 2015: > https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_Americas#Chile. > However, I?m guessing that perhaps your server/the Perl module doesn?t know > that? > > > > ?Chile currently observes Daylight Saving Time (DST). Instead of turning > the clocks back one hour on Sunday, April 26, 2015 as previously planned, > the Chilean Government has decided to make no further changes to the clock > in future years.? ( > http://www.timeanddate.com/news/time/chile-abolishes-dst-2015.html). > > > > Hmm? I don?t know what date is the problem? > > > > Could you run ?perl -d overdue_notices.pl -t" again, but use ?n? instead > of ?c?? That way, you?ll be able to see what exact call is generating this > error. > > > > I?m guessing it might be one of the lines: > > > > my $today = DateTime->now(time_zone => C4::Context->tz ); > > > > But that?s just a guess. What happens if you try running your overdues > again? You might have had the misfortune of the overdues just running at > the wrong time on the wrong day. > > > > Curious to hear how you go! > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* koha-devel-bounces at lists.koha-community.org [mailto: > koha-devel-bounces at lists.koha-community.org] *On Behalf Of *Larry Letelier > *Sent:* Wednesday, 27 April 2016 3:09 PM > *To:* koha-devel at lists.koha-community.org > *Subject:* [Koha-devel] Invalid local time for date in time zone: > America/Santiago > > > > Hi people, > > > > We have a 'little' issue with the overdue aka notifications process. > > > > # pwd > > /usr/share/koha/bin/cronjobs > > > > # ./overdue_notices.pl -t > > Invalid local time for date in time zone: America/Santiago > > > > perl -d overdue_notices.pl -t > > > > Loading DB routines from perl5db.pl version 1.33 > > Editor support available. > > > > Enter h or `h h' for help, or `man perldebug' for more help. > > > > main::(overdue_notices.pl:278): my $dbh = C4::Context->dbh(); > > DB<1> c > > > > Invalid local time for date in time zone: America/Santiago > > > > at /usr/share/perl5/DateTime/TimeZone.pm line 198 > > > DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'local', 'DateTime=HASH(0x617e938)') called at > /usr/share/perl5/DateTime/TimeZone.pm line 157 > > > DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 > > DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') > called at /usr/lib/perl5/DateTime.pm line 375 > > DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at > /usr/lib/perl5/DateTime.pm line 263 > > DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, > 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at > /usr/lib/perl5/DateTime.pm line 299 > > DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, > 'minute', 0, 'second', 0, 'month', 9, ...) called at > /usr/lib/perl5/DateTime.pm line 1933 > > DateTime::truncate(undef, 'to', 'day') called at > /usr/share/koha/lib/Koha/Calendar.pm line 214 > > Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm > line 290 > > Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at > overdue_notices.pl line 538 > > Debugged program terminated. Use q to quit or R to restart, > > use o inhibit_exit to avoid stopping after program termination, > > h q, h R or h o to get additional info. > > DB<1> q > > > > This is a Koha 3.2008000 > > > > In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. > > > > > > Any idea with this ? > > > > Thanks for read this, > > -Larry > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry at opengeek.cl Thu Apr 28 05:40:42 2016 From: larry at opengeek.cl (Larry Letelier) Date: Thu, 28 Apr 2016 00:40:42 -0300 Subject: [Koha-devel] Invalid local time for date in time zone: America/Santiago In-Reply-To: <018d01d1a0ff$019ac580$04d05080$@prosentient.com.au> References: <018201d1a0f9$28a3a850$79eaf8f0$@prosentient.com.au> <018d01d1a0ff$019ac580$04d05080$@prosentient.com.au> Message-ID: David, I will review the data on date_due field. Thanks!! for your time ! LOL time.. ;-) tomorrow ?--Larry 2016-04-28 0:35 GMT-03:00 David Cook : > Hi Larry, > > > > I find time fascinating, so happy to help : ). > > > > Thanks for that pastebin. That?s really helpful. > > > > We can see the problem is with the following call: > > > > $calendar->days_between( dt_from_string($data->{date_due}),$date_to_run ); > > > > If I follow correctly, $date_to_run should be the time when you run the > script in America/Santiago time. > > > > $data->{date_due} will be from the database? probably the issues table I > think? and I think that?s looking OK, since the following line appears in > the debugger: > > > > Koha::Calendar::days_between('Koha::Calendar=HASH(0x65dcf80)', > 'DateTime=HASH(0x6507b38)', 'DateTime=HASH(0x64e7848)') > > > > We?d have an error earlier if those dates were the ones causing problems? > so I think they?re OK since they?ve been created into objects as evidenced > above. > > > > However? 'DateTime=HASH(0x6507b38)' is cloned in > Koha::Calendar::days_between() and has Koha::Calendar::is_holiday() run on > it? > > > > -- > > > > I have an urgent matter now, but that?s part of the way there. I?m > thinking the problem is with the ?date_due? from one of the overdue items! > Possibly something from September if the debug message is correct? > > > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Larry Letelier [mailto:larry at opengeek.cl] > *Sent:* Thursday, 28 April 2016 1:05 PM > *To:* David Cook > *Cc:* koha-devel at lists.koha-community.org > *Subject:* Re: [Koha-devel] Invalid local time for date in time zone: > America/Santiago > > > > Hi David, > > > > Thanks for you reply, > > > > yes your are right, Chile abolished dst, we have a minister with many > earthquakes in him head. > > So, > > > > Here is the ?perl -d overdue_notices.pl -t" using "n": > > http://pastebin.com/ZxHkNCK3 > > > > If i run again : > > > > perl overdue_notices.pl -t > > Invalid local time for date in time zone: America/Santiago > > > > Thanks in advance guys, > > > > > *-- Larry Letelier N.* > > *F: **+56 2 3205 2737* > > *F: * > *+56 9 7589 6842* > > > > 2016-04-27 23:53 GMT-03:00 David Cook : > > Oh, that?s interesting. > > > > I?ve seen this happen on other Perl projects during daylight savings time > changes. > > > > For instance, try the following Perl code: > > > > use DateTime; > > my $dt = DateTime->new( > > year => 2015, > > month => 10, > > day => 4, > > hour => 2, > > minute => 0, > > second => 0, > > time_zone => 'Australia/Sydney', > > ); > > > > You?ll get the message: > > > > ?Invalid local time for date in time zone: Australia/Sydney? > > > > If I recall correctly, it?s because 4 October 2015 2:00am Australia/Sydney > didn?t exist. When that time was reached, the clock actually skipped > forward, and it became 4 October 2015 3:00am Australia/Sydney. In effect, > local time went from 1:59:59 to 3:00:00. 2:00:00 through 2:59:59 never > existed. Fascinating, no? > > > > Wikipedia says that Chile stopped observing DST in 2015: > https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_Americas#Chile. > However, I?m guessing that perhaps your server/the Perl module doesn?t know > that? > > > > ?Chile currently observes Daylight Saving Time (DST). Instead of turning > the clocks back one hour on Sunday, April 26, 2015 as previously planned, > the Chilean Government has decided to make no further changes to the clock > in future years.? ( > http://www.timeanddate.com/news/time/chile-abolishes-dst-2015.html). > > > > Hmm? I don?t know what date is the problem? > > > > Could you run ?perl -d overdue_notices.pl -t" again, but use ?n? instead > of ?c?? That way, you?ll be able to see what exact call is generating this > error. > > > > I?m guessing it might be one of the lines: > > > > my $today = DateTime->now(time_zone => C4::Context->tz ); > > > > But that?s just a guess. What happens if you try running your overdues > again? You might have had the misfortune of the overdues just running at > the wrong time on the wrong day. > > > > Curious to hear how you go! > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* koha-devel-bounces at lists.koha-community.org [mailto: > koha-devel-bounces at lists.koha-community.org] *On Behalf Of *Larry Letelier > *Sent:* Wednesday, 27 April 2016 3:09 PM > *To:* koha-devel at lists.koha-community.org > *Subject:* [Koha-devel] Invalid local time for date in time zone: > America/Santiago > > > > Hi people, > > > > We have a 'little' issue with the overdue aka notifications process. > > > > # pwd > > /usr/share/koha/bin/cronjobs > > > > # ./overdue_notices.pl -t > > Invalid local time for date in time zone: America/Santiago > > > > perl -d overdue_notices.pl -t > > > > Loading DB routines from perl5db.pl version 1.33 > > Editor support available. > > > > Enter h or `h h' for help, or `man perldebug' for more help. > > > > main::(overdue_notices.pl:278): my $dbh = C4::Context->dbh(); > > DB<1> c > > > > Invalid local time for date in time zone: America/Santiago > > > > at /usr/share/perl5/DateTime/TimeZone.pm line 198 > > > DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'local', 'DateTime=HASH(0x617e938)') called at > /usr/share/perl5/DateTime/TimeZone.pm line 157 > > > DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 > > DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') > called at /usr/lib/perl5/DateTime.pm line 375 > > DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at > /usr/lib/perl5/DateTime.pm line 263 > > DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, > 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at > /usr/lib/perl5/DateTime.pm line 299 > > DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, > 'minute', 0, 'second', 0, 'month', 9, ...) called at > /usr/lib/perl5/DateTime.pm line 1933 > > DateTime::truncate(undef, 'to', 'day') called at > /usr/share/koha/lib/Koha/Calendar.pm line 214 > > Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm > line 290 > > Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at > overdue_notices.pl line 538 > > Debugged program terminated. Use q to quit or R to restart, > > use o inhibit_exit to avoid stopping after program termination, > > h q, h R or h o to get additional info. > > DB<1> q > > > > This is a Koha 3.2008000 > > > > In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. > > > > > > Any idea with this ? > > > > Thanks for read this, > > -Larry > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri Apr 29 13:58:18 2016 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 29 Apr 2016 12:58:18 +0100 Subject: [Koha-devel] Frameworks / DB constraints In-Reply-To: References: Message-ID: Not completely, the constraint could be added anyway. 2016-04-27 15:50 GMT+01:00 Tomas Cohen Arazi : > So it's fixed. Thanks Jonathan, again :-D > > 2016-04-23 3:08 GMT-03:00 Jonathan Druart > : >> >> Just a note: From 16.05 it won't be possible to delete a framework in >> used from the interface. >> See bug 15790. >> >> 2016-04-19 15:34 GMT+01:00 Tomas Cohen Arazi : >> > Hi fellows, I noticed (in a production server) that a cataloguing >> > framework >> > was deleted by a user. This raised a problem with records that used that >> > framework: trying to look at the record's detail page ended up in a >> > fatal >> > error. >> > >> > Currently, the framework code is not a FK, so we don't enforce it at DB >> > level. A possible solution is to just add it as a FK, another option >> > would >> > be to fallback to the default framework in the relevant function. Jesse >> > proposed on IRC creating the foreign key with ON DELETE SET NULL. >> > >> > We need to fix this, so: ideas? preferences? vote? >> > >> > -- >> > Tom?s Cohen Arazi >> > Theke Solutions (http://theke.io) >> > ? +54 9351 3513384 >> > GPG: B2F3C15F >> > >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel at 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/ >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > > > > -- > Tom?s Cohen Arazi > Theke Solutions (http://theke.io) > ? +54 9351 3513384 > GPG: B2F3C15F From kohanews at gmail.com Sat Apr 30 02:42:41 2016 From: kohanews at gmail.com (kohanews) Date: Fri, 29 Apr 2016 17:42:41 -0700 Subject: [Koha-devel] Koha Community Newsletter: April 2016 Message-ID: <5723FF81.1010403@gmail.com> Fellow Koha users: The Koha Community Newsletter for April 2016 is here: https://koha-community.org/koha-community-newsletter-april-2016/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Sat Apr 30 17:13:19 2016 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Sat, 30 Apr 2016 15:13:19 +0000 Subject: [Koha-devel] Test Suite Message-ID: Thanks for some extensive pushing, Kyle and Brendan. We still have some tests failing. I resolved a few trivial ones: bug 16403, 16404, 16405, 16407 (hardcoded borrowers), 16408 16406 Context.t is a harder one (it should not fail only for not having a cache). I also tested on top of bug 16155. Note that we probably still need some DBIx updates ! With DBIx update and some of the above fixes all TestBuilder related tests pass: All tests successful. Files=69, Tests=1929, 85 wallclock secs ( 0.53 usr 0.13 sys + 75.33 cusr 5.92 csys = 81.91 CPU) Result: PASS And finally what about: Can't locate Catmandu/Importer/MARC.pm Can't locate object method "_convert_marc_to_json" Can't locate Catmandu/Store/ElasticSearch.pm Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: