From gaetan.boisson at biblibre.com Wed Feb 1 15:18:44 2017 From: gaetan.boisson at biblibre.com (Gaetan Boisson) Date: Wed, 1 Feb 2017 15:18:44 +0100 Subject: [Koha-devel] proper sorting order and search for Swedish characters and ISBN search In-Reply-To: <00da01d26c76$67a62c50$36f284f0$@prosentient.com.au> References: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com> <20161124163203.GA26313@zazou.cscnet.co.uk> <00da01d26c76$67a62c50$36f284f0$@prosentient.com.au> Message-ID: Digging this back up as we finally found a solution. And by "we" i mean Fridolin Somers, whose knowledge of ICU, zebra and indexing never ceases to amaze me! Setting the ICU locale to sv-SE was not enough it seems, because this still transliterated ?, ?, ?, ?, ? and ? to a, o, A and O. We just had to add a rule to exclude them from the transliteration: Meh, sounds easy enough now! Hopefully this will come in handy to someone. Le 12/01/2017 ? 02:51, David Cook a ?crit : > Considering the folk at IndexData are Danish, perhaps they could provide > some insight more directly. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > 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 Colin Campbell >> Sent: Friday, 25 November 2016 3:32 AM >> To: koha-devel at lists.koha-community.org >> Subject: Re: [Koha-devel] proper sorting order and search for Swedish >> characters and ISBN search >> >> On Fri, Nov 04, 2016 at 05:20:03PM +0100, Gaetan Boisson wrote: >>> Hello, >>> >>> I have been trying several things to try to sort this out, and haven't >>> found a way (yet) that would avoid ugly compromises. >>> >>> The issue is: in Swedish ?, ? and ? are separate letters. Not variants >>> of a and o. This means that searching for ? shouldn't bring up a. When >>> sorting, they belong to the very end of the alphabet, after z, not along > a and >> o. >> In ICU, setting the locale parameter to "sv" (swedish) should do this. I > cant >> seem to get this to work in yaz-icu but there are tests in the yaz code > base for >> passing locale to strings. However I'm not sure how to correctly specify > this for >> yaz the documentation is way too sketchy. >> >> Colin >> >> -- >> Colin Campbell >> Chief Software Engineer, >> PTFS Europe Limited >> Content Management and Library Solutions >> +44 (0) 800 756 6803 (phone) >> +44 (0) 7759 633626 (mobile) >> colin.campbell at ptfs-europe.com >> skype: colin_campbell2 >> >> http://www.ptfs-europe.com >> _______________________________________________ >> 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/ -- Gaetan Boisson Chef de projet biblioth?caire BibLibre +33(0)6 52 42 51 29 108 rue Breteuil 13006 Marseille gaetan.boisson at biblibre.com From marka at pobox.com Wed Feb 1 21:40:13 2017 From: marka at pobox.com (Mark Alexander) Date: Wed, 01 Feb 2017 15:40:13 -0500 Subject: [Koha-devel] Hello, and question about kohadevbox Message-ID: <1485981347-sup-729@t60p> Hi all, I'm a newbie here, and have been working on setting up a Koha git environment. The kohadevbox project looked good, so I gave it a try just now. The provisioning went fine until the koha-create step: fatal: [jessie]: FAILED! => {"changed": true, "cmd": "koha-create --create-db kohadev", "delta": "0:00:06.582852", "end": "2017-02-01 20:02:32.211551", "failed": true, "rc": 1, "start": "2017-02-01 20:02:25.628699", "stderr": "", "stdout": "Koha instance is empty, no staff user created.\nStarting Zebra server for kohadev", "stdout_lines": ["Koha instance is empty, no staff user created.", "Starting Zebra server for kohadev"], "warnings": []} I ssh'd into the VM and tried removing the kohadev instance and recreating it by hand, and it appears that koha-create returns a non-zero status, even though it appears to have been successful: vagrant at kohadevbox:~$ sudo /usr/sbin/koha-create --create-db kohadev Koha instance is empty, no staff user created. Starting Zebra server for kohadev vagrant at kohadevbox:~$ echo $? 1 vagrant at kohadevbox:~$ Is there some way I can get vagrant to ignore the non-zero result from koha-create, and restart the provisioning at the point where it left off? Thanks in advance! From katrin.fischer.83 at web.de Wed Feb 1 22:27:31 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 1 Feb 2017 22:27:31 +0100 Subject: [Koha-devel] proper sorting order and search for Swedish characters and ISBN search In-Reply-To: References: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com> <20161124163203.GA26313@zazou.cscnet.co.uk> <00da01d26c76$67a62c50$36f284f0$@prosentient.com.au> Message-ID: Thx for sharing! On 01.02.2017 15:18, Gaetan Boisson wrote: > Digging this back up as we finally found a solution. And by "we" i > mean Fridolin Somers, whose knowledge of ICU, zebra and indexing never > ceases to amaze me! > > Setting the ICU locale to sv-SE was not enough it seems, because this > still transliterated ?, ?, ?, ?, ? and ? to a, o, A and O. > > We just had to add a rule to exclude them from the transliteration: > > > > Meh, sounds easy enough now! > > Hopefully this will come in handy to someone. > > > Le 12/01/2017 ? 02:51, David Cook a ?crit : >> Considering the folk at IndexData are Danish, perhaps they could provide >> some insight more directly. >> >> David Cook >> Systems Librarian >> Prosentient Systems >> 72/330 Wattle St >> Ultimo, NSW 2007 >> Australia >> >> 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 Colin Campbell >>> Sent: Friday, 25 November 2016 3:32 AM >>> To: koha-devel at lists.koha-community.org >>> Subject: Re: [Koha-devel] proper sorting order and search for Swedish >>> characters and ISBN search >>> >>> On Fri, Nov 04, 2016 at 05:20:03PM +0100, Gaetan Boisson wrote: >>>> Hello, >>>> >>>> I have been trying several things to try to sort this out, and haven't >>>> found a way (yet) that would avoid ugly compromises. >>>> >>>> The issue is: in Swedish ?, ? and ? are separate letters. Not variants >>>> of a and o. This means that searching for ? shouldn't bring up a. When >>>> sorting, they belong to the very end of the alphabet, after z, not >>>> along >> a and >>> o. >>> In ICU, setting the locale parameter to "sv" (swedish) should do >>> this. I >> cant >>> seem to get this to work in yaz-icu but there are tests in the yaz code >> base for >>> passing locale to strings. However I'm not sure how to correctly >>> specify >> this for >>> yaz the documentation is way too sketchy. >>> >>> Colin >>> >>> -- >>> Colin Campbell >>> Chief Software Engineer, >>> PTFS Europe Limited >>> Content Management and Library Solutions >>> +44 (0) 800 756 6803 (phone) >>> +44 (0) 7759 633626 (mobile) >>> colin.campbell at ptfs-europe.com >>> skype: colin_campbell2 >>> >>> http://www.ptfs-europe.com >>> _______________________________________________ >>> 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 josef.moravec at gmail.com Wed Feb 1 23:47:55 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Wed, 01 Feb 2017 22:47:55 +0000 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: <1485981347-sup-729@t60p> References: <1485981347-sup-729@t60p> Message-ID: Hello Mark and welcome ;) kohadevbox could be very usefu for developing and testing purposes, for sure. Just try to run vagrant up --provision it should continue in provision process regards Josef st 1. 2. 2017 v 21:40 odes?latel Mark Alexander napsal: Hi all, I'm a newbie here, and have been working on setting up a Koha git environment. The kohadevbox project looked good, so I gave it a try just now. The provisioning went fine until the koha-create step: fatal: [jessie]: FAILED! => {"changed": true, "cmd": "koha-create --create-db kohadev", "delta": "0:00:06.582852", "end": "2017-02-01 20:02:32.211551", "failed": true, "rc": 1, "start": "2017-02-01 20:02:25.628699", "stderr": "", "stdout": "Koha instance is empty, no staff user created.\nStarting Zebra server for kohadev", "stdout_lines": ["Koha instance is empty, no staff user created.", "Starting Zebra server for kohadev"], "warnings": []} I ssh'd into the VM and tried removing the kohadev instance and recreating it by hand, and it appears that koha-create returns a non-zero status, even though it appears to have been successful: vagrant at kohadevbox:~$ sudo /usr/sbin/koha-create --create-db kohadev Koha instance is empty, no staff user created. Starting Zebra server for kohadev vagrant at kohadevbox:~$ echo $? 1 vagrant at kohadevbox:~$ Is there some way I can get vagrant to ignore the non-zero result from koha-create, and restart the provisioning at the point where it left off? Thanks in advance! _______________________________________________ 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 barton at bywatersolutions.com Thu Feb 2 00:14:39 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Wed, 1 Feb 2017 18:14:39 -0500 Subject: [Koha-devel] proper sorting order and search for Swedish characters and ISBN search In-Reply-To: References: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com> <20161124163203.GA26313@zazou.cscnet.co.uk> <00da01d26c76$67a62c50$36f284f0$@prosentient.com.au> Message-ID: Gaetan, I've added your entry here: https://wiki.koha-community.org/wiki/ICU_Chains_Library#Swedish Please let me know if I've made any copy/paste errors. Thanks, --Barton On Wed, Feb 1, 2017 at 9:18 AM, Gaetan Boisson wrote: > Digging this back up as we finally found a solution. And by "we" i mean > Fridolin Somers, whose knowledge of ICU, zebra and indexing never ceases to > amaze me! > > Setting the ICU locale to sv-SE was not enough it seems, because this > still transliterated ?, ?, ?, ?, ? and ? to a, o, A and O. > > We just had to add a rule to exclude them from the transliteration: > > > > Meh, sounds easy enough now! > > Hopefully this will come in handy to someone. > > > > Le 12/01/2017 ? 02:51, David Cook a ?crit : > >> Considering the folk at IndexData are Danish, perhaps they could provide >> some insight more directly. >> >> David Cook >> Systems Librarian >> Prosentient Systems >> 72/330 Wattle St >> Ultimo, NSW 2007 >> Australia >> >> 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 Colin Campbell >>> Sent: Friday, 25 November 2016 3:32 AM >>> To: koha-devel at lists.koha-community.org >>> Subject: Re: [Koha-devel] proper sorting order and search for Swedish >>> characters and ISBN search >>> >>> On Fri, Nov 04, 2016 at 05:20:03PM +0100, Gaetan Boisson wrote: >>> >>>> Hello, >>>> >>>> I have been trying several things to try to sort this out, and haven't >>>> found a way (yet) that would avoid ugly compromises. >>>> >>>> The issue is: in Swedish ?, ? and ? are separate letters. Not variants >>>> of a and o. This means that searching for ? shouldn't bring up a. When >>>> sorting, they belong to the very end of the alphabet, after z, not along >>>> >>> a and >> >>> o. >>> In ICU, setting the locale parameter to "sv" (swedish) should do this. I >>> >> cant >> >>> seem to get this to work in yaz-icu but there are tests in the yaz code >>> >> base for >> >>> passing locale to strings. However I'm not sure how to correctly specify >>> >> this for >> >>> yaz the documentation is way too sketchy. >>> >>> Colin >>> >>> -- >>> Colin Campbell >>> Chief Software Engineer, >>> PTFS Europe Limited >>> Content Management and Library Solutions >>> +44 (0) 800 756 6803 (phone) >>> +44 (0) 7759 633626 (mobile) >>> colin.campbell at ptfs-europe.com >>> skype: colin_campbell2 >>> >>> http://www.ptfs-europe.com >>> _______________________________________________ >>> 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/ >> > > -- > Gaetan Boisson > Chef de projet biblioth?caire > BibLibre > +33(0)6 52 42 51 29 > 108 rue Breteuil 13006 Marseille > gaetan.boisson at biblibre.com > > _______________________________________________ > 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 marka at pobox.com Thu Feb 2 02:08:03 2017 From: marka at pobox.com (Mark Alexander) Date: Wed, 01 Feb 2017 20:08:03 -0500 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: References: <1485981347-sup-729@t60p> Message-ID: <1485997321-sup-6723@t60p> Excerpts from Josef Moravec's message of 2017-02-01 22:47:55 +0000: > Just try to run > > vagrant up --provision Thanks. I tried that and it the system is now in a worse state with a half-installed koha-common package. There was an error in the installation of koha-common: ... Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ...", "dpkg: error processing package koha-common (--configure):", " subprocess installed post-installation script returned error exit status 1", "Errors were encountered while processing:", " koha-common[} I tried configuring the half-installed koha-common manually via ssh, in an attempt to figure out what went wrong (see below). It's a bit too much for me to understand right now. I'll wait a week and try to start from scratch again. vagrant at kohadevbox:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... dpkg: error processing package koha-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) vagrant at kohadevbox:log$ sudo dpkg --configure -D377 koha-common D000001: ensure_diversions: new, (re)loading D000001: process queue pkg koha-common:all queue.len 0 progress 1, try 1 D000040: checking dependencies of koha-common:all (- ) D000040: ok 2 msgs >><< D000040: checking Breaks Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... D000002: fork/exec /var/lib/dpkg/info/koha-common.postinst ( configure 16.12.01~git+20170201001109.692ea16f ) dpkg: error processing package koha-common (--configure): subprocess installed post-installation script returned error exit status 1 D000001: ensure_diversions: same, skipping Errors were encountered while processing: koha-common vagrant at kohadevbox:log$ sudo /var/lib/dpkg/info/koha-common.postinst Use of uninitialized value $action in string eq at /usr/share/debconf/frontend line 27. From jonathan.druart at bugs.koha-community.org Thu Feb 2 09:40:19 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 02 Feb 2017 08:40:19 +0000 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: <1485997321-sup-6723@t60p> References: <1485981347-sup-729@t60p> <1485997321-sup-6723@t60p> Message-ID: Did you try to destroy it then create a new one from scratch? :) On Thu, 2 Feb 2017 at 02:08 Mark Alexander wrote: > Excerpts from Josef Moravec's message of 2017-02-01 22:47:55 +0000: > > Just try to run > > > > vagrant up --provision > > Thanks. I tried that and it the system is now in a worse state with a > half-installed > koha-common package. There was an error in the installation of > koha-common: > > ... Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ...", > "dpkg: error processing package koha-common (--configure):", " > subprocess installed post-installation script returned error exit > status 1", "Errors were encountered while processing:", " koha-common[} > > I tried configuring the half-installed koha-common manually via ssh, > in an attempt to figure out what went wrong (see below). It's a bit > too much for me to understand right now. I'll wait a week and try to > start from scratch again. > > vagrant at kohadevbox:~$ sudo apt-get dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] y > Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... > dpkg: error processing package koha-common (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > koha-common > E: Sub-process /usr/bin/dpkg returned an error code (1) > vagrant at kohadevbox:log$ sudo dpkg --configure -D377 koha-common > D000001: ensure_diversions: new, (re)loading > D000001: process queue pkg koha-common:all queue.len 0 progress 1, try 1 > D000040: checking dependencies of koha-common:all (- ) > D000040: ok 2 msgs >><< > D000040: checking Breaks > Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... > D000002: fork/exec /var/lib/dpkg/info/koha-common.postinst ( configure > 16.12.01~git+20170201001109.692ea16f ) > dpkg: error processing package koha-common (--configure): > subprocess installed post-installation script returned error exit status 1 > D000001: ensure_diversions: same, skipping > Errors were encountered while processing: > koha-common > vagrant at kohadevbox:log$ sudo /var/lib/dpkg/info/koha-common.postinst > Use of uninitialized value $action in string eq at > /usr/share/debconf/frontend line 27. > _______________________________________________ > 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 tomascohen at gmail.com Thu Feb 2 11:23:09 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 02 Feb 2017 10:23:09 +0000 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: References: <1485981347-sup-729@t60p> <1485997321-sup-6723@t60p> Message-ID: This is due to recent changes on koha-* scripts. I'll try to fix it today. Once it fails on the instance creation you need to run $ vagrant provision And you will be fine. The instance is correctly created, but the exit status of the koha-create command seems to say otherwise. Regards El jue., 2 de feb. de 2017 5:40 AM, Jonathan Druart < jonathan.druart at bugs.koha-community.org> escribi?: > Did you try to destroy it then create a new one from scratch? :) > > > On Thu, 2 Feb 2017 at 02:08 Mark Alexander wrote: > > Excerpts from Josef Moravec's message of 2017-02-01 22:47:55 +0000: > > Just try to run > > > > vagrant up --provision > > Thanks. I tried that and it the system is now in a worse state with a > half-installed > koha-common package. There was an error in the installation of > koha-common: > > ... Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ...", > "dpkg: error processing package koha-common (--configure):", " > subprocess installed post-installation script returned error exit > status 1", "Errors were encountered while processing:", " koha-common[} > > I tried configuring the half-installed koha-common manually via ssh, > in an attempt to figure out what went wrong (see below). It's a bit > too much for me to understand right now. I'll wait a week and try to > start from scratch again. > > vagrant at kohadevbox:~$ sudo apt-get dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] y > Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... > dpkg: error processing package koha-common (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > koha-common > E: Sub-process /usr/bin/dpkg returned an error code (1) > vagrant at kohadevbox:log$ sudo dpkg --configure -D377 koha-common > D000001: ensure_diversions: new, (re)loading > D000001: process queue pkg koha-common:all queue.len 0 progress 1, try 1 > D000040: checking dependencies of koha-common:all (- ) > D000040: ok 2 msgs >><< > D000040: checking Breaks > Setting up koha-common (16.12.01~git+20170202001109.c65a151f) ... > D000002: fork/exec /var/lib/dpkg/info/koha-common.postinst ( configure > 16.12.01~git+20170201001109.692ea16f ) > dpkg: error processing package koha-common (--configure): > subprocess installed post-installation script returned error exit status 1 > D000001: ensure_diversions: same, skipping > Errors were encountered while processing: > koha-common > vagrant at kohadevbox:log$ sudo /var/lib/dpkg/info/koha-common.postinst > Use of uninitialized value $action in string eq at > /usr/share/debconf/frontend line 27. > _______________________________________________ > 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 (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From indradg at gmail.com Thu Feb 2 15:15:09 2017 From: indradg at gmail.com (Indranil Das Gupta) Date: Thu, 2 Feb 2017 19:45:09 +0530 Subject: [Koha-devel] exact purpose of items.paidfor column Message-ID: Hi all, What is the exact purpose of the items.paidfor MEDIUMTEXT field? I do see a bug filed - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12817 regards, Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg From baptiste.wojtkowski at biblibre.com Fri Feb 3 15:10:59 2017 From: baptiste.wojtkowski at biblibre.com (Baptiste Wojtkowski) Date: Fri, 3 Feb 2017 15:10:59 +0100 Subject: [Koha-devel] New Contributor Message-ID: <17aa6842-2c14-dc84-2420-de3741756e46@biblibre.com> Hello, I am Baptiste and I will work at Biblibre during 6 month (until July, 15th) . I will work at fixing bugs on koha and mana. Baptiste Wojtkowski From francois.charbonnier at inlibro.com Fri Feb 3 18:17:18 2017 From: francois.charbonnier at inlibro.com (Francois Charbonnier) Date: Fri, 3 Feb 2017 12:17:18 -0500 Subject: [Koha-devel] Need help for a new calendar (performance improvement and library opening hours) BZ17015 Message-ID: Dear community, We submitted a patch recently that would benefit many. It solves two old bug put on hold for a while (Move calculation code out of C4::Calendar) and (hourly loans doesn't know when library closed). If you a have a bit of time ahead of you to help us get it upstreamed. It will be much appreciated! When I read again the description from bugzilla, I felt that an overview of the work and its benefits will help you get involved. * *_*Short version*_ : The communinity and some of our clients noticed two issues : 1. Hour loans doesn't know when a library is closed 2. We have performance issues when checking in overdue book or managing overdue fines. We identified that both issues are related to the way Koha does date calculation. To improve and fix these issues, we developped a new calendar with a couple of new features. _The benefits of this new calendar are_ : 1. management of the libraries opening hours (new feature). 2. performance improvement when circulating items and managing fines. In particular, when checking in overdue book or managing overdue fines. 3. help to setup holidays/closed days from one year to another (new feature) To acheive this, we redesigned the calendar database table and rewrote part of the code in charge of the date calculation. We used this work to move part of the code and separate what's in charge of the calendar and what's used to do the calculation. This way, we solved two bugzilla issues opened a long time ago : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11211 (Move calculation code out of C4::Calendar) (opened by Jesse Weaver on the 2013-11-06) https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8133 (hourly loans doesn't know when library closed) (opended by Nicole C. Engard on the 2012-05-21) For now, BZ 11211 blocked BZ 8133. All features from the old calendar is available in the new calendar. The new calendar passed all the unit tests. The patch for the new calendar is here : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17015 _* *__*Long version*_ : The calendar's database table contains only rules to set whether the library is closed or not. If Koha needs a date or a range of date (was the library closed that day? how long is this book overdue? etc.), it has to be calculated using these rules. Depending on the type of transactions, how Koha does the calculation is not always efficient. For example, a return of overdue books can take as long as many seconds (for 2 months old overdues for example). We redesigned the calendar table to be able to give Koha the information it needs to do the calculation in a more efficient way. In the calendar's new table, we don't store rules anymore. Each day from the calendar is now stored (an entry for each day). For each day, we can indicate if the library is open or closed. We took this redesign opportunity to add the library opening hours as well. That way, Koha gets straight the information it needs to determine if the library is open or not, it can take into consideration the opening hours (good for hour loans and the date range calculation is simplified by using the information stored in the database. No need to calculate it based on different rules anymore. Among the patches we submitted, we have a script to benchmark checkin and checkout transactions. The benchmark of checkin is more indicative of the performance improvement. Here is an example of collected statistics. When an item is returned the day the checkout expires, the calculation time decreased of 22% (for 100 checkins, the calculation time drops from 52.2s to 40.7s). When an item is 2 months overdue and returned, the calculation time decreased of 70% (for 100 checkins, the calculation time drops from 154s to 46.6s). _How does the new calendar work_ ? Before the first use, a script will populate the new calendar table with on entry for each day of the year. This script can retreive your actual setting to keep track of your old set up. It also creates all the entries for future years. The basic set up would be : the library wants to have a 1 year overview of the calendar so they can set it up in advance. The script creates every entry in the table to be able to set up the calendar 1 year in advance. Then, another script will be scheduled to run every day. This script will add a new entry for every day spent. In this manner, Koha keeps a 1 year advance overview at all time. The advantage of this last script is to help the koha admin to set up the calendar in advance. Each time the script will add a new entry (a new day), it will check one year in the past how the same day was set up to try to determine if the library should be closed or not : - If the date is a unique holiday : the script will not keep it for the new entry. - If the date is a repeatable holiday : the script will keep it. (For example, a library closed every saturday) - If the day type was "floatting" (it's a new type of holiday) : the new entry status is "needs confirmation". Thus, when setting up the calendar, I have two options : 1. I know it's a repeatable holiday every year or very week, I choose the date type 'repeatable'. When the script add a new entry, it keeps the holiday. 2. I want to check the holiday every year to adjust the settings (for example, Easter stat holiday), I choose the new date type "floatting". Then, when the script add a new entry, it doesn't assume the library is closed but change the date status to "needs confirmation". Then I will be able to overview these "need confirmation" holidays and set them up when I get the information. The script manage the opening hours as well. It checks the previous week settings instead of the previous year. The other new feature to help setting up the calendar is in the way Koha can create holidays between two dates. When creating this range of dates, you can : - either use a specific day and copy its settings to all the dates in the range. - or use a range of dates and copy the settings of each day to each day of the new range. Besides that, the calendar keeps all its actual features. The patch for the new calendar is here : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17015 Thank you very much! Fran?ois -- Fran?ois Charbonnier, Bibl. prof. / Chef de produits T?l. : (888) 604-2627 francois.charbonnier at inLibro.com inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Sat Feb 4 14:20:00 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sat, 04 Feb 2017 13:20:00 +0000 Subject: [Koha-devel] KohaDevBox updates Message-ID: Hi everyone. I've just pushed some updates I had on my working branch for the KohaDevBox: Updates: (a) Support for setting ElasticSearch 5.1 (b) Fixes for instance creation errors Details: (a) For supporting ElasticSearch 5.1 I've removed references to '2.x' in the code (either for repository configuration or display messages). So you should now set in your vars/user.yml file either: elasticsearch_version: '5.x' elasticsearch_version: '2.x' elasticsearch_version: '1.7' for the desired ES version. (Note: the quotes are required) ES 5.1 requires higher RAM availability so I made the Vagrantfile set 4GB of RAM when KOHA_ELASTICSEARCH=1 is set in ENV when doing the 'vagrant up' command. You can tweak the Vagrantfile locally to whatever you want (lower value?). This has all been documented on the README.md file This should be enough for being able to test https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17255 If there's something missing, please file a bug in https://github.com/digibib/kohadevbox/issues/new so we take care of it. As usual, pull requests are welcome. (b) There have recently been some changes on the koha-* scripts so they don't (only) have hardcoded paths, but accept a new entry in koha-conf.xml () which specifies the place to pick the source code from. Pretty cool! But this made koha-gitify fail to set all it is needed to keep working as we did before. As a workaround I've added a fixed {{ vagrant_home_dir }}/kohaclone entry to the koha-conf-site.xml.in file we ship with KohaDevBox. Ideally, we should just add --dev-install and --dev-install-dir options to koha-create and just (probably) deprecate koha-gitify. I'm not sure what is the best solution. koha-gitify does lots of path fixes in places that are not related to koha-* scripts (zebra configuration files, koha-conf.xml itself, etc). I'm raising this so we can discuss the best way to deal with this. Having a koha-gitify-like feature baked inside Koha is not a bad idea at all! I'd like to highlight that I haven't succeeded in figuring why installing Test::DBIx::Class fails randomly. I blamed CPAN mirrors at some point because the default one was returning 'not found' when fetching the sources. But that doesn't seem to be the ONLY cause for failures. Any help on this is welcome. The way to check what's going on is to comment out that step and log into the box and cpanm manually. The most important on this regard: don't feel bad when the box fails to load because of this stuff. Remember you can 'continue' the process by reprovisioning. It is important to keep in mind that you need to do it with the same params you chose for 'vagrant up'. For example, I always do: $ KOHA_ELASTICSEARCH=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 vagrant up so, if it fails to install something (temporary network issues? the weird Test::DBIx::Class random failure?) I always do: $ KOHA_ELASTICSEARCH=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 vagrant provision No need to halt and reload the machine. I'm not sure why people are doing it, but don't. Unless you have specific reasons to do so. It will eat a couple minutes from your time with no evident advantage. Thanks for reading, and for the recent pull requests we've got. Have a great weekend! Tom?s -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From marka at pobox.com Sun Feb 5 14:04:25 2017 From: marka at pobox.com (Mark Alexander) Date: Sun, 05 Feb 2017 08:04:25 -0500 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: References: <1485981347-sup-729@t60p> <1485997321-sup-6723@t60p> Message-ID: <1486299392-sup-1177@t60p> Excerpts from Tomas Cohen Arazi's message of 2017-02-02 10:23:09 +0000: > This is due to recent changes on koha-* scripts. I'll try to fix it today. Thanks, it seems better now. I decided to start over from scratch because the koha-common package somehow got into a broken, half-installed state that I was unable to fix. I reproduced the provision steps manually in a fresh Jessie VM, so that I could take snapshots of the VM for disaster recovery, and to see exactly where failures might occur. Things went much better this time: I was able to get a gitified Koha installation up and running. But things failed when I tried to start plack using koha-plack. The failure occurred in adjust_paths_dev_install(), in /usr/share/koha/bin/koha-functions.sh, at this line: dev_install=$(xmlstarlet sel -t -v 'yazgfs/config/dev_install' /etc/koha/sites/$instancename/koha-conf.xml) There is no dev_install in my copy of koha-conf.xml, so xmlstarlet returned a non-zero exit status. Because koha-plack has a "set -e" at the top, the script exited immediately and did not start plack. From tomascohen at gmail.com Sun Feb 5 14:11:04 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sun, 05 Feb 2017 13:11:04 +0000 Subject: [Koha-devel] Hello, and question about kohadevbox In-Reply-To: <1486299392-sup-1177@t60p> References: <1485981347-sup-729@t60p> <1485997321-sup-6723@t60p> <1486299392-sup-1177@t60p> Message-ID: Try updating yo kohadevbox code $ git pull And recreating. I've manually added to kohadevbox. See my email to the list. El dom., 5 de feb. de 2017 10:04 AM, Mark Alexander escribi?: > Excerpts from Tomas Cohen Arazi's message of 2017-02-02 10:23:09 +0000: > > This is due to recent changes on koha-* scripts. I'll try to fix it > today. > > Thanks, it seems better now. > > I decided to start over from scratch because the koha-common package > somehow got into a broken, half-installed state that I was unable to fix. > > I reproduced the provision steps manually in a fresh Jessie VM, so > that I could take snapshots of the VM for disaster recovery, and to > see exactly where failures might occur. Things went much better this > time: I was able to get a gitified Koha installation up and running. > > But things failed when I tried to start plack using koha-plack. The > failure occurred in adjust_paths_dev_install(), in > /usr/share/koha/bin/koha-functions.sh, at this line: > > dev_install=$(xmlstarlet sel -t -v 'yazgfs/config/dev_install' > /etc/koha/sites/$instancename/koha-conf.xml) > > There is no dev_install in my copy of koha-conf.xml, so xmlstarlet returned > a non-zero exit status. Because koha-plack has a "set -e" at the top, > the script exited immediately and did not start plack. > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Mon Feb 6 08:36:40 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 6 Feb 2017 07:36:40 +0000 Subject: [Koha-devel] KohaDevBox updates In-Reply-To: References: Message-ID: Great, Tomas. I gave it a try this weekend. And stumbled over unknown filesystem type 'vboxsf' (needing GuestAdditions via module assistant). Sometimes a timeout on waiting for machine to boot. Still had a (partial) failure on koha-create. Added the dev_install entry ? And also a failure on Test::DBIx::Class. But getting further step by step. Note that bringing koha-gitify into the codebase would not be a bad thing. It will help us to keep them in sync which will become more important when more people use kohadevbox. Marcel Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Tomas Cohen Arazi Verzonden: zaterdag 4 februari 2017 14:20 Aan: koha-devel Onderwerp: [Koha-devel] KohaDevBox updates Hi everyone. I've just pushed some updates I had on my working branch for the KohaDevBox: Updates: (a) Support for setting ElasticSearch 5.1 (b) Fixes for instance creation errors Details: (a) For supporting ElasticSearch 5.1 I've removed references to '2.x' in the code (either for repository configuration or display messages). So you should now set in your vars/user.yml file either: elasticsearch_version: '5.x' elasticsearch_version: '2.x' elasticsearch_version: '1.7' for the desired ES version. (Note: the quotes are required) ES 5.1 requires higher RAM availability so I made the Vagrantfile set 4GB of RAM when KOHA_ELASTICSEARCH=1 is set in ENV when doing the 'vagrant up' command. You can tweak the Vagrantfile locally to whatever you want (lower value?). This has all been documented on the README.md file This should be enough for being able to test https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17255 If there's something missing, please file a bug in https://github.com/digibib/kohadevbox/issues/new so we take care of it. As usual, pull requests are welcome. (b) There have recently been some changes on the koha-* scripts so they don't (only) have hardcoded paths, but accept a new entry in koha-conf.xml () which specifies the place to pick the source code from. Pretty cool! But this made koha-gitify fail to set all it is needed to keep working as we did before. As a workaround I've added a fixed {{ vagrant_home_dir }}/kohaclone entry to the koha-conf-site.xml.in file we ship with KohaDevBox. Ideally, we should just add --dev-install and --dev-install-dir options to koha-create and just (probably) deprecate koha-gitify. I'm not sure what is the best solution. koha-gitify does lots of path fixes in places that are not related to koha-* scripts (zebra configuration files, koha-conf.xml itself, etc). I'm raising this so we can discuss the best way to deal with this. Having a koha-gitify-like feature baked inside Koha is not a bad idea at all! I'd like to highlight that I haven't succeeded in figuring why installing Test::DBIx::Class fails randomly. I blamed CPAN mirrors at some point because the default one was returning 'not found' when fetching the sources. But that doesn't seem to be the ONLY cause for failures. Any help on this is welcome. The way to check what's going on is to comment out that step and log into the box and cpanm manually. The most important on this regard: don't feel bad when the box fails to load because of this stuff. Remember you can 'continue' the process by reprovisioning. It is important to keep in mind that you need to do it with the same params you chose for 'vagrant up'. For example, I always do: $ KOHA_ELASTICSEARCH=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 vagrant up so, if it fails to install something (temporary network issues? the weird Test::DBIx::Class random failure?) I always do: $ KOHA_ELASTICSEARCH=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 vagrant provision No need to halt and reload the machine. I'm not sure why people are doing it, but don't. Unless you have specific reasons to do so. It will eat a couple minutes from your time with no evident advantage. Thanks for reading, and for the recent pull requests we've got. Have a great weekend! Tom?s -- Tom?s Cohen Arazi Theke Solutions (https://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Feb 7 03:50:15 2017 From: dcook at prosentient.com.au (David Cook) Date: Tue, 7 Feb 2017 13:50:15 +1100 Subject: [Koha-devel] Github Message-ID: <053601d280ec$e92e5290$bb8af7b0$@prosentient.com.au> Looking at Moodle's Github, I notice a line that says "mirrored from git://git.moodle.org/moodle.git" (https://github.com/moodle/moodle). I know https://github.com/Koha-Community/Koha is supposed to be a mirror of "git://git.koha-community.org/koha.git", so I was thinking that might be nice. although it seems like adding/updating that "mirrored from" is easier said than done: https://issues.apache.org/jira/browse/INFRA-9978. But I've been looking around and it seems that you might be able to turn off pull requests? Is that something folk would want to do? I've noticed other Githubs add their own little subtitle saying that it's just a mirror of another Git. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Feb 7 11:01:31 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 07 Feb 2017 10:01:31 +0000 Subject: [Koha-devel] Hea v2 Message-ID: Hi developers, I have submitted a version 2 of Hea on bug 18066. There are changes to the server code (hea-ws and hea-app) and Koha. I will need help for testing. There are screenshots on bug 18066 comment 2, and a test plan on comment 7. It would be great to get feedbacks and signoff quickly :) Cheers, Jonathan https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18066 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue Feb 7 14:38:38 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 07 Feb 2017 13:38:38 +0000 Subject: [Koha-devel] Koha development meeting reminder Message-ID: Hi All, The next Koha development meeting is on IRC tomorrow 08 February 2017 at 20:00 UTC You can see what that is in your local time here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting&iso=20170208T20 Agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_February_2017 Please make sure to add any topics you wish to discuss. See you all soon! -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at orex.es Wed Feb 8 08:13:46 2017 From: info at orex.es (Hugo Agud) Date: Wed, 8 Feb 2017 08:13:46 +0100 Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin In-Reply-To: References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com> Message-ID: Good morning There is any new on this? we have tried to install EDS plugin to Koha, but it doesn't appear on the intranet (I guess because of plack) , but there is on the plugin folder... I am going to contact ebsco, but if any body wish to share some info on it... I will pass to EBSCO Kindest Regards 2016-11-22 16:33 GMT+01:00 SUZUKI Arthur : > Some of the tricks used to integrate code from an intranet plugin on OPAC > are explained here. > > https://github.com/bywatersolutions/koha-plugin-coverflow#setup > > This "Setup" part explains quite well the Apache config modifications > needed to let users access coverflow.pl from OPAC, and why does this " > coverflow.pl" exist. > > the EDS plugin documentation lacks this information about Apache conf. > > (actually it doesn't but it is digged really deep : > https://github.com/ebsco/edsapi-koha-plugin/wiki/Apache-Setup) > > Le 22/11/2016 ? 16:12, Paul Poulain a ?crit : > >> Hi Arthur, >> >> The intranet part of the "plugin" is a plugin, so yes, it goes into the >> scope of Plack. >> >> But the eds-*.pl files (https://github.com/ebsco/edsa >> pi-koha-plugin/tree/master/Koha/Plugin/EDS/opac) don't. That's the OPAC >> part of the "plugin", that is not really a plugin >> >> >> Le 22/11/2016 ? 15:49, SUZUKI Arthur a ?crit : >> >>> Hello Paul, >>> >>> I don't know much about EDS nor Plack but I've been playing with koha >>> plugin functionality lately. >>> >>> I guess you're talking about this plugin : >>> https://github.com/ebsco/edsapi-koha-plugin >>> >>> does the koha plugin directory falls in the Plack scope? >>> >>> If koha is installed from Source, this directory is >>> "$KOHA_USERDIR/var/lib/plugins/" >>> >>> (I don't know for debian package, but probably something like >>> /var/lib/koha/plugins) >>> >>> Hope this helps. >>> >>> Arthur >>> >>> Le 22/11/2016 ? 15:17, Paul Poulain a ?crit : >>> >>>> Hello friends, >>>> >>>> We've deployed Koha 3.22, running Plack and the EDS plugin, and it >>>> appears that it does not work. We think it's because there are some .pl >>>> code that is out of plack scope, so it's not run. Is there anyone here who >>>> has some experience with koha / Plack / EDS ? >>>> >>>> (Frido will probably send a patch to Ebsco in the next days if there's >>>> no other ida) >>>> >>>> >>>> >>> >> > -- > Arthur SUZUKI > Service informatique des biblioth?ques > BIBLIOTH?QUES UNIVERSITAIRES > Universit? Jean Moulin Lyon 3 > 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 > ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr > L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon > > _______________________________________________ > 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 arthur.suzuki at univ-lyon3.fr Wed Feb 8 11:30:30 2017 From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur) Date: Wed, 8 Feb 2017 11:30:30 +0100 Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin In-Reply-To: References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com> Message-ID: <54e7dee4-ca40-8a2a-e519-f4a47ec58b6d@univ-lyon3.fr> Hello Hugo, For my plugin I had to change some things in plack.psgi file, otherwise Perl code wouldn't get executed. First add the plugins source directory to the cached perl files : my $plugins = Plack::App::CGIBin->new( root => '/home/koha/var/lib/plugins/' )->to_app; Secondly in the "builder" section of plack.psgi add a /plugins mount point: mount '/plugins' => $plugins; Then in nginx config you can add the following lines: rewrite ^/recommendations.pl$ /plugins/Koha/Plugin/Com/Liliputech/RecommenderEngine/recommendations.pl; location /plugins { include /home/koha/etc/nginx.d/plack_proxy.conf; } And it works, pffeeewww! (don't forget to change files and dir according to your installation). Now I changed the way my plugin works so as not to rely on such complex hacks though. All data generated from my plugin is now available through the "Public Report" interface, which is much more convenient I must say : https://calyx.net.au/enhancing-kohas-public-reports-feature/ If you want to check my source : https://github.com/liliputech/koharecommenderengine Hope that may help. All the best, Arthur Le 08/02/2017 ? 08:13, Hugo Agud a ?crit : > Good morning > > There is any new on this? we have tried to install EDS plugin to Koha, > but it doesn't appear on the intranet (I guess because of plack) , but > there is on the plugin folder... I am going to contact ebsco, but if > any body wish to share some info on it... I will pass to EBSCO > > Kindest Regards > > 2016-11-22 16:33 GMT+01:00 SUZUKI Arthur >: > > Some of the tricks used to integrate code from an intranet plugin > on OPAC are explained here. > > https://github.com/bywatersolutions/koha-plugin-coverflow#setup > > > This "Setup" part explains quite well the Apache config > modifications needed to let users access coverflow.pl > from OPAC, and why does this "coverflow.pl > " exist. > > the EDS plugin documentation lacks this information about Apache conf. > > (actually it doesn't but it is digged really deep : > https://github.com/ebsco/edsapi-koha-plugin/wiki/Apache-Setup > ) > > Le 22/11/2016 ? 16:12, Paul Poulain a ?crit : > > Hi Arthur, > > The intranet part of the "plugin" is a plugin, so yes, it goes > into the scope of Plack. > > But the eds-*.pl files > (https://github.com/ebsco/edsapi-koha-plugin/tree/master/Koha/Plugin/EDS/opac > ) > don't. That's the OPAC part of the "plugin", that is not > really a plugin > > > Le 22/11/2016 ? 15:49, SUZUKI Arthur a ?crit : > > Hello Paul, > > I don't know much about EDS nor Plack but I've been > playing with koha plugin functionality lately. > > I guess you're talking about this plugin : > https://github.com/ebsco/edsapi-koha-plugin > > > does the koha plugin directory falls in the Plack scope? > > If koha is installed from Source, this directory is > "$KOHA_USERDIR/var/lib/plugins/" > > (I don't know for debian package, but probably something > like /var/lib/koha/plugins) > > Hope this helps. > > Arthur > > Le 22/11/2016 ? 15:17, Paul Poulain a ?crit : > > Hello friends, > > We've deployed Koha 3.22, running Plack and the EDS > plugin, and it appears that it does not work. We think > it's because there are some .pl code that is out of > plack scope, so it's not run. Is there anyone here who > has some experience with koha / Plack / EDS ? > > (Frido will probably send a patch to Ebsco in the next > days if there's no other ida) > > > > > > -- > Arthur SUZUKI > Service informatique des biblioth?ques > BIBLIOTH?QUES UNIVERSITAIRES > Universit? Jean Moulin Lyon 3 > 6 Cours Albert Thomas - B.P. 8242 ? 69355 > Lyon Cedex 08 > ligne directe : +33 (0)4 78 78 79 16 > | http://bu.univ-lyon3.fr > L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon > > _______________________________________________ > 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/ > > > -- Arthur SUZUKI Service informatique des biblioth?ques BIBLIOTH?QUES UNIVERSITAIRES Universit? Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed Feb 8 11:39:28 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 08 Feb 2017 10:39:28 +0000 Subject: [Koha-devel] What's on in koha-devel #10 Message-ID: Hello librarians and developers, Several interesting initiatives emerged in this beginning of year 2017. Lot of things need to ready for the next stable release in March. If you have some spare time, do not hesitate to get involve and make things you love moving forward :) = Catalyst academy = Let's start with the yearly Catalyst academy week. The Open Source Academy is a Catalyst initiative designed to provide training & work experience in open source development for young New Zealand technologists. We got signoffs and patches from 6 students (Zoe, Luke, Grace, Karen, Caitlin and Emma) and they all got at least 1 patch pushed into master this week [1]. Congrats to all of them! Looking forward the next one :) = Move marcxml out of the biblioitems table (bug 17196) = Well, that's it, it's in and will be in 17.05! I'd like to specially thanks Mason, Josef, Zeno, Nick and Marcel to have been involved in the testing and QA process of this important change. It will offer us more flexibility in the future for new developments as well as bring us performance boost in few areas. Since that change will break lot of reports, I have worked on a way to automatically detect the problematic reports and automagically convert it using the new columns. I think we really need it for the next major release, take a look at bug 17898 (Add a way to automatically convert SQL reports). = Dashboard = I have submitted a pull request which has been quickly merged (thanks Chris!). The dashboard (http://dashboard.koha-community.org) now displays a "Overall bug tracker health status" with the number of blocker, critical and major bug reports opened over the last 60 days. If you want to quickly know which are the hot patches waiting for you, just click on the link and you will get the bug list. =Bootstrap 3= The bootstrap library used for the staff interface has been upgraded to the version 3.3.7. Lot of work has been done by Josef and Owen to make the staff interface looking awesome. Elements like buttons, links, icons, modal windows have been homogenised. Some work are still in progress but the big step has been done. You can take a look at the depend patches of bug 17873 (Make all buttons Bootstrap styled) if you want easy signoffs. = Hea - Share your statistics with the community = Few days ago I have submitted patches for a proposition of what could be Hea version 2. If you want more informations, take a look at bug 18066 and especially the comment 2 about screenshots. Developers are very welcome to test, and librarians to give their opinion on what could be missing to make Hea better. I would also like to get help from a native English speaker to add more informations on the administration page to explain better what happens (and what will not happen!) when an option or another is set. = Refactoring = Lot of refactoring bug reports are waiting for testers and QAers. Everything has been stuck for the last month. I really would like to see more attention on these bugs, to continue the work in progress. To know how you can help, take a look at this graph: https://bugs.koha-community.org/bugzilla3/showdependencygraph.cgi?id=15449 Zoom out, zoom out, once again. If you are a signoffer, pick the orange boxes, if you are a QAer, look at the yellow ones. = Template Toolkit syntax for notices = This is certainly one of the most important area if you want to help us getting this in for the next release. These are quite lot of things to do to get something ready. First we want to make sure we will not get regression using the TT syntax. To prove that, I have opened an omnibus (see bug 17961 and related bugs - TT syntax for notices - Prove we have an equivalent for our historical custom syntax). A huge amount of tests are provided to prepare the ground and safe our backs for later. It is, in my opinion, the important part of the work. All of these patches are easy to test. To ease the migration for libraries, I have developed an interface to automagically convert the notices from the historical syntax to the TT syntax. You can take a look at bug 17981 and bug 18007 for this interface change. To test *all* of this stack change, you just need to checkout the remote branch from my github repository [2] Screenshot of the convert interface: https://pageshot.net/pVRqSxln4A9cqjtM/pro.kohadev.vm = Authority merge bugs = Marcel is reworking the authority merge feature. It is quite buggy and the code is hard to maintain currently. You can take a look at bug 17908 (Authority merge omnibus) and all related bug reports to help and/or follow the progress. The next general IRC meeting is on March 1st, 20 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_1_March_2017 The next dev IRC meeting is today (!) at 20 UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_February_2017 Hope to see your there! Cheers, Jonathan [1] https://wiki.koha-community.org/wiki/Catalyst_Academy [2] https://github.com/joubu/Koha/tree/bug_17981 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed Feb 8 16:13:25 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 08 Feb 2017 15:13:25 +0000 Subject: [Koha-devel] What's on in koha-devel #10 In-Reply-To: References: Message-ID: Erratum: Next major release will be in May, not March :) On Wed, 8 Feb 2017 at 11:39 Jonathan Druart < jonathan.druart at bugs.koha-community.org> wrote: > Hello librarians and developers, > > Several interesting initiatives emerged in this beginning of year 2017. > Lot of things need to ready for the next stable release in March. > If you have some spare time, do not hesitate to get involve and make > things you love moving forward :) > > = Catalyst academy = > Let's start with the yearly Catalyst academy week. > The Open Source Academy is a Catalyst initiative designed to provide > training & work experience in open source development for young New Zealand > technologists. > We got signoffs and patches from 6 students (Zoe, Luke, Grace, Karen, > Caitlin and Emma) and they all got at least 1 patch pushed into master this > week [1]. > Congrats to all of them! Looking forward the next one :) > > = Move marcxml out of the biblioitems table (bug 17196) = > Well, that's it, it's in and will be in 17.05! > I'd like to specially thanks Mason, Josef, Zeno, Nick and Marcel to have > been involved in the testing and QA process of this important change. > It will offer us more flexibility in the future for new developments as > well as bring us performance boost in few areas. > > Since that change will break lot of reports, I have worked on a way to > automatically detect the problematic reports and automagically convert it > using the new columns. > I think we really need it for the next major release, take a look at bug > 17898 (Add a way to automatically convert SQL reports). > > = Dashboard = > I have submitted a pull request which has been quickly merged (thanks > Chris!). > The dashboard (http://dashboard.koha-community.org) now displays a > "Overall bug tracker health status" with the number of blocker, critical > and major bug reports opened over the last 60 days. If you want to > quickly know which are the hot patches waiting for you, just click on the > link and you will get the bug list. > > =Bootstrap 3= > The bootstrap library used for the staff interface has been upgraded to > the version 3.3.7. > Lot of work has been done by Josef and Owen to make the staff interface > looking awesome. > Elements like buttons, links, icons, modal windows have been homogenised. > Some work are still in progress but the big step has been done. > You can take a look at the depend patches of bug 17873 (Make all buttons > Bootstrap styled) if you want easy signoffs. > > = Hea - Share your statistics with the community = > Few days ago I have submitted patches for a proposition of what could be > Hea version 2. > If you want more informations, take a look at bug 18066 and especially the > comment 2 about screenshots. > Developers are very welcome to test, and librarians to give their opinion > on what could be missing to make Hea better. > I would also like to get help from a native English speaker to add more > informations on the administration page to explain better what happens (and > what will not happen!) when an option or another is set. > > = Refactoring = > Lot of refactoring bug reports are waiting for testers and QAers. > Everything has been stuck for the last month. > I really would like to see more attention on these bugs, to continue the > work in progress. > To know how you can help, take a look at this graph: > https://bugs.koha-community.org/bugzilla3/showdependencygraph.cgi?id=15449 > Zoom out, zoom out, once again. If you are a signoffer, pick the orange > boxes, if you are a QAer, look at the yellow ones. > > = Template Toolkit syntax for notices = > This is certainly one of the most important area if you want to help us > getting this in for the next release. > These are quite lot of things to do to get something ready. First we want > to make sure we will not get regression using the TT syntax. > To prove that, I have opened an omnibus (see bug 17961 and related bugs - > TT syntax for notices - Prove we have an equivalent for our historical > custom syntax). A huge amount of tests are provided to prepare the ground > and safe our backs for later. It is, in my opinion, the important part of > the work. > All of these patches are easy to test. > To ease the migration for libraries, I have developed an interface to > automagically convert the notices from the historical syntax to the TT > syntax. > You can take a look at bug 17981 and bug 18007 for this interface change. > To test *all* of this stack change, you just need to checkout the remote > branch from my github repository [2] > Screenshot of the convert interface: > https://pageshot.net/pVRqSxln4A9cqjtM/pro.kohadev.vm > > = Authority merge bugs = > Marcel is reworking the authority merge feature. It is quite buggy and the > code is hard to maintain currently. > You can take a look at bug 17908 (Authority merge omnibus) and all > related bug reports to help and/or follow the progress. > > > The next general IRC meeting is on March 1st, 20 UTC. > https://wiki.koha-community.org/wiki/General_IRC_meeting_1_March_2017 > > The next dev IRC meeting is today (!) at 20 UTC > > https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_February_2017 > > Hope to see your there! > > Cheers, > Jonathan > > [1] https://wiki.koha-community.org/wiki/Catalyst_Academy > [2] https://github.com/joubu/Koha/tree/bug_17981 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From liz at catalyst.net.nz Thu Feb 9 02:04:25 2017 From: liz at catalyst.net.nz (Liz Rea) Date: Thu, 9 Feb 2017 14:04:25 +1300 Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin In-Reply-To: References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com> Message-ID: <5eb02356-0a4d-28d0-45dc-79096f491c63@catalyst.net.nz> The problem here is that the plugin has a problem, and erroring plugins don't show up in the intranet (ask me how I know ;)) You can get around it by commenting out the use C4::Branches in EDS.pm, but the search still may not work. We have filed a bug with EBSCO about it (well, Magnus did one on Github and we Catalyst emailed them about it). https://github.com/ebsco/edsapi-koha-plugin/issues/15 There is also a bug to improve error handling for the plugins: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17461 It's not perfect but it is a LOT better than what happens now. Cheers, Liz, of the still sore forehead. On 08/02/17 20:13, Hugo Agud wrote: > Good morning > > There is any new on this? we have tried to install EDS plugin to Koha, but > it doesn't appear on the intranet (I guess because of plack) , but there is > on the plugin folder... I am going to contact ebsco, but if any body wish > to share some info on it... I will pass to EBSCO > > Kindest Regards > > 2016-11-22 16:33 GMT+01:00 SUZUKI Arthur : > >> Some of the tricks used to integrate code from an intranet plugin on OPAC >> are explained here. >> >> https://github.com/bywatersolutions/koha-plugin-coverflow#setup >> >> This "Setup" part explains quite well the Apache config modifications >> needed to let users access coverflow.pl from OPAC, and why does this " >> coverflow.pl" exist. >> >> the EDS plugin documentation lacks this information about Apache conf. >> >> (actually it doesn't but it is digged really deep : >> https://github.com/ebsco/edsapi-koha-plugin/wiki/Apache-Setup) >> >> Le 22/11/2016 ? 16:12, Paul Poulain a ?crit : >> >>> Hi Arthur, >>> >>> The intranet part of the "plugin" is a plugin, so yes, it goes into the >>> scope of Plack. >>> >>> But the eds-*.pl files (https://github.com/ebsco/edsa >>> pi-koha-plugin/tree/master/Koha/Plugin/EDS/opac) don't. That's the OPAC >>> part of the "plugin", that is not really a plugin >>> >>> >>> Le 22/11/2016 ? 15:49, SUZUKI Arthur a ?crit : >>> >>>> Hello Paul, >>>> >>>> I don't know much about EDS nor Plack but I've been playing with koha >>>> plugin functionality lately. >>>> >>>> I guess you're talking about this plugin : >>>> https://github.com/ebsco/edsapi-koha-plugin >>>> >>>> does the koha plugin directory falls in the Plack scope? >>>> >>>> If koha is installed from Source, this directory is >>>> "$KOHA_USERDIR/var/lib/plugins/" >>>> >>>> (I don't know for debian package, but probably something like >>>> /var/lib/koha/plugins) >>>> >>>> Hope this helps. >>>> >>>> Arthur >>>> >>>> Le 22/11/2016 ? 15:17, Paul Poulain a ?crit : >>>> >>>>> Hello friends, >>>>> >>>>> We've deployed Koha 3.22, running Plack and the EDS plugin, and it >>>>> appears that it does not work. We think it's because there are some .pl >>>>> code that is out of plack scope, so it's not run. Is there anyone here who >>>>> has some experience with koha / Plack / EDS ? >>>>> >>>>> (Frido will probably send a patch to Ebsco in the next days if there's >>>>> no other ida) >>>>> >>>>> >>>>> >> -- >> Arthur SUZUKI >> Service informatique des biblioth?ques >> BIBLIOTH?QUES UNIVERSITAIRES >> Universit? Jean Moulin Lyon 3 >> 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 >> ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr >> L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon >> >> _______________________________________________ >> 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/ -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: OpenPGP digital signature URL: From magnus at enger.priv.no Mon Feb 13 11:36:08 2017 From: magnus at enger.priv.no (Magnus Enger) Date: Mon, 13 Feb 2017 11:36:08 +0100 Subject: [Koha-devel] Sending email on behalf of customers Message-ID: Hi! I run Koha for several customers, and a number of them have email enabled. The sender of these emails is set to be the email of the library in question, e.g. library at example.org. Now, the problem is that services like GMail and Hotmail are not accepting these emails, because they see them as non-legitimate, in the sense that they are sent from some random server somewhere on the internet, that is not in any way associated with example.org. And they are right, of course! I *am* sending email on behalf of libraries from some random server on the internet. So, the question is: how to get around this? I see two possibilities: 1. Work with the sysadmins of the organizations of each library and have them include my servers in their "published lists of trusted servers" (I am thinking of stuff like SPF, PTR, OpenDKIM etc - I have not gotten my head around all of the details.) This would entail talking to lots of different sysadmins (if there is one) at lots of different organizations = lots of work... 2. So I was thinking about a second optoin - paying my way out, through some service like the ones listed here: https://zapier.com/learn/email-marketing/best-transactional-email-sending-services/ My thinking is that GMail and Hotmail would "think" like "hm, this email says it comes from example.org, but it originated from some random server. BUT it was sent through ServiceX, which you have to pay to use, so it is probably legit". But I have no idea if GMail and Hotmail works like that at all. Does anyone else have a clue about this? Or some other way to solve the problem? Best regards, Magnus Enger Libriotech From M.de.Rooy at rijksmuseum.nl Mon Feb 13 11:44:28 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 13 Feb 2017 10:44:28 +0000 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: As a workaround: Use real library email address in ReplyToDefault and ReturnpathDefault. Use the real server domain in the From address like library@[yourserver] Should cover most cases. As a fallback, autoforward eventual replies at the From address to the library. (Now you are only "in offense" here..) -----Oorspronkelijk bericht----- Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Magnus Enger Verzonden: maandag 13 februari 2017 11:36 Aan: koha-devel at lists.koha-community.org Onderwerp: [Koha-devel] Sending email on behalf of customers Hi! I run Koha for several customers, and a number of them have email enabled. The sender of these emails is set to be the email of the library in question, e.g. library at example.org. Now, the problem is that services like GMail and Hotmail are not accepting these emails, because they see them as non-legitimate, in the sense that they are sent from some random server somewhere on the internet, that is not in any way associated with example.org. And they are right, of course! I *am* sending email on behalf of libraries from some random server on the internet. So, the question is: how to get around this? I see two possibilities: 1. Work with the sysadmins of the organizations of each library and have them include my servers in their "published lists of trusted servers" (I am thinking of stuff like SPF, PTR, OpenDKIM etc - I have not gotten my head around all of the details.) This would entail talking to lots of different sysadmins (if there is one) at lots of different organizations = lots of work... 2. So I was thinking about a second optoin - paying my way out, through some service like the ones listed here: https://zapier.com/learn/email-marketing/best-transactional-email-sending-services/ My thinking is that GMail and Hotmail would "think" like "hm, this email says it comes from example.org, but it originated from some random server. BUT it was sent through ServiceX, which you have to pay to use, so it is probably legit". But I have no idea if GMail and Hotmail works like that at all. Does anyone else have a clue about this? Or some other way to solve the problem? Best regards, Magnus Enger Libriotech _______________________________________________ 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 magnus at enger.priv.no Mon Feb 13 13:23:14 2017 From: magnus at enger.priv.no (Magnus Enger) Date: Mon, 13 Feb 2017 13:23:14 +0100 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: Thanks Marcel! I'll definitely give this a try! On 13 February 2017 at 11:44, Marcel de Rooy wrote: > As a workaround: Use real library email address in ReplyToDefault and ReturnpathDefault. > Use the real server domain in the From address like library@[yourserver] My server is available at something like myserver.libriotech.no. Should KohaAdminEmailAddress (which is used for From by default) be library at myserver.libriotech.no or just library at libriotech.no? Best regards, Magnus From eric.begin at inLibro.com Mon Feb 13 13:40:29 2017 From: eric.begin at inLibro.com (=?UTF-8?Q?Eric_B=c3=a9gin?=) Date: Mon, 13 Feb 2017 07:40:29 -0500 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: Hi Magnus, We had this issue too and the way to solve it is that your customer's server must "announced" that your Koha server can send email it their behalf. There is usually 2 ways to do so (you must do both) *SPF - Sender Policy Framework* *DKIM - DomainKeys Identified Mail* Digital Ocean has a good guide on how to do this : https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy If you need additional help, Charles, on our team, is the one to contact ;-) Eric On 2017-02-13 07:23, Magnus Enger wrote: > Thanks Marcel! > > I'll definitely give this a try! > > On 13 February 2017 at 11:44, Marcel de Rooy wrote: >> As a workaround: Use real library email address in ReplyToDefault and ReturnpathDefault. >> Use the real server domain in the From address like library@[yourserver] > My server is available at something like myserver.libriotech.no. > Should KohaAdminEmailAddress (which is used for From by default) be > library at myserver.libriotech.no or just library at libriotech.no? > > Best regards, > Magnus > _______________________________________________ > 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 Mon Feb 13 13:40:47 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 13 Feb 2017 12:40:47 +0000 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: > My server is available at something like myserver.libriotech.no. > Should KohaAdminEmailAddress (which is used for From by default) be library at myserver.libriotech.no or just library at libriotech.no? Depends on your exact configuration. Both domains may go the same ip address. Also check your reverse dns. When I check via mxtoolbox.com I do not get a response on myserver.libriotech.no But I cannot smtp check libriotech.no either. From arthur.suzuki at univ-lyon3.fr Mon Feb 13 16:50:30 2017 From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur) Date: Mon, 13 Feb 2017 16:50:30 +0100 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: It has nothing to do with SPF, DKIM and such gadget (though it may help). Google wants your mail host to have consistent reverse-dns records (ptr). Which means : host [your ip address] should gives such results : Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: [your ip address].in-addr.arpa domain name pointer [your mailhost fqdn] Google's mail servers are really quite a pain to mail to. Also beware if your mailhost has ipv6 enable, the reverse dns record should be consistent for ipv6 too. Le 13/02/2017 ? 13:40, Marcel de Rooy a ?crit : >> My server is available at something like myserver.libriotech.no. >> Should KohaAdminEmailAddress (which is used for From by default) be library at myserver.libriotech.no or just library at libriotech.no? > Depends on your exact configuration. Both domains may go the same ip address. > Also check your reverse dns. > When I check via mxtoolbox.com I do not get a response on myserver.libriotech.no > But I cannot smtp check libriotech.no either. > > _______________________________________________ > 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/ -- Arthur SUZUKI Service informatique des biblioth?ques BIBLIOTH?QUES UNIVERSITAIRES Universit? Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon From arthur.suzuki at univ-lyon3.fr Mon Feb 13 18:56:54 2017 From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur) Date: Mon, 13 Feb 2017 18:56:54 +0100 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: Erratum : At least SPF is indeed needed so as to be able to send mail for a domain and being recognized as legitimate user. Otherwise mail is accepted by Gmail/Hotmail/etc but thrown to the Spam folder. Sorry for my mistake and good luck to you. Arthur Le 13 f?vrier 2017 16:50:30 UTC+01:00, SUZUKI Arthur a ?crit : >It has nothing to do with SPF, DKIM and such gadget (though it may >help). > >Google wants your mail host to have consistent reverse-dns records >(ptr). > >Which means : > >host [your ip address] > >should gives such results : > >Using domain server: >Name: 8.8.8.8 >Address: 8.8.8.8#53 >Aliases: > >[your ip address].in-addr.arpa domain name pointer [your mailhost fqdn] > >Google's mail servers are really quite a pain to mail to. >Also beware if your mailhost has ipv6 enable, the reverse dns record >should be consistent for ipv6 too. > >Le 13/02/2017 ? 13:40, Marcel de Rooy a ?crit : >>> My server is available at something like myserver.libriotech.no. >>> Should KohaAdminEmailAddress (which is used for From by default) be >library at myserver.libriotech.no or just library at libriotech.no? >> Depends on your exact configuration. Both domains may go the same ip >address. >> Also check your reverse dns. >> When I check via mxtoolbox.com I do not get a response on >myserver.libriotech.no >> But I cannot smtp check libriotech.no either. >> >> _______________________________________________ >> 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/ > >-- >Arthur SUZUKI >Service informatique des biblioth?ques >BIBLIOTH?QUES UNIVERSITAIRES >Universit? Jean Moulin Lyon 3 >6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 >ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr >L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon > >_______________________________________________ >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 michael.hafen at washk12.org Mon Feb 13 20:29:31 2017 From: michael.hafen at washk12.org (Michael Hafen) Date: Mon, 13 Feb 2017 12:29:31 -0700 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: I have a mail server specifically for sending email from Koha and other services I host, but I'm just one email domain. My point is that some of your customers may already have an email server / service you could use for sending email. On Mon, Feb 13, 2017 at 10:56 AM, SUZUKI Arthur wrote: > Erratum : > At least SPF is indeed needed so as to be able to send mail for a domain > and being recognized as legitimate user. > Otherwise mail is accepted by Gmail/Hotmail/etc but thrown to the Spam > folder. > > Sorry for my mistake and good luck to you. > Arthur > > > Le 13 f?vrier 2017 16:50:30 UTC+01:00, SUZUKI Arthur < > arthur.suzuki at univ-lyon3.fr> a ?crit : >> >> It has nothing to do with SPF, DKIM and such gadget (though it may help). >> >> Google wants your mail host to have consistent reverse-dns records (ptr). >> >> Which means : >> >> host [your ip address] >> >> should gives such results : >> >> Using domain server: >> Name: 8.8.8.8 >> Address: 8.8.8.8#53 >> Aliases: >> >> [your ip address].in-addr.arpa domain name pointer [your mailhost fqdn] >> >> Google's mail servers are really quite a pain to mail to. >> Also beware if your mailhost has ipv6 enable, the reverse dns record >> should be consistent for ipv6 too. >> >> Le 13/02/2017 ? 13:40, Marcel de Rooy a ?crit : >> >>> My server is available at something like myserver.libriotech.no. >>>> Should KohaAdminEmailAddress (which is used for From by default) be library at myserver.libriotech.no or just library at libriotech.no? >>>> >>> Depends on your exact configuration. Both domains may go the same ip address. >>> Also check your reverse dns. >>> When I check via mxtoolbox.com I do not get a response on myserver.libriotech.no >>> But I cannot smtp check libriotech.no either. >>> >>> ------------------------------ >>> >>> 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/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at orex.es Tue Feb 14 14:46:59 2017 From: info at orex.es (Hugo Agud) Date: Tue, 14 Feb 2017 14:46:59 +0100 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: Hi We experienced the same problem, we fixed it using Amazon SES, is like a certificate e-mail, it is very easy to use.. Amazon just send a verify mail to the address from you're going to send mails, and once is verified it becomes a 'certified' mail and all the major firewall, gmail allow to delivery them. Obviosusly you have to configure your mta to send mails using Amazon SES and it also have a cost, but it is quite low If you need more detailed info, just send me a mail Kindest Regatds Hugo 2017-02-13 16:50 GMT+01:00 SUZUKI Arthur : > It has nothing to do with SPF, DKIM and such gadget (though it may help). > > Google wants your mail host to have consistent reverse-dns records (ptr). > > Which means : > > host [your ip address] > > should gives such results : > > Using domain server: > Name: 8.8.8.8 > Address: 8.8.8.8#53 > Aliases: > > [your ip address].in-addr.arpa domain name pointer [your mailhost fqdn] > > Google's mail servers are really quite a pain to mail to. > Also beware if your mailhost has ipv6 enable, the reverse dns record > should be consistent for ipv6 too. > > > Le 13/02/2017 ? 13:40, Marcel de Rooy a ?crit : > >> My server is available at something like myserver.libriotech.no. >>> Should KohaAdminEmailAddress (which is used for From by default) be >>> library at myserver.libriotech.no or just library at libriotech.no? >>> >> Depends on your exact configuration. Both domains may go the same ip >> address. >> Also check your reverse dns. >> When I check via mxtoolbox.com I do not get a response on >> myserver.libriotech.no >> But I cannot smtp check libriotech.no either. >> >> _______________________________________________ >> 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/ >> > > -- > Arthur SUZUKI > Service informatique des biblioth?ques > BIBLIOTH?QUES UNIVERSITAIRES > Universit? Jean Moulin Lyon 3 > 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 > ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr > L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon > > > _______________________________________________ > 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 paul.poulain at biblibre.com Tue Feb 14 18:25:35 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 14 Feb 2017 18:25:35 +0100 Subject: [Koha-devel] Hackfest in Marseille, book your flight ! Message-ID: <6ae97ad1-2e93-0d19-ddd4-c7a8b4396a2b@biblibre.com> Hi, A reminder : the Hackfest in Marseille will take place next month, march 20 - 24. Book your flights & drop me an email (I'm hoping to officially open registrations this week) See you next month ! -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From kohanews at gmail.com Wed Feb 15 03:27:06 2017 From: kohanews at gmail.com (kohanews) Date: Tue, 14 Feb 2017 18:27:06 -0800 Subject: [Koha-devel] Call for news: February 2017 Newsletter Message-ID: <8c0c5702-1f43-21fe-5b9e-85f869f78d03@gmail.com> I'm collecting news for the February 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 From baptiste.wojtkowski at biblibre.com Wed Feb 15 16:52:57 2017 From: baptiste.wojtkowski at biblibre.com (Baptiste Wojtkowski) Date: Wed, 15 Feb 2017 16:52:57 +0100 Subject: [Koha-devel] Edit button in circulation rule Message-ID: <02445478-15de-9cd9-e8ac-00c9f9eb4c15@biblibre.com> Hello all, Is that normal that, by editing a circulation rule : 1) You can change the patron category and the Item type 2) If you do it, this will create a new rule instead of editing the old one. Kind regards Baptiste Wojtkowski From jonathan.druart at bugs.koha-community.org Wed Feb 15 17:10:29 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 15 Feb 2017 16:10:29 +0000 Subject: [Koha-devel] Edit button in circulation rule In-Reply-To: <02445478-15de-9cd9-e8ac-00c9f9eb4c15@biblibre.com> References: <02445478-15de-9cd9-e8ac-00c9f9eb4c15@biblibre.com> Message-ID: Hi Baptiste, Definitely not, it's a bug. Please open a new bug report, and ideally submit a patch to fix it :) Cheers, Jonathan On Wed, 15 Feb 2017 at 16:52 Baptiste Wojtkowski < baptiste.wojtkowski at biblibre.com> wrote: > Hello all, > > Is that normal that, by editing a circulation rule : > > 1) You can change the patron category and the Item type > 2) If you do it, this will create a new rule instead of editing the old > one. > > Kind regards > > Baptiste Wojtkowski > > _______________________________________________ > 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 magnus at enger.priv.no Thu Feb 16 08:50:38 2017 From: magnus at enger.priv.no (Magnus Enger) Date: Thu, 16 Feb 2017 08:50:38 +0100 Subject: [Koha-devel] Sending email on behalf of customers In-Reply-To: References: Message-ID: Thanks for your input, folks! Much appreciated! I will be looking more closely at your answers in the near future. I'll summarize my findings here when I have worked out a solution. Best regards, Magnus Enger Libriotech On 14 February 2017 at 14:46, Hugo Agud wrote: > Hi > > We experienced the same problem, we fixed it using Amazon SES, is like a > certificate e-mail, it is very easy to use.. Amazon just send a verify mail > to the address from you're going to send mails, and once is verified it > becomes a 'certified' mail and all the major firewall, gmail allow to > delivery them. > > Obviosusly you have to configure your mta to send mails using Amazon SES and > it also have a cost, but it is quite low > > If you need more detailed info, just send me a mail > > Kindest Regatds > Hugo > > 2017-02-13 16:50 GMT+01:00 SUZUKI Arthur : >> >> It has nothing to do with SPF, DKIM and such gadget (though it may help). >> >> Google wants your mail host to have consistent reverse-dns records (ptr). >> >> Which means : >> >> host [your ip address] >> >> should gives such results : >> >> Using domain server: >> Name: 8.8.8.8 >> Address: 8.8.8.8#53 >> Aliases: >> >> [your ip address].in-addr.arpa domain name pointer [your mailhost fqdn] >> >> Google's mail servers are really quite a pain to mail to. >> Also beware if your mailhost has ipv6 enable, the reverse dns record >> should be consistent for ipv6 too. >> >> >> Le 13/02/2017 ? 13:40, Marcel de Rooy a ?crit : >>>> >>>> My server is available at something like myserver.libriotech.no. >>>> Should KohaAdminEmailAddress (which is used for From by default) be >>>> library at myserver.libriotech.no or just library at libriotech.no? >>> >>> Depends on your exact configuration. Both domains may go the same ip >>> address. >>> Also check your reverse dns. >>> When I check via mxtoolbox.com I do not get a response on >>> myserver.libriotech.no >>> But I cannot smtp check libriotech.no either. >>> >>> _______________________________________________ >>> 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/ >> >> >> -- >> Arthur SUZUKI >> Service informatique des biblioth?ques >> BIBLIOTH?QUES UNIVERSITAIRES >> Universit? Jean Moulin Lyon 3 >> 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08 >> ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr >> L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon >> >> >> _______________________________________________ >> 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 jonathan.druart at bugs.koha-community.org Thu Feb 16 14:45:07 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 16 Feb 2017 13:45:07 +0000 Subject: [Koha-devel] Help requested - new Koha installer and onboarding tool Message-ID: Hello, As some of you may know, a lot of works have been made by Alex, Owen and Mark to provide a new Koha installer. It really looks awesome and it would be great to get it in quickly. An onboarding tool feature is added at the end of the installation process to create some mandatory data, like library, patron category, superlibrarian, etc. Everything is almost done and has been fully tested. However a big bug has been found during the QA review: some sample data files have been moved from a directory to another and the translated files have not been taken into account. Which leads to issues if you try to install Koha using a translated languages. Bug 17855 (onboarding tool) and bug 17942 (web installer style improvement) are ready (fully tested). But we need bug 18039 (move the installer files for translated languages) first. It is not easy to test everything for just one guy, so we would need one person for each language: de-DE, es-ES, fr-FR, fr-CA, , it-IT, nb-NO, pl-PL, ru-RU and uk-UA The goal is to: 1. apply 18039, then 17855 and finally 17942 (things are not clear on the bug reports, so please use my remote branch [1]) 2. Translate the template for your language 3. Try the new web installer process, using your language 4. Get amazed about how beautiful it is 5. Switch to master, update the templates 6. Select all the sample files, screenshots of the file list, DB dump 7. Switch to the new branch 8. Select all the sample files, screenshots of the file list, DB dump 9. Compare all what you can compare and make sure the behaviours before and after the patches are the same. Let me know if you have any questions. If you are using ru-RU and uk-UA, be around! These 2 directories have not been updated for ages and I am wondering if someone is using them. Cheers, Jonathan [1] https://github.com/joubu/Koha/tree/new_web_installer -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Thu Feb 16 14:57:10 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 16 Feb 2017 13:57:10 +0000 Subject: [Koha-devel] Help requested - new Koha installer and onboarding tool In-Reply-To: References: Message-ID: Maybe remove these directories if nobody takes care of them? Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Jonathan Druart Verzonden: donderdag 16 februari 2017 14:45 Aan: koha-devel at lists.koha-community.org Onderwerp: [Koha-devel] Help requested - new Koha installer and onboarding tool Hello, As some of you may know, a lot of works have been made by Alex, Owen and Mark to provide a new Koha installer. It really looks awesome and it would be great to get it in quickly. An onboarding tool feature is added at the end of the installation process to create some mandatory data, like library, patron category, superlibrarian, etc. Everything is almost done and has been fully tested. However a big bug has been found during the QA review: some sample data files have been moved from a directory to another and the translated files have not been taken into account. Which leads to issues if you try to install Koha using a translated languages. Bug 17855 (onboarding tool) and bug 17942 (web installer style improvement) are ready (fully tested). But we need bug 18039 (move the installer files for translated languages) first. It is not easy to test everything for just one guy, so we would need one person for each language: de-DE, es-ES, fr-FR, fr-CA, , it-IT, nb-NO, pl-PL, ru-RU and uk-UA The goal is to: 1. apply 18039, then 17855 and finally 17942 (things are not clear on the bug reports, so please use my remote branch [1]) 2. Translate the template for your language 3. Try the new web installer process, using your language 4. Get amazed about how beautiful it is 5. Switch to master, update the templates 6. Select all the sample files, screenshots of the file list, DB dump 7. Switch to the new branch 8. Select all the sample files, screenshots of the file list, DB dump 9. Compare all what you can compare and make sure the behaviours before and after the patches are the same. Let me know if you have any questions. If you are using ru-RU and uk-UA, be around! These 2 directories have not been updated for ages and I am wondering if someone is using them. Cheers, Jonathan [1] https://github.com/joubu/Koha/tree/new_web_installer -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Fri Feb 17 02:46:32 2017 From: info at bywatersolutions.com (Brendan Gallagher) Date: Thu, 16 Feb 2017 17:46:32 -0800 Subject: [Koha-devel] Hackfest in Marseille, book your flight ! In-Reply-To: <6ae97ad1-2e93-0d19-ddd4-c7a8b4396a2b@biblibre.com> References: <6ae97ad1-2e93-0d19-ddd4-c7a8b4396a2b@biblibre.com> Message-ID: Excellent! We have five people attending from ByWater (Me, Joy, Nick, JesseM and Michael). We are hoping to dedicate a full day to RDF (linked data) work - maybe more! I am hoping to see as many of you as we can there. We always look forward to this hackfest - such a great experience if you can afford to attend. Cheers, Brendan On Tue, Feb 14, 2017 at 9:25 AM, Paul Poulain wrote: > Hi, > > A reminder : the Hackfest in Marseille will take place next month, march > 20 - 24. > > Book your flights & drop me an email (I'm hoping to officially open > registrations this week) > > See you next month ! > > -- > Paul Poulain, Associ?-g?rant / co-owner > BibLibre, Services en logiciels libres pour les biblioth?ques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > 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 Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtompset at hotmail.com Fri Feb 17 06:06:09 2017 From: mtompset at hotmail.com (Mark Tompsett) Date: Fri, 17 Feb 2017 05:06:09 +0000 Subject: [Koha-devel] schema.koha-community.org regenerate? Message-ID: Greetings, There is a new table biblio_metadata and marcxml is gone from biblioitems. This is what caught my attention, and why I am asking if someone could regenerate the online schema. Any assistance is appreciated. [Smile] 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: wlEmoticon-smile[1].png URL: From sonia.bouis at univ-lyon3.fr Fri Feb 17 11:16:42 2017 From: sonia.bouis at univ-lyon3.fr (BOUIS Sonia) Date: Fri, 17 Feb 2017 10:16:42 +0000 Subject: [Koha-devel] Hackfest in Marseille, book your flight ! (Brendan Gallagher) In-Reply-To: References: Message-ID: <1487326604781.82617@univ-lyon3.fr> Hello Brendan, I'm happy to see you all next month :) The french association KohaLa is going to organise a workshop to work on updating marc framework with the last IFLA recommandation. I'm sure that there will be cataloging and authority specialists that will be enthousiat to see what's is going on with RDF and linked data. Cheers, Sonia Message: 3 Date: Thu, 16 Feb 2017 17:46:32 -0800 From: Brendan Gallagher To: Paul Poulain Cc: "koha-devel at lists.koha-community.org" Subject: Re: [Koha-devel] Hackfest in Marseille, book your flight ! Message-ID: Content-Type: text/plain; charset="utf-8" Excellent! We have five people attending from ByWater (Me, Joy, Nick, JesseM and Michael). We are hoping to dedicate a full day to RDF (linked data) work - maybe more! I am hoping to see as many of you as we can there. We always look forward to this hackfest - such a great experience if you can afford to attend. Cheers, Brendan On Tue, Feb 14, 2017 at 9:25 AM, Paul Poulain wrote: > Hi, > > A reminder : the Hackfest in Marseille will take place next month, march > 20 - 24. > > Book your flights & drop me an email (I'm hoping to officially open > registrations this week) > > See you next month ! > > -- > Paul Poulain, Associ?-g?rant / co-owner > BibLibre, Services en logiciels libres pour les biblioth?ques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > 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 Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ _______________________________________________ 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/ End of Koha-devel Digest, Vol 135, Issue 18 ******************************************* From mtompset at hotmail.com Sun Feb 19 05:30:47 2017 From: mtompset at hotmail.com (Mark Tompsett) Date: Sun, 19 Feb 2017 04:30:47 +0000 Subject: [Koha-devel] marc_tag_structure: Some clean up is needed? Message-ID: Greetings, I was looking to sign off bug 18111, which looks good by the way, and then I noticed that ods and xml exports were floody. So, I was pondering how to fix them, because the code is reminiscent of MARC indicators and not authorised_value or framework code. So, I put in a condition to catch things and make it not floody, but then my exports were strange. Some had ?#? and some had ?? in the authorised_values. This, of course, didn?t match the CSV patch in bug 17389. And regardless of format, I would expect the same values in the columns. So I thought, ?Why are some #?s and some blank?? Turns out marc_tag_structure has both NULL and empty strings in the authorised_value field. I thought to myself, ?Where did this get set?? I had recently dropped and recreated my database, so it had to be an installer file. Well, it turns out that installer/data/mysql/en/marcflavour/marc21/mandatory/marc21_framework_DEFAULT.sql has some NULL and some empty strings. So, first question: is that right? So, then I thought, ?Okay, so where is this # being processed?? I found it around line 1128 in C4/ImportExportFramework.pm which reads: $data = '' if ($data eq '#'); So, second question: shouldn?t an empty string have been put out in the first place? To which I thought, ?Bah! It works. It?s ugly and gross and should be refactored somehow, but I don?t know which way, so I?ll just leave it.? So, last question: if you were going to refactor, what would your plan of attack be? This includes choosing not to refactor as an option. GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sun Feb 19 23:28:47 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Sun, 19 Feb 2017 23:28:47 +0100 Subject: [Koha-devel] exact purpose of items.paidfor column In-Reply-To: References: Message-ID: <0fbfb13c-0aee-7e46-6c07-e07c9e934452@web.de> Hi Indranil, commented on the bug report. Hope this helps, Katrin On 02.02.2017 15:15, Indranil Das Gupta wrote: > Hi all, > > What is the exact purpose of the items.paidfor MEDIUMTEXT field? > > I do see a bug filed - > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12817 > > regards, > Indranil Das Gupta > L2C2 Technologies > > Phone : +91-98300-20971 > WWW : http://www.l2c2.co.in > Blog : http://blog.l2c2.co.in > IRC : indradg on irc://irc.freenode.net > Twitter : indradg > _______________________________________________ > 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 Feb 20 01:26:40 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 20 Feb 2017 11:26:40 +1100 Subject: [Koha-devel] Hackfest in Marseille, book your flight ! In-Reply-To: References: <6ae97ad1-2e93-0d19-ddd4-c7a8b4396a2b@biblibre.com> Message-ID: <0ac501d28b10$019e87f0$04db97d0$@prosentient.com.au> I wish that I could get away, but France is a bit too far for me at the moment. Here?s hoping that Andreas and Magnus can make it for the RDF day! I?ll block out those days in my calendar, so maybe I can participate a bit remotely if only with some email discussion. Really curious to see what you folk get up to with RDF! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia 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 Brendan Gallagher Sent: Friday, 17 February 2017 12:47 PM To: Paul Poulain Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Hackfest in Marseille, book your flight ! Excellent! We have five people attending from ByWater (Me, Joy, Nick, JesseM and Michael). We are hoping to dedicate a full day to RDF (linked data) work - maybe more! I am hoping to see as many of you as we can there. We always look forward to this hackfest - such a great experience if you can afford to attend. Cheers, Brendan On Tue, Feb 14, 2017 at 9:25 AM, Paul Poulain > wrote: Hi, A reminder : the Hackfest in Marseille will take place next month, march 20 - 24. Book your flights & drop me an email (I'm hoping to officially open registrations this week) See you next month ! -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries _______________________________________________ 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 Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Feb 20 02:01:41 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 20 Feb 2017 12:01:41 +1100 Subject: [Koha-devel] Task schedulers and message queues for Koha Message-ID: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> Hi all, In 2016, I worked on a Koha task scheduler for downloading and importing records via OAI-PMH. I have code which works, but it's lacking test coverage and I'm unsure that it will make it through QA and be accepted. I recall Chris Cormack suggesting I look at Gearman (http://gearman.org/) instead, and it looks pretty good at a glance, although Andreas and I had talked about having more control over the workers than Gearman seems to offer. Plus, it added another dependency to Koha where people already struggle with dependencies. Martin suggested that there were a lot of other implementations out there, but I haven't really found much else that provides everything we want out of the box. The one I have found is Celery (http://www.celeryproject.org/), which looks like exactly what I want I think, but it requires Python for its server and workers, and it requires a message broker like RabbitMQ or Redis. Lots of extra dependencies. Since my goal is to get our code into Koha, I really want to know what will work for people. Are people happy with a home grown solution? It's not really that complicated. My current version is essentially a task scheduler which forks a worker on demand when it's time to run a task (up to a configurable max of X tasks so you don't kill your server). It lets you submit tasks, tell the scheduler to start/schedule them, and you can even tell in progress tasks to stop (by having the scheduler tell the worker to stop and the worker decides where in its task it checks for stop commands from the scheduler). As I try to add test coverage and make this scheduler more palatable, I find myself thinking about the code more like Koha::Scheduler and Koha::Queue, and using the more scalable worker model used by others. The scheduler daemon would listen on a socket for tasks, it would create a Koha::Scheduler instance which would enqueue tasks to run once that task's time was met or exceeded. Now depending on the architecture. you could have a separate daemon or the same daemon with a Koha::Queue instance. It would accept tasks/messages from the scheduler, and it would dequeue tasks to available workers - which are separate processes - have previously registered against particular queues. In this way, you can have a oaipmh-download queue, oaipmh-import queue, a email-report queue, etc. I suspect that we could make use of Koha::Scheduler and Koha::Queue throughout much of Koha for doing background tasks. If we don't want to reinvent the wheel with Koha::Queue, we could use something like RabbitMQ. But I think we need *something*. I'm open to ideas. I already have the OAI-PMH download and OAI-PMH import handled. That's the easy part. Any worker can do that. The hard part is figuring out how the Koha Community will take up a task scheduler. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.ducos at biblibre.com Mon Feb 20 17:03:41 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Mon, 20 Feb 2017 16:03:41 +0000 Subject: [Koha-devel] dns hea.koha-community.org Message-ID: <4f60f37bfd0ce8b015aadcd6bfb149bf@webmail.biblibre.com> Hello. I just move hea to another server. Someone can modify the dns entry of?hea.koha-community.org to ? hea.koha-community.org.?? ?716?? ?IN?? ?A?? ?163.172.17.20 Thanks. Laurent Ducos Administrateur Syst?mes et R?seaux ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Tue Feb 21 02:35:06 2017 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Tue, 21 Feb 2017 14:35:06 +1300 Subject: [Koha-devel] dns hea.koha-community.org In-Reply-To: <4f60f37bfd0ce8b015aadcd6bfb149bf@webmail.biblibre.com> References: <4f60f37bfd0ce8b015aadcd6bfb149bf@webmail.biblibre.com> Message-ID: Done Chris On 21/02/17 05:03, Laurent Ducos wrote: > Hello. > I just move hea to another server. > Someone can modify the dns entry of hea.koha-community.org to > hea.koha-community.org. 716 IN A 163.172.17.20 > Thanks. > Laurent Ducos > Administrateur Syst?mes et R?seaux > > > > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From laurent.ducos at biblibre.com Tue Feb 21 10:05:08 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Tue, 21 Feb 2017 10:05:08 +0100 Subject: [Koha-devel] dns hea.koha-community.org In-Reply-To: References: <4f60f37bfd0ce8b015aadcd6bfb149bf@webmail.biblibre.com> Message-ID: <20170221090508.GB8335@lducos-Latitude-E5450> Le Tuesday 21 Feb 2017 ? 14:35:06 (+1300), Chris Cormack a ?crit : > Done Thanks :) > > Chris > > On 21/02/17 05:03, Laurent Ducos wrote: > > Hello. > > I just move hea to another server. > > Someone can modify the dns entry of hea.koha-community.org to > > hea.koha-community.org. 716 IN A 163.172.17.20 > > Thanks. > > Laurent Ducos > > Administrateur Syst?mes et R?seaux > > > > > > > > > > _______________________________________________ > > 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/ -- Laurent Ducos Administrateur Syst?mes et R?seaux ? BibLibre +3397477071 From alex.sassmannshausen at gmail.com Tue Feb 21 11:57:45 2017 From: alex.sassmannshausen at gmail.com (Alex Sassmannshausen) Date: Tue, 21 Feb 2017 11:57:45 +0100 Subject: [Koha-devel] Interlibrary loans module Message-ID: <87mvdf6cba.fsf@gmail.com> Hello Kohites! Andrew and I have just finished a second major revision of our proposed interlibrary loans module for Koha. The code and bug can be found at [https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317]. We believe the code has now reached the maturity it requires for wider engagement, and, more importantly, it's now reached the maturity that it should be easy to get it up and running relatively easily in your development environments. Unfortunately we cannot deploy the module using sandboxes because backends are implemented as separate code projects. And we would *love* your comments thoughts and concerns about the module if you are interested in ILL! The final comment on the bug contains basic documentation for the Module as a whole, and also some installation instructions. But for reference, I've attached the same document to this email too. Below you will find some further high-level background and a roadmap of what we would like to achieve. For now, if you're interested in this module: ? have a look at the bug, and get involved in the discussion! ? try to set up the module in your dev environment. It should work easily on dev boxes and dev installs that track master. ? let us know if you face any issues! ? start a conversation with us if you might be interested in creating a backend for your country's / organization's ILL workflows. Finally, if you don't have access to a development environment, but you would be interested in becoming involved in this project, get in touch and we might be able to provide you with access to a testing environment! Best regards, Alex Sassmannshausen PTFS Europe 1 High-level background ??????????????????????? The ILLModule aims to provide a core framework against which different ILL workflows can be implemented within Koha. It achieves this by using 2 new tables as data store, and by using an extensible backend system to create 'connectors' to ILL providers. The data store consists of the illrequests and the illrequestattributes tables. The former is a traditional table that stores essential values associated with an ILL request. The later is a key/value store, linked to a row in the former. This store can be used to store arbitrary data provided by a backend. The backends implement highly customizable workflows for several core steps in the ILL management process. At the same time, each backend can extend the core steps (called defined as the `core_status_graph` in Koha/Illrequest.pm) with their own additional steps (defined as the `status_graph` in a backend's Base.pm). Each of these steps, both core and extensions, in turn can define any number of 'stages' required to complete each individual step. Each step has access to a template include file, which can dispatch on 'stage'. This is mirrored by each step having a sub in a backend's Base.pm, which once again can dispatch on 'stage'. The subs in Base.pm have access to the full data store provided by the ILLModule; similarly the template includes have full access to Koha template features, including access to custom JS blocks through which, for instance, external APIs can be called. The main aim of this Koha module was to provide a core that is comprehensive enough to store core data to only have to implement ILL once in Koha, whilst being extensible enough so that virtually any ILL workflow can be implemented against this core. We believe we have achieved this. I'd be very interested to hear from you if you believe you have a workflow that cannot be captured by this (obviously, third party tools that do not provide API access will be virtually impossible to seamlessly integrate into Koha). 2 Roadmap ????????? The roadmap starts from the current release of code on the bugzilla issue. ? Publication of mature beta level code (21 February 2017) ? public testing ? public discussion ? dogfooding ? Augment core functionality (~ June 2017) ? add advanced configuration options for the core module ? add a standard system for configuring backends ? allow for an 'unmediated workflow' ? finalise 'generic requests' workflow ? Meet Koha QA standards (~ July 2017) ? Add unit tests to core ILLModule ? Ensure UI respects Koha standards ? Ensure Core code passes qa scripts ? Addition of Documentation ? contributing a chapter to the Koha manual ? ensure all pod information is correct and complete ? ('writing your own backend' tutorial?) ? Provide consistent error handling ? standard means through which a backend can 'throw' an error. ? replace uses of die with this standard route ? Integration into Koha core in Koha 17.11 -------------- next part -------------- Table of Contents ????????????????? 1 Change Log (since last set of patches pushed to bugzilla) .. 1.1 Core module .. 1.2 Backends ..... 1.2.1 New backend: FreeForm ..... 1.2.2 New backend: BLDSS (British Library) ..... 1.2.3 Dummy 2 Module Features .. 2.1 What is handled by the module? .. 2.2 What is not yet handled 3 Installation 4 Optional 5 Missing before inclusion in community 6 Test plan .. 6.1 Core Module (+ Dummy backend) ..... 6.1.1 Creating requests (Staff) ..... 6.1.2 Creating requests (Patrons) ..... 6.1.3 Editing requests (Staff) ..... 6.1.4 Editing requests (Patrons) ..... 6.1.5 Requesting Cancellation (Patrons) ..... 6.1.6 Confirming requests (Staff) ..... 6.1.7 Reverting requests (Staff) ..... 6.1.8 Deleting requests (Staff) ..... 6.1.9 Place request with partners (Staff) .. 6.2 BLDSS backend .. 6.3 FreeForm backend 1 Change Log (since last set of patches pushed to bugzilla) ??????????????????????????????????????????????????????????? 1.1 Core module ??????????????? ? Many improvements to general documentation in UI and configuration. ? Many improvements to the user interface. ? OPAC interface to viewing and commenting on their requests. ? OPAC interface for creating new requests with backends of choice. ? Add 'metadata' abstraction allowing backends to translate raw data from their source to user friendly content. ? Add 'custom_capability's, means by which backends can extend the workflow of the ILL module in a seamless manner. ? Add support for custom JS blocks in ILL backend template includes. ? Add generic 'backend request -> email to partners' functionality. ? Remove loads of legacy code. 1.2 Backends ???????????? 1.2.1 New backend: FreeForm ??????????????????????????? ? Allows creation of ILL requests using a manual form, which can be extended at creation time. 1.2.2 New backend: BLDSS (British Library) ?????????????????????????????????????????? ? Allows searching stock held by the british library, and placing requests against it. ? By default uses test account, which means it is useful for learning. 1.2.3 Dummy ??????????? ? Upgrade to support latest features. 2 Module Features ????????????????? ? Extensible core for handling interlibrary loan requests in Koha ? As many backends can be added as desirable ? OPAC request form as well as Intranet request form ? Intranet request management ? Ability to create items against a backend (e.g. British Library), using its advanced search features, and to then request the item from peer libraries. 2.1 What is handled by the module? ?????????????????????????????????? ? Create new requests ? Allow staff and customer notes ? Process those requests using custom workflows for backends ? Retain associations between requests and biblioitems that may be created locally ? Peer lending libraries contact management (using Koha's Organizational borrower types) ? Storage of core request information (borrower links, branch links, request status, staff and customer notes, unique identifiers) ? Storage of arbitrary data returned by backend, and display of that data. 2.2 What is not yet handled ??????????????????????????? ? Automatic processing of received ILLs (biblio + biblioitem creation) ? Integration into specialized ILL loan & reminder policies 3 Installation ?????????????? ? Apply patches (they should apply cleanly and without trouble on master) ? Run databaseupdate to generate the ILL tables. ? Copy the 'interlibrary_loans' element from '$kohaclone_root/etc/koha-conf.xml' to your active koha_conf.xml ? Update the path in 'interlibrary_loans > backend_dir' in koha_conf.xml to point to '$kohaclone_root/Koha/Illbackends' ? git clone backends into the backend directory: ????? ? cd $kohaclone_root/Koha/ && mkdir Illbackends && cd Illbackends ? git clone https://github.com/a-sassmannshausen/{Dummy,FreeForm,BLDSS} ????? ? Enable ILLModule in syspreferences 4 Optional ?????????? ? Ensure latest Koha-Conf configuration values for interlibrary_loans are set (see $kohaclone_root/etc/koha-conf.xml) ? Create peer lending libraries (by default they are expected to be part of the 'ILLLIBS' borrower category, which also needs to be created). 5 Missing before inclusion in community ??????????????????????????????????????? ? Unit tests ? Documentation (code + manual) ? Unmediated ILL Request placement workflow ? Advanced configuration ? Complete Generic Requests workflow (allow setting requests to completed in this way, allow requests to resume backend specific workflows after generic email is sent) ? Friendlier error handling. 6 Test plan ??????????? 6.1 Core Module (+ Dummy backend) ????????????????????????????????? ? Ensure the Dummy backend is installed (see [Installation]) ? Enable the ILLModule (located under Administration sysprefs) ? Create a test patron, grant them at least ILL and usual staff permissions. ? Browse to 'Home > ILL requests' (button should be visible) [Installation] See section 3 6.1.1 Creating requests (Staff) ??????????????????????????????? ? Click on the 'New ILL request' button. ? If you have multiple backends installed, select 'Dummy' ? Complete the form ? Borrowernumber must be a borrowernumber, not a cardnumber. ? You will always be shown the same 2 results ? Request one of the items ? You have now 'created' the request 6.1.2 Creating requests (Patrons) ????????????????????????????????? ? Log in to the OPAC ? Click on 'Your interlibrary loan requests' ? Click on 'Create a new request' ? If you have multiple backends installed, select 'Dummy' ? Complete the form ? As above, you will always be shown the same 2 results ? Request one of the items ? You have now 'created' the request. 6.1.3 Editing requests (Staff) ?????????????????????????????? ? From the ill-requests list, click on 'Manage request' ? Click on 'Edit request' ? Add some staff notes (or change other values) ? Click 'Submit'. 6.1.4 Editing requests (Patrons) ???????????????????????????????? ? From the patron screen, click on 'Your interlibrary loan requests' ? click on 'View' ? Enter some notes. ? Click on 'Submit modifications' 6.1.5 Requesting Cancellation (Patrons) ??????????????????????????????????????? ? From the patron screen, click on 'Your interlibrary loan requests' ? Click on 'View' ? Click on 'Request Cancellation' ? The request status should have changed ? The request can now be cancelled by staff if they consider the cancellation is still possible 6.1.6 Confirming requests (Staff) ????????????????????????????????? Once a request is created, it exists in the ILLModule. But the request has not yet been ordered from the source. To do the latter, a request must be confirmed by staff: ? From the ill-requests list, click on 'Manage request' ? Click on 'Confirm request'. ? The following process will be different for each backend. ? In the case of Dummy, a simple click on the button is sufficient. ? Other backends may take you through several screens. 6.1.7 Reverting requests (Staff) ???????????????????????????????? Once a request is confirmed it may still be possible to undo this operation. This depends on the backend used, and the policies at the source. ? From the ill-requests list, click on 'Manage request' ? Click on 'Revert request'. ? The following process will be different for each backend ? In the case of Dummy, a simple click on the button is sufficient. 6.1.8 Deleting requests (Staff) ??????????????????????????????? ? From the ill-requests list, click on 'Manage request' ? Click on 'Delete request' ? This button will only be visible when the request has not yet been confirmed. 6.1.9 Place request with partners (Staff) ????????????????????????????????????????? Rather than use the sources workflows to source a title for a specific interlibrary loan, it may be desirable to ask a friendly library whether they are able to satisfy the request. The ILLModule supports this through "Generic requests". To use this you will need to create 'Organizational patrons' to represent the partner libraries. They must be of the 'ILLLIBS' patron category (this can be changed by editing the koha-conf.xml file), which must first be created. Ensure that these patrons have email addresses! Once a few patrons have been set up: ? From the ill-requests list, click on 'Manage request' ? Click on 'Place request with partners' ? This button will only be visible if the request has not yet been confirmed. ? Complete the form ? You may select multiple partners in the select list ? You may edit the email as desired. ? Click on Send email ? If your server is correctly configured to send emails, all should have worked fine and an email should have been sent. 6.2 BLDSS backend ????????????????? A backend to place and manage requests with the British library. ? Repeat tests as above. ? The workflows will be different for: ? 'create' ? 'confirm' ? There is an additional workflow: ? 'status': retrieve the current status of the request at the British library. 6.3 FreeForm backend ???????????????????? A backend to allow arbitrary manual creation of requests using an unrestricted form of fields & values. This backend has no 'source'. As such, requests that are created need to then be 'confirmed' outside of ILLModule (or using the generic requests functionality). ? Repeat tests as above. ? The workflows will be different for: ? 'create' ? 'confirm' ? 'revert request' From info at orex.es Tue Feb 21 12:10:24 2017 From: info at orex.es (Hugo Agud) Date: Tue, 21 Feb 2017 12:10:24 +0100 Subject: [Koha-devel] Interlibrary loans module In-Reply-To: <87mvdf6cba.fsf@gmail.com> References: <87mvdf6cba.fsf@gmail.com> Message-ID: Hi Alex Wow! it sounds great.. I will try to do my best with this bug ;) Kindest Regards Hugo 2017-02-21 11:57 GMT+01:00 Alex Sassmannshausen < alex.sassmannshausen at gmail.com>: > Hello Kohites! > > Andrew and I have just finished a second major revision of our proposed > interlibrary loans module for Koha. The code and bug can be found at > [https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317]. > > We believe the code has now reached the maturity it requires for wider > engagement, and, more importantly, it's now reached the maturity that it > should be easy to get it up and running relatively easily in your > development environments. > > Unfortunately we cannot deploy the module using sandboxes because > backends are implemented as separate code projects. > > And we would *love* your comments thoughts and concerns about the module > if you are interested in ILL! > > The final comment on the bug contains basic documentation for the Module > as a whole, and also some installation instructions. But for reference, > I've attached the same document to this email too. > > Below you will find some further high-level background and a roadmap of > what we would like to achieve. > > For now, if you're interested in this module: > ? have a look at the bug, and get involved in the discussion! > ? try to set up the module in your dev environment. It should work > easily on dev boxes and dev installs that track master. > ? let us know if you face any issues! > ? start a conversation with us if you might be interested in creating a > backend for your country's / organization's ILL workflows. > > Finally, if you don't have access to a development environment, but you > would be interested in becoming involved in this project, get in touch > and we might be able to provide you with access to a testing > environment! > > Best regards, > > Alex Sassmannshausen > > PTFS Europe > > > 1 High-level background > ??????????????????????? > > The ILLModule aims to provide a core framework against which different > ILL workflows can be implemented within Koha. It achieves this by > using 2 new tables as data store, and by using an extensible backend > system to create 'connectors' to ILL providers. > > The data store consists of the illrequests and the > illrequestattributes tables. The former is a traditional table that > stores essential values associated with an ILL request. The later is > a key/value store, linked to a row in the former. This store can be > used to store arbitrary data provided by a backend. > > The backends implement highly customizable workflows for several core > steps in the ILL management process. > > At the same time, each backend can extend the core steps (called > defined as the `core_status_graph` in Koha/Illrequest.pm) with their > own additional steps (defined as the `status_graph` in a backend's > Base.pm). > > Each of these steps, both core and extensions, in turn can define any > number of 'stages' required to complete each individual step. > > Each step has access to a template include file, which can dispatch on > 'stage'. This is mirrored by each step having a sub in a backend's > Base.pm, which once again can dispatch on 'stage'. The subs in > Base.pm have access to the full data store provided by the ILLModule; > similarly the template includes have full access to Koha template > features, including access to custom JS blocks through which, for > instance, external APIs can be called. > > The main aim of this Koha module was to provide a core that is > comprehensive enough to store core data to only have to implement ILL > once in Koha, whilst being extensible enough so that virtually any ILL > workflow can be implemented against this core. > > We believe we have achieved this. I'd be very interested to hear from > you if you believe you have a workflow that cannot be captured by this > (obviously, third party tools that do not provide API access will be > virtually impossible to seamlessly integrate into Koha). > > > 2 Roadmap > ????????? > > The roadmap starts from the current release of code on the bugzilla > issue. > > ? Publication of mature beta level code (21 February 2017) > ? public testing > ? public discussion > ? dogfooding > > ? Augment core functionality (~ June 2017) > ? add advanced configuration options for the core module > ? add a standard system for configuring backends > ? allow for an 'unmediated workflow' > ? finalise 'generic requests' workflow > > ? Meet Koha QA standards (~ July 2017) > ? Add unit tests to core ILLModule > ? Ensure UI respects Koha standards > ? Ensure Core code passes qa scripts > > ? Addition of Documentation > ? contributing a chapter to the Koha manual > ? ensure all pod information is correct and complete > ? ('writing your own backend' tutorial?) > > ? Provide consistent error handling > ? standard means through which a backend can 'throw' an error. > ? replace uses of die with this standard route > > ? Integration into Koha core in Koha 17.11 > > > _______________________________________________ > 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 z.tajoli at cineca.it Tue Feb 21 14:28:05 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Tue, 21 Feb 2017 14:28:05 +0100 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> Message-ID: <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> Hi David, Il 20/02/2017 02:01, David Cook ha scritto: > In 2016, I worked on a Koha task scheduler for downloading and importing > records via OAI-PMH. I have code which works, but it?s lacking test > coverage and I?m unsure that it will make it through QA and be accepted. for me is not 100% clear why do you use a Task scheduler. Why do you no manage queues only with cron ? At least we need a web interface to setup cron. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From nick at bywatersolutions.com Tue Feb 21 19:55:34 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 21 Feb 2017 18:55:34 +0000 Subject: [Koha-devel] Koha Developers Meeting reminder - Tuesday, February 21, 2017 - 13 UTC Message-ID: Hi All, The next Koha Developers IRC meeting is tomorrow, convert into local time using the link below: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting&iso=20170222T13 The agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_22_February Please add anything you wish to discuss. For those who cannot attend please add your name in the apologies and take the time survey here https://framadate.org/3dAEB8zqQLzzTptD or leave a suggestion for next meeting time See you all soon! -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Feb 21 23:29:25 2017 From: dcook at prosentient.com.au (David Cook) Date: Wed, 22 Feb 2017 09:29:25 +1100 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> Message-ID: <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> Hi Zeno, Thanks for your message. Originally, I developed the OAI-PMH harvester using a cronjob, but that wasn't acceptable for Stockholm University Library for a few reasons. One, there was no web interface for controlling it. Two, they wanted to execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as its finest granularity. Three, even if you setup a cronjob to run every minute, long running tasks could get duplicated (although you could mitigate that with locks which would be a pain). Plus, you want to run tasks in parallel, so you're going to want to use multiple processes, which cron isn't really set up to achieve. At the end of it, I think it's more 'to purpose' to have your own daemon where you can control time intervals, workers, have a web interface, etc. Cron is useful for many purposes, but I don't think it's always the right solution. Plus, creating a web interface for cron isn't necessarily the best idea I think. I would consider it to be a hack rather than a solution. As others have pointed out before me, it comes with significant security issues. With a task scheduler, you're much more in control of everything. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Tajoli Zeno [mailto:z.tajoli at cineca.it] > Sent: Wednesday, 22 February 2017 12:28 AM > To: David Cook ; koha-devel at lists.koha- > community.org > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > Hi David, > > Il 20/02/2017 02:01, David Cook ha scritto: > > In 2016, I worked on a Koha task scheduler for downloading and > > importing records via OAI-PMH. I have code which works, but it's > > lacking test coverage and I'm unsure that it will make it through QA and be > accepted. > > for me is not 100% clear why do you use a Task scheduler. > Why do you no manage queues only with cron ? > At least we need a web interface to setup cron. > > Bye > Zeno Tajoli > > > -- > Zeno Tajoli > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > Email: z.tajoli at cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From katrin.fischer.83 at web.de Wed Feb 22 07:31:07 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 22 Feb 2017 07:31:07 +0100 Subject: [Koha-devel] Koha 16.11.04 released Message-ID: The Koha community is proud to announce the release of Koha 16.11.04. This is a maintenance release of 16.11 and contains 3 enhancements and 41 bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-04-release Packages will be available soon. From alex.sassmannshausen at gmail.com Wed Feb 22 07:52:23 2017 From: alex.sassmannshausen at gmail.com (Alex Sassmannshausen) Date: Wed, 22 Feb 2017 07:52:23 +0100 Subject: [Koha-devel] Interlibrary loans module In-Reply-To: References: <87mvdf6cba.fsf@gmail.com> Message-ID: <87k28ik994.fsf@gmail.com> Hugo Agud writes: > Hi Alex > > Wow! it sounds great.. I will try to do my best with this bug ;) Fabulous! Let me know if you need a pointer. Alex > > Kindest Regards > Hugo > > 2017-02-21 11:57 GMT+01:00 Alex Sassmannshausen : > > Hello Kohites! > > Andrew and I have just finished a second major revision of our proposed > interlibrary loans module for Koha. The code and bug can be found at > [https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317]. > > We believe the code has now reached the maturity it requires for wider > engagement, and, more importantly, it's now reached the maturity that it > should be easy to get it up and running relatively easily in your > development environments. > > Unfortunately we cannot deploy the module using sandboxes because > backends are implemented as separate code projects. > > And we would *love* your comments thoughts and concerns about the module > if you are interested in ILL! > > The final comment on the bug contains basic documentation for the Module > as a whole, and also some installation instructions. But for reference, > I've attached the same document to this email too. > > Below you will find some further high-level background and a roadmap of > what we would like to achieve. > > For now, if you're interested in this module: > ? have a look at the bug, and get involved in the discussion! > ? try to set up the module in your dev environment. It should work > easily on dev boxes and dev installs that track master. > ? let us know if you face any issues! > ? start a conversation with us if you might be interested in creating a > backend for your country's / organization's ILL workflows. > > Finally, if you don't have access to a development environment, but you > would be interested in becoming involved in this project, get in touch > and we might be able to provide you with access to a testing > environment! > > Best regards, > > Alex Sassmannshausen > > PTFS Europe > > 1 High-level background > ??????????????????????? > > The ILLModule aims to provide a core framework against which different > ILL workflows can be implemented within Koha. It achieves this by > using 2 new tables as data store, and by using an extensible backend > system to create 'connectors' to ILL providers. > > The data store consists of the illrequests and the > illrequestattributes tables. The former is a traditional table that > stores essential values associated with an ILL request. The later is > a key/value store, linked to a row in the former. This store can be > used to store arbitrary data provided by a backend. > > The backends implement highly customizable workflows for several core > steps in the ILL management process. > > At the same time, each backend can extend the core steps (called > defined as the `core_status_graph` in Koha/Illrequest.pm) with their > own additional steps (defined as the `status_graph` in a backend's > Base.pm). > > Each of these steps, both core and extensions, in turn can define any > number of 'stages' required to complete each individual step. > > Each step has access to a template include file, which can dispatch on > 'stage'. This is mirrored by each step having a sub in a backend's > Base.pm, which once again can dispatch on 'stage'. The subs in > Base.pm have access to the full data store provided by the ILLModule; > similarly the template includes have full access to Koha template > features, including access to custom JS blocks through which, for > instance, external APIs can be called. > > The main aim of this Koha module was to provide a core that is > comprehensive enough to store core data to only have to implement ILL > once in Koha, whilst being extensible enough so that virtually any ILL > workflow can be implemented against this core. > > We believe we have achieved this. I'd be very interested to hear from > you if you believe you have a workflow that cannot be captured by this > (obviously, third party tools that do not provide API access will be > virtually impossible to seamlessly integrate into Koha). > > 2 Roadmap > ????????? > > The roadmap starts from the current release of code on the bugzilla > issue. > > ? Publication of mature beta level code (21 February 2017) > ? public testing > ? public discussion > ? dogfooding > > ? Augment core functionality (~ June 2017) > ? add advanced configuration options for the core module > ? add a standard system for configuring backends > ? allow for an 'unmediated workflow' > ? finalise 'generic requests' workflow > > ? Meet Koha QA standards (~ July 2017) > ? Add unit tests to core ILLModule > ? Ensure UI respects Koha standards > ? Ensure Core code passes qa scripts > > ? Addition of Documentation > ? contributing a chapter to the Koha manual > ? ensure all pod information is correct and complete > ? ('writing your own backend' tutorial?) > > ? Provide consistent error handling > ? standard means through which a backend can 'throw' an error. > ? replace uses of die with this standard route > > ? Integration into Koha core in Koha 17.11 > > _______________________________________________ > 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 mirko at abunchofthings.net Wed Feb 22 08:31:31 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Wed, 22 Feb 2017 08:31:31 +0100 Subject: [Koha-devel] Koha 16.11.04 released In-Reply-To: References: Message-ID: <2245fdc3-9026-997d-86c1-38a740884105@abunchofthings.net> Katrin Fischer schrieb am 22.02.2017 > The Koha community is proud to announce the release of Koha 16.11.04. > > This is a maintenance release of 16.11 and contains 3 enhancements > and 41 bugfixes. > > The full release notes are available at > https://koha-community.org/koha-16-11-04-release > > Packages will be available soon. The Debian package for Koha 16.11.04 is now available from the Koha community repository. -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de From z.tajoli at cineca.it Wed Feb 22 09:49:13 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Wed, 22 Feb 2017 09:49:13 +0100 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> Message-ID: <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> Hi David and all, Il 21/02/2017 23:29, David Cook ha scritto: >. Two, they wanted to > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as its > finest granularity. Three, even if you setup a cronjob to run every minute, > long running tasks could get duplicated (although you could mitigate that > with locks which would be a pain). Plus, you want to run tasks in parallel, > so you're going to want to use multiple processes, which cron isn't really > set up to achieve. Ok, if you need those features cron isn't enough. But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ They have official debiano packages: https://packages.debian.org/jessie/python-celery https://packages.debian.org/jessie/rabbitmq-server https://packages.debian.org/jessie/libanyevent-rabbitmq-perl We still use one of their dpendencies for similar tasks (libanyevent-perl "event loop framework with multiple implementations"). Python is already present in our Debian/Ubuntu system, it is a prereq of the distributions. Redone a so complex stack in perl i think is very complex. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From nick at bywatersolutions.com Wed Feb 22 15:29:22 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Wed, 22 Feb 2017 14:29:22 +0000 Subject: [Koha-devel] Summary: Koha Devel Meeting, 22 Februrary 2017 Message-ID: Hi All, We had a productive dev meeting today, just wanted to highlight some of our discussions for the general list readers. If this seems useful I will try to send these updates after each dev meeting: The Onboarding tool still needs more testing (see Jonathan's email here: http://lists.koha-community.org/pipermail/koha-devel/2017-February/043481.html) This tool will make it easier for those setting up a new instance to enable necessary settings and configuration and generally make Koha setup more friendly. It was proposed as a possibility to roll the tool out in English first, and add other languages as they are tested. Ideally we would have as much testing as possible now. We will discuss and vote on how to move ahead at the next Developers meeting (8 March 2017, 19UTC) The ru-RU and uk-UA languages were discussed for possible removal as there has been no maintenance, if you are using these or interested in helping maintain (or have strong opinion) please let us know. Testing and QA teams can always use more help so let us know if you are interested. Other interesting notes: ElasticSearch dependencies are being packaged by Mirko Jonathan continues work on refactoring and moving things to the Koha namespace (see here for Koha::Patron status) OverDrive integration has been pushed to master The next meeting will be 8 March 2017, 19UTC , I hope to see you there. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Feb 23 01:56:30 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 23 Feb 2017 11:56:30 +1100 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> Message-ID: <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> Hi Zeno, I have a number of concerns about Celery. One of those is that it would add numerous external dependencies and complexity to Koha implementations. Your suggestion of Celery + RabbitMQ + AnyEvent::RabbitMQ sounds ok, although it would involve work too. While Celery clients exist for PHP and Node.js, we'd need to create a Perl implementation of the Celery protocol using AnyEvent::RabbitMQ (or Net::RabbitFoot). Not that I'm necessarily opposed to that. We'd also still need to write the tasks in Python (or use web hooks which would have the overhead of HTTP plus you'd have to worry about your web server being up). I'm not sure how keen the community at large is to support more server-side languages. I like writing Python, so I don't mind porting over my OAI-PMH code from Perl to Python. I've abandoned the HTTP::OAI module anyway for a few reasons. RabbitMQ is a pretty heavy duty product as well which comes with its own requirements: https://www.rabbitmq.com/production-checklist.html. While we currently help people with Apache, MySQL, Zebra, and ElasticSearch, we'd also all need to become experts with RabbitMQ. I've already put together a Perl-based scheduler using POE which forks its own workers. And I've already put together a basic Perl-based message queue which sends events to pre-existing workers (like Celery). Celery with RabbitMQ is more mature and complex, but my Perl programs do the trick. Looking at DSpace's OAI-PMH harvester, it works very much like my first design. It's a Java scheduler which uses threads rather than child processes to do its work. Due to the lack of engagement overall, I think I'll probably just keep my existing design, since it works and works quite well. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Tajoli Zeno [mailto:z.tajoli at cineca.it] > Sent: Wednesday, 22 February 2017 7:49 PM > To: David Cook ; koha-devel at lists.koha- > community.org > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > Hi David and all, > > Il 21/02/2017 23:29, David Cook ha scritto: > >. Two, they wanted to > > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as > >its finest granularity. Three, even if you setup a cronjob to run > >every minute, long running tasks could get duplicated (although you > >could mitigate that with locks which would be a pain). Plus, you want > >to run tasks in parallel, so you're going to want to use multiple > >processes, which cron isn't really set up to achieve. > > Ok, if you need those features cron isn't enough. > But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ > > They have official debiano packages: > https://packages.debian.org/jessie/python-celery > https://packages.debian.org/jessie/rabbitmq-server > https://packages.debian.org/jessie/libanyevent-rabbitmq-perl > > We still use one of their dpendencies for similar tasks (libanyevent-perl "event > loop framework with multiple implementations"). > > Python is already present in our Debian/Ubuntu system, it is a prereq of the > distributions. > > Redone a so complex stack in perl i think is very complex. > > Bye > Zeno Tajoli > > > > -- > Zeno Tajoli > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > Email: z.tajoli at cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From tomascohen at gmail.com Thu Feb 23 04:15:38 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 23 Feb 2017 03:15:38 +0000 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> Message-ID: Share it :-) El mi?., 22 de feb. de 2017 9:57 PM, David Cook escribi?: > Hi Zeno, > > I have a number of concerns about Celery. One of those is that it would add > numerous external dependencies and complexity to Koha implementations. > > Your suggestion of Celery + RabbitMQ + AnyEvent::RabbitMQ sounds ok, > although it would involve work too. While Celery clients exist for PHP and > Node.js, we'd need to create a Perl implementation of the Celery protocol > using AnyEvent::RabbitMQ (or Net::RabbitFoot). Not that I'm necessarily > opposed to that. > > We'd also still need to write the tasks in Python (or use web hooks which > would have the overhead of HTTP plus you'd have to worry about your web > server being up). I'm not sure how keen the community at large is to > support > more server-side languages. I like writing Python, so I don't mind porting > over my OAI-PMH code from Perl to Python. I've abandoned the HTTP::OAI > module anyway for a few reasons. > > RabbitMQ is a pretty heavy duty product as well which comes with its own > requirements: https://www.rabbitmq.com/production-checklist.html. While we > currently help people with Apache, MySQL, Zebra, and ElasticSearch, we'd > also all need to become experts with RabbitMQ. > > I've already put together a Perl-based scheduler using POE which forks its > own workers. And I've already put together a basic Perl-based message queue > which sends events to pre-existing workers (like Celery). Celery with > RabbitMQ is more mature and complex, but my Perl programs do the trick. > > Looking at DSpace's OAI-PMH harvester, it works very much like my first > design. It's a Java scheduler which uses threads rather than child > processes > to do its work. > > Due to the lack of engagement overall, I think I'll probably just keep my > existing design, since it works and works quite well. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > > > -----Original Message----- > > From: Tajoli Zeno [mailto:z.tajoli at cineca.it] > > Sent: Wednesday, 22 February 2017 7:49 PM > > To: David Cook ; koha-devel at lists.koha- > > community.org > > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > > > Hi David and all, > > > > Il 21/02/2017 23:29, David Cook ha scritto: > > >. Two, they wanted to > > > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as > > >its finest granularity. Three, even if you setup a cronjob to run > > >every minute, long running tasks could get duplicated (although you > > >could mitigate that with locks which would be a pain). Plus, you want > > >to run tasks in parallel, so you're going to want to use multiple > > >processes, which cron isn't really set up to achieve. > > > > Ok, if you need those features cron isn't enough. > > But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ > > > > They have official debiano packages: > > https://packages.debian.org/jessie/python-celery > > https://packages.debian.org/jessie/rabbitmq-server > > https://packages.debian.org/jessie/libanyevent-rabbitmq-perl > > > > We still use one of their dpendencies for similar tasks (libanyevent-perl > "event > > loop framework with multiple implementations"). > > > > Python is already present in our Debian/Ubuntu system, it is a prereq of > the > > distributions. > > > > Redone a so complex stack in perl i think is very complex. > > > > Bye > > Zeno Tajoli > > > > > > > > -- > > Zeno Tajoli > > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > > Email: z.tajoli at cineca.it Fax: 051/6132198 > > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) > > > _______________________________________________ > 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 (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Feb 23 04:51:41 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 23 Feb 2017 14:51:41 +1100 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> Message-ID: <0ce901d28d88$2470b300$6d521900$@prosentient.com.au> Which one, Tomas? I?m planning to post the code for what I have already in early March. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen at gmail.com] Sent: Thursday, 23 February 2017 2:16 PM To: David Cook ; Tajoli Zeno ; koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Task schedulers and message queues for Koha Share it :-) El mi?., 22 de feb. de 2017 9:57 PM, David Cook > escribi?: Hi Zeno, I have a number of concerns about Celery. One of those is that it would add numerous external dependencies and complexity to Koha implementations. Your suggestion of Celery + RabbitMQ + AnyEvent::RabbitMQ sounds ok, although it would involve work too. While Celery clients exist for PHP and Node.js, we'd need to create a Perl implementation of the Celery protocol using AnyEvent::RabbitMQ (or Net::RabbitFoot). Not that I'm necessarily opposed to that. We'd also still need to write the tasks in Python (or use web hooks which would have the overhead of HTTP plus you'd have to worry about your web server being up). I'm not sure how keen the community at large is to support more server-side languages. I like writing Python, so I don't mind porting over my OAI-PMH code from Perl to Python. I've abandoned the HTTP::OAI module anyway for a few reasons. RabbitMQ is a pretty heavy duty product as well which comes with its own requirements: https://www.rabbitmq.com/production-checklist.html. While we currently help people with Apache, MySQL, Zebra, and ElasticSearch, we'd also all need to become experts with RabbitMQ. I've already put together a Perl-based scheduler using POE which forks its own workers. And I've already put together a basic Perl-based message queue which sends events to pre-existing workers (like Celery). Celery with RabbitMQ is more mature and complex, but my Perl programs do the trick. Looking at DSpace's OAI-PMH harvester, it works very much like my first design. It's a Java scheduler which uses threads rather than child processes to do its work. Due to the lack of engagement overall, I think I'll probably just keep my existing design, since it works and works quite well. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Tajoli Zeno [mailto:z.tajoli at cineca.it ] > Sent: Wednesday, 22 February 2017 7:49 PM > To: David Cook >; koha-devel at lists.koha- > community.org > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > Hi David and all, > > Il 21/02/2017 23:29, David Cook ha scritto: > >. Two, they wanted to > > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as > >its finest granularity. Three, even if you setup a cronjob to run > >every minute, long running tasks could get duplicated (although you > >could mitigate that with locks which would be a pain). Plus, you want > >to run tasks in parallel, so you're going to want to use multiple > >processes, which cron isn't really set up to achieve. > > Ok, if you need those features cron isn't enough. > But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ > > They have official debiano packages: > https://packages.debian.org/jessie/python-celery > https://packages.debian.org/jessie/rabbitmq-server > https://packages.debian.org/jessie/libanyevent-rabbitmq-perl > > We still use one of their dpendencies for similar tasks (libanyevent-perl "event > loop framework with multiple implementations"). > > Python is already present in our Debian/Ubuntu system, it is a prereq of the > distributions. > > Redone a so complex stack in perl i think is very complex. > > Bye > Zeno Tajoli > > > > -- > Zeno Tajoli > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > Email: z.tajoli at cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) _______________________________________________ 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 (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Thu Feb 23 17:10:56 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 23 Feb 2017 17:10:56 +0100 Subject: [Koha-devel] Hackfest in Marseille, registration open ! Message-ID: <2c1652ef-0b98-fdbb-9f7c-87a4844869a4@biblibre.com> Hello, Registrations for the hackfest are open ! Drop me an email and I'll register you and add you to the usual google document ! Welcome already to the 5 ByWaterians and to Claire G. that have announced they'll be here ;-) (Magnus, we will miss you :( ) -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From z.tajoli at cineca.it Sat Feb 25 10:10:39 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Sat, 25 Feb 2017 10:10:39 +0100 Subject: [Koha-devel] Help requested - new Koha installer and onboarding tool In-Reply-To: References: Message-ID: <971872d7-c61b-5a35-aabd-e904ebc56af2@cineca.it> Hi to all, Il 16/02/2017 14:45, Jonathan Druart ha scritto: > But we need bug 18039 (move the installer files for translated > languages) first. > It is not easy to test everything for just one guy, so we would need one > person for each language: de-DE, es-ES, fr-FR, fr-CA, , it-IT, nb-NO, > pl-PL, ru-RU and uk-UA I tested and sign-off it-IT. I added a follow up for it-IT because for Italy the files notices.sql, notices.txt and system_preferences.sql are better suited for dir 'default'. The sign-off create a quite big file (2 Mb). There is any setup of git to avoid this result ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From jonathan.druart at bugs.koha-community.org Tue Feb 28 12:30:16 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 28 Feb 2017 11:30:16 +0000 Subject: [Koha-devel] Hea v2 In-Reply-To: References: Message-ID: A Hea test server has been set up to ease the tests. Take a look at bug 18066 comment 11 for more information. It's now very easy to test this new version, it will be very helpful to have some of you testing it to get feedbacks. Cheers, Jonathan On Tue, 7 Feb 2017 at 11:01 Jonathan Druart < jonathan.druart at bugs.koha-community.org> wrote: > Hi developers, > > I have submitted a version 2 of Hea on bug 18066. > There are changes to the server code (hea-ws and hea-app) and Koha. > I will need help for testing. There are screenshots on bug 18066 comment > 2, and a test plan on comment 7. > It would be great to get feedbacks and signoff quickly :) > > Cheers, > Jonathan > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18066 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Feb 28 14:48:09 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 28 Feb 2017 13:48:09 +0000 Subject: [Koha-devel] Removal of api/swagger/definitions.t Message-ID: Hi, I propose removing t/db_dependent/api/swagger/definitions.t for a simple reason: it is not obvious that our endpoints should mimick our object models. For instance, if some fields should not be exposed on the API, then they should not be tested for existence. Also, think of fields that have names that are kept for historical reasons and should better be changed on the published api. Maybe I went too far explaining it, but I think it should be removed. Regards -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue Feb 28 17:47:47 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 28 Feb 2017 16:47:47 +0000 Subject: [Koha-devel] Koha General IRC Meeting Reminder - 1 MArch 2017, 20 UTC Message-ID: Hello All, Just a reminder that tomorrow at 20 UTC is the monthly general IRC meeting for koha. Local time conversion here: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting&iso=20170301T20 The agenda is on the wiki here https://wiki.koha-community.org/wiki/General_IRC_meeting_1_March_2017 Please add anything you wish to discuss. See you soon! -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: