From bargioni at pusc.it  Tue Nov  1 10:47:46 2016
From: bargioni at pusc.it (Stefano Bargioni)
Date: Tue, 01 Nov 2016 10:47:46 +0100
Subject: [Koha-devel] Create autocomplete for addbiblio.pl
In-Reply-To: <CABndEwRZrOrm3dZ6BRWSNN2vpyw3OBR-DWMN0vKF2aFOgwtUNQ@mail.gmail.com>
References: <CABndEwRZrOrm3dZ6BRWSNN2vpyw3OBR-DWMN0vKF2aFOgwtUNQ@mail.gmail.com>
Message-ID: <20161101094746.27608.qmail@mail.pusc.it>

I like your idea.
Anyway, you can select the field 110a using
$('input[id^=tag_110_subfield_a_]')
HTH. Stefano 


Rodrigo Santellan writes: 

> Hi, 
> 
> I'm trying to create an autocomplete for a few fields when adding a biblio.
> My problem so far is that the ids generated are things like this:
> *tag_110_subfield_a_361770_300725* (I'm trying to create an author
> autocomplete). One quick fix for me will be to add to the fields a class
> containing this: tag_[% subfield_loo.tag %]_subfield_[%
> subfield_loo.subfield %] 
> 
> Should this will be helpful to anybody else? Is there a better way to do
> this? 
> 
> Regards

From jonathan.druart at bugs.koha-community.org  Tue Nov  1 11:38:18 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Tue, 01 Nov 2016 10:38:18 +0000
Subject: [Koha-devel] Create autocomplete for addbiblio.pl
In-Reply-To: <CABndEwRZrOrm3dZ6BRWSNN2vpyw3OBR-DWMN0vKF2aFOgwtUNQ@mail.gmail.com>
References: <CABndEwRZrOrm3dZ6BRWSNN2vpyw3OBR-DWMN0vKF2aFOgwtUNQ@mail.gmail.com>
Message-ID: <CAJzKNY4_xd1dFBVJ73ssapMhxDmEfwnQ_fCd3dR2bU5mZZUL4A@mail.gmail.com>

Hi Rodrigo,

I think what you are trying to achieve should be done using plugins, have a
look at the cataloguing/value_builder scripts.

Cheers,
Jonathan

On Mon, 31 Oct 2016 at 20:19 Rodrigo Santellan <rsantellan at gmail.com> wrote:

> Hi,
>
> I'm trying to create an autocomplete for a few fields when adding a
> biblio. My problem so far is that the ids generated are things like this:
> *tag_110_subfield_a_361770_300725* (I'm trying to create an author
> autocomplete). One quick fix for me will be to add to the fields a class
> containing this: tag_[% subfield_loo.tag %]_subfield_[%
> subfield_loo.subfield %]
>
> Should this will be helpful to anybody else? Is there a better way to do
> this?
>
> Regards
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161101/dea4c0c0/attachment-0001.html>

From rsantellan at gmail.com  Tue Nov  1 13:29:41 2016
From: rsantellan at gmail.com (Rodrigo Santellan)
Date: Tue, 1 Nov 2016 09:29:41 -0300
Subject: [Koha-devel] Create autocomplete for addbiblio.pl
In-Reply-To: <CAJzKNY4_xd1dFBVJ73ssapMhxDmEfwnQ_fCd3dR2bU5mZZUL4A@mail.gmail.com>
References: <CABndEwRZrOrm3dZ6BRWSNN2vpyw3OBR-DWMN0vKF2aFOgwtUNQ@mail.gmail.com>
	<CAJzKNY4_xd1dFBVJ73ssapMhxDmEfwnQ_fCd3dR2bU5mZZUL4A@mail.gmail.com>
Message-ID: <CABndEwR7_rpn_V-v8Gpq8K2_gezSbvw4B3+sfsh-i16CX+xGcw@mail.gmail.com>

Stefano,

This work really good *$('input[id^=tag_110_subfield_**a_]') *I can select
the desired inputs that way without touching anything. I still will propose
to add the class that add more data to the field.

Jonathan: for what I see the plugins add stuff after the field not in the
field like I want.

Thanks for the help!

Regards

On Tue, Nov 1, 2016 at 7:38 AM, Jonathan Druart <
jonathan.druart at bugs.koha-community.org> wrote:

> Hi Rodrigo,
>
> I think what you are trying to achieve should be done using plugins, have
> a look at the cataloguing/value_builder scripts.
>
> Cheers,
> Jonathan
>
> On Mon, 31 Oct 2016 at 20:19 Rodrigo Santellan <rsantellan at gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm trying to create an autocomplete for a few fields when adding a
>> biblio. My problem so far is that the ids generated are things like this:
>> *tag_110_subfield_a_361770_300725* (I'm trying to create an author
>> autocomplete). One quick fix for me will be to add to the fields a class
>> containing this: tag_[% subfield_loo.tag %]_subfield_[%
>> subfield_loo.subfield %]
>>
>> Should this will be helpful to anybody else? Is there a better way to do
>> this?
>>
>> Regards
>> _______________________________________________
>> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161101/340526c7/attachment.html>

From chrisc at catalyst.net.nz  Tue Nov  1 20:39:31 2016
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Wed, 2 Nov 2016 08:39:31 +1300
Subject: [Koha-devel] Koha meeting reminder
Message-ID: <20161101193931.yqbolxvzje6cfmtn@rorohiko.wgtn.cat-it.co.nz>

Hi All

The next Koha meeting is on IRC at 2 November 2016 at 20:00 UTC 

You can see what that is in your local time here 
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting&iso=20161102T20

This is an important meeting as we confirm the roles for the 17.05 release

Agenda is here
https://wiki.koha-community.org/wiki/General_IRC_meeting_2_November_2016

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161102/7651d893/attachment.pgp>

From divyabatra2001 at gmail.com  Fri Nov  4 07:11:42 2016
From: divyabatra2001 at gmail.com (Divya Batra)
Date: Fri, 4 Nov 2016 11:41:42 +0530
Subject: [Koha-devel] koha on redhat
Message-ID: <CACOJLOoDtdhkFTtEJLNT9djB392jgtmKQd5R03snnpvN8zau+w@mail.gmail.com>

Dear,
Greetings


I want to know about the procedure and entire method for installing koha on
redhat. Ours is a government organization and servers with redhat installed
is available for us to use and complete redhat support is also available.
As it is a government organization internet access is as such not available
on the server system so offline installation is needed to be done.
Koha is an open source system, so it should be possible to install it on
any linux machine. I want to know how we can do that.
We want to install a stable koha version on a stable redhat version.

Hoping for a positive reply.
Thanks & Regards
Divya Batra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161104/7fb71902/attachment.html>

From rsantellan at gmail.com  Fri Nov  4 13:31:45 2016
From: rsantellan at gmail.com (Rodrigo Santellan)
Date: Fri, 4 Nov 2016 09:31:45 -0300
Subject: [Koha-devel] koha on redhat
In-Reply-To: <CACOJLOoDtdhkFTtEJLNT9djB392jgtmKQd5R03snnpvN8zau+w@mail.gmail.com>
References: <CACOJLOoDtdhkFTtEJLNT9djB392jgtmKQd5R03snnpvN8zau+w@mail.gmail.com>
Message-ID: <CABndEwTbSejS1euWgUqMWfaLyAraFjt0wXv0W7VGJ+AMheu=8w@mail.gmail.com>

Divya,

There is a page on the wiki that says how to on RHEL:
https://wiki.koha-community.org/wiki/Koha_on_Redhat_Enterprise_6

My recommendation is that install it on a machine with internet first for
all the dependency resolutions and then try it on the actual server.

You can download the source code and run the MakeFile.PL,



*perl Makefile.PLmake && make testmake install*

On the other side you can use alien to convert a deb package to a rpm
package: http://www.thegeekstuff.com/2010/11/alien-command-examples/ and
try with that.

If you try and fail post the terminal outputs so we can help.

Regards.

On Fri, Nov 4, 2016 at 3:11 AM, Divya Batra <divyabatra2001 at gmail.com>
wrote:

> Dear,
> Greetings
>
>
> I want to know about the procedure and entire method for installing koha
> on redhat. Ours is a government organization and servers with redhat
> installed is available for us to use and complete redhat support is also
> available.
> As it is a government organization internet access is as such not
> available on the server system so offline installation is needed to be
> done.
> Koha is an open source system, so it should be possible to install it on
> any linux machine. I want to know how we can do that.
> We want to install a stable koha version on a stable redhat version.
>
> Hoping for a positive reply.
> Thanks & Regards
> Divya Batra
>
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161104/fffa1b60/attachment.html>

From gaetan.boisson at biblibre.com  Fri Nov  4 17:20:03 2016
From: gaetan.boisson at biblibre.com (Gaetan Boisson)
Date: Fri, 4 Nov 2016 17:20:03 +0100
Subject: [Koha-devel] proper sorting order and search for Swedish characters
 and ISBN search
Message-ID: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com>

  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.

ICU has some kind of setting that allows to standardize isbns for 
searching, so you can search for any hyphenated variant, and still find 
the isbn that actually appears in your data. I *think* this works by 
removing all the hyphens in the index, but i am not quite sure.

Anyway, in order to get the Swedish letters right, we had to do some 
specific chr configuration. Doing this forces us not to use ICU, which 
means giving up on standardized isbn search.

Alternatives are transforming all the isbns in the records (quite uly). 
Or using the SearchWithISBNVariations syspref, but as far as i 
understand, this only works when using the dedicated isbn index, not in 
the simple search.

Has anyone found a more satisfactory way of handling this?

Thanks,


-- 
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 z.tajoli at cineca.it  Fri Nov  4 17:46:57 2016
From: z.tajoli at cineca.it (Tajoli Zeno)
Date: Fri, 4 Nov 2016 17:46:57 +0100
Subject: [Koha-devel] proper sorting order and search for Swedish
 characters and ISBN search
In-Reply-To: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com>
References: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com>
Message-ID: <d99a507e-800c-c631-1c1d-f58a1fb1b4dc@cineca.it>

Hi Gaetan and all,

Il 04/11/2016 17:20, Gaetan Boisson ha scritto:
> 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.
>
> ICU has some kind of setting that allows to standardize isbns for
> searching, so you can search for any hyphenated variant, and still find
> the isbn that actually appears in your data. I *think* this works by
> removing all the hyphens in the index, but i am not quite sure.
>
> Anyway, in order to get the Swedish letters right, we had to do some
> specific chr configuration. Doing this forces us not to use ICU, which
> means giving up on standardized isbn search.

I think you speaking about general index.

zebradb/lang_defs/en/sort-string-utf.chr
7 lowercase {0-9}{a-y}?z?????
8 uppercase {0-9}{A-Y}?Z?????
[..]
16 # equivalent ??(ae)
17 # equivalent ??(oe)
18 # equivalent ?(aa)
19 # equivalent u?

zebradb/etc/words-icu.xml
2   <transliterate rule="{ ? > oe "/>
3   <transliterate rule="{ ? > oe "/>
4   <transliterate rule="{ ? > ae "/>
5   <transliterate rule="{ ? > ae "/>

zebradb/etc/phrases-icu.xml
2   <transliterate rule="{ ? > oe "/>
3   <transliterate rule="{ ? > oe "/>
4   <transliterate rule="{ ? > ae "/>
5   <transliterate rule="{ ? > ae "/>

Is it not enough to change only those configurations to fix your problem ?
Which configuration do force you to CHR conf instead of ICU ?

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 chris at bigballofwax.co.nz  Mon Nov  7 21:05:50 2016
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Tue, 8 Nov 2016 09:05:50 +1300
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
Message-ID: <CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>

On 8 November 2016 at 08:50, Michael Kuhn <mik at adminkuhn.ch> wrote:
> Hi,
>
> We are looking for a solution to build a redundant infrastructure for Koha.
>
> What we want to do is shown in the diagram
> http://adminkuhn.ch/download/Redundant.png
>
> The main objective of such a solution is: If one of the Application Servers
> goes down the other will take over the job without losing any time. If the
> DB-Server Master goes down we will be able to build the Master out of the
> Slave and create a new Slave next to the new Master.
>
> Has anyone ever built such an infrastructure with Koha and can give us some
> advice how to proceed? Is this possible with Koha anyway?


Will shift this to Koha-devel

Yes this is possible and quite easy to do. What makes it tricky is
Zebra, which you have left out
of your diagram.
You either need to have the full zebra index on both your application
servers (which means modifying rebuild_zebraqueue to make
sure it gets built by each machine)
Or you need to use something like nfs or another distributed
filesystem. Or use rsync etc.

It becomes a lot easier with elasticsearch of course, because you just
have your elastic cluster
and they talk to that.

Hope this helps

Chris

>
> Best wishes: Michael
> --
> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz
> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

From rsantellan at gmail.com  Mon Nov  7 21:17:17 2016
From: rsantellan at gmail.com (Rodrigo Santellan)
Date: Mon, 7 Nov 2016 17:17:17 -0300
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
Message-ID: <CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>

Chris,

What about the uploaded files? You will need to replicate them to the other
server.

What about the cross connection of the DB, you will use mysql proxy in the
middle?

I'm really curious about those answers.

Regards.

On Mon, Nov 7, 2016 at 5:05 PM, Chris Cormack <chris at bigballofwax.co.nz>
wrote:

> On 8 November 2016 at 08:50, Michael Kuhn <mik at adminkuhn.ch> wrote:
> > Hi,
> >
> > We are looking for a solution to build a redundant infrastructure for
> Koha.
> >
> > What we want to do is shown in the diagram
> > http://adminkuhn.ch/download/Redundant.png
> >
> > The main objective of such a solution is: If one of the Application
> Servers
> > goes down the other will take over the job without losing any time. If
> the
> > DB-Server Master goes down we will be able to build the Master out of the
> > Slave and create a new Slave next to the new Master.
> >
> > Has anyone ever built such an infrastructure with Koha and can give us
> some
> > advice how to proceed? Is this possible with Koha anyway?
>
>
> Will shift this to Koha-devel
>
> Yes this is possible and quite easy to do. What makes it tricky is
> Zebra, which you have left out
> of your diagram.
> You either need to have the full zebra index on both your application
> servers (which means modifying rebuild_zebraqueue to make
> sure it gets built by each machine)
> Or you need to use something like nfs or another distributed
> filesystem. Or use rsync etc.
>
> It becomes a lot easier with elasticsearch of course, because you just
> have your elastic cluster
> and they talk to that.
>
> Hope this helps
>
> Chris
>
> >
> > Best wishes: Michael
> > --
> > Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> > Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz
> > T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch
> > _______________________________________________
> > Koha mailing list  http://koha-community.org
> > Koha at lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161107/c837d5f8/attachment.html>

From chris at bigballofwax.co.nz  Mon Nov  7 21:19:12 2016
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Tue, 8 Nov 2016 09:19:12 +1300
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
	<CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
Message-ID: <CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>

If you allow people to upload files sure.

We usually don't that is what a CMS is for. (Uploaded images are
stored in the db)

And yes talking to a DB is a solved problem, thousands of applications
around the world do that already.
The only thing that is unique to Koha is Zebra

Chris

On 8 November 2016 at 09:17, Rodrigo Santellan <rsantellan at gmail.com> wrote:
> Chris,
>
> What about the uploaded files? You will need to replicate them to the other
> server.
>
> What about the cross connection of the DB, you will use mysql proxy in the
> middle?
>
> I'm really curious about those answers.
>
> Regards.
>
> On Mon, Nov 7, 2016 at 5:05 PM, Chris Cormack <chris at bigballofwax.co.nz>
> wrote:
>>
>> On 8 November 2016 at 08:50, Michael Kuhn <mik at adminkuhn.ch> wrote:
>> > Hi,
>> >
>> > We are looking for a solution to build a redundant infrastructure for
>> > Koha.
>> >
>> > What we want to do is shown in the diagram
>> > http://adminkuhn.ch/download/Redundant.png
>> >
>> > The main objective of such a solution is: If one of the Application
>> > Servers
>> > goes down the other will take over the job without losing any time. If
>> > the
>> > DB-Server Master goes down we will be able to build the Master out of
>> > the
>> > Slave and create a new Slave next to the new Master.
>> >
>> > Has anyone ever built such an infrastructure with Koha and can give us
>> > some
>> > advice how to proceed? Is this possible with Koha anyway?
>>
>>
>> Will shift this to Koha-devel
>>
>> Yes this is possible and quite easy to do. What makes it tricky is
>> Zebra, which you have left out
>> of your diagram.
>> You either need to have the full zebra index on both your application
>> servers (which means modifying rebuild_zebraqueue to make
>> sure it gets built by each machine)
>> Or you need to use something like nfs or another distributed
>> filesystem. Or use rsync etc.
>>
>> It becomes a lot easier with elasticsearch of course, because you just
>> have your elastic cluster
>> and they talk to that.
>>
>> Hope this helps
>>
>> Chris
>>
>> >
>> > Best wishes: Michael
>> > --
>> > Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis
>> > Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz
>> > T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch
>> > _______________________________________________
>> > Koha mailing list  http://koha-community.org
>> > Koha at lists.katipo.co.nz
>> > https://lists.katipo.co.nz/mailman/listinfo/koha
>> _______________________________________________
>> 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 michael.hafen at washk12.org  Mon Nov  7 22:36:13 2016
From: michael.hafen at washk12.org (Michael Hafen)
Date: Mon, 7 Nov 2016 14:36:13 -0700
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
	<CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
	<CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>
Message-ID: <CAAh7Ud=ShU4cS0hGu2-fvZKCbLNOcOJUNWRYtVx=_6ra=-zvWQ@mail.gmail.com>

Has anyone tried access Zebra through a network socket instead of the unix
one?  I was under the impression that that was possible.
I've considered a similar setup to what Michael Kuhn is trying build.  I
already have a database cluster using active-active replication and IP
address fail-over with heartbeat.  So that's working for me just fine.
I've also played with GlusterFS as a shared upload space to serve other
applications, so that's also a possibility.  It really is Zebra that is the
biggest question for me.
My hope is that accessing Zebra over the network is possible, then I just
dedicate a worker to running and maintaining Zebra, and point the other
workers at it.  That way worst case is searching doesn't work for the hour
or so it would take to spin up Zebra somewhere else if it's server goes
down.

On Mon, Nov 7, 2016 at 1:19 PM, Chris Cormack <chris at bigballofwax.co.nz>
wrote:

> If you allow people to upload files sure.
>
> We usually don't that is what a CMS is for. (Uploaded images are
> stored in the db)
>
> And yes talking to a DB is a solved problem, thousands of applications
> around the world do that already.
> The only thing that is unique to Koha is Zebra
>
> Chris
>
> On 8 November 2016 at 09:17, Rodrigo Santellan <rsantellan at gmail.com>
> wrote:
> > Chris,
> >
> > What about the uploaded files? You will need to replicate them to the
> other
> > server.
> >
> > What about the cross connection of the DB, you will use mysql proxy in
> the
> > middle?
> >
> > I'm really curious about those answers.
> >
> > Regards.
> >
> > On Mon, Nov 7, 2016 at 5:05 PM, Chris Cormack <chris at bigballofwax.co.nz>
> > wrote:
> >>
> >> On 8 November 2016 at 08:50, Michael Kuhn <mik at adminkuhn.ch> wrote:
> >> > Hi,
> >> >
> >> > We are looking for a solution to build a redundant infrastructure for
> >> > Koha.
> >> >
> >> > What we want to do is shown in the diagram
> >> > http://adminkuhn.ch/download/Redundant.png
> >> >
> >> > The main objective of such a solution is: If one of the Application
> >> > Servers
> >> > goes down the other will take over the job without losing any time. If
> >> > the
> >> > DB-Server Master goes down we will be able to build the Master out of
> >> > the
> >> > Slave and create a new Slave next to the new Master.
> >> >
> >> > Has anyone ever built such an infrastructure with Koha and can give us
> >> > some
> >> > advice how to proceed? Is this possible with Koha anyway?
> >>
> >>
> >> Will shift this to Koha-devel
> >>
> >> Yes this is possible and quite easy to do. What makes it tricky is
> >> Zebra, which you have left out
> >> of your diagram.
> >> You either need to have the full zebra index on both your application
> >> servers (which means modifying rebuild_zebraqueue to make
> >> sure it gets built by each machine)
> >> Or you need to use something like nfs or another distributed
> >> filesystem. Or use rsync etc.
> >>
> >> It becomes a lot easier with elasticsearch of course, because you just
> >> have your elastic cluster
> >> and they talk to that.
> >>
> >> Hope this helps
> >>
> >> Chris
> >>
> >> >
> >> > Best wishes: Michael
> >> > --
> >> > Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg.
> Fachausweis
> >> > Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz
> >> > T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch
> >> > _______________________________________________
> >> > Koha mailing list  http://koha-community.org
> >> > Koha at lists.katipo.co.nz
> >> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >> _______________________________________________
> >> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161107/81f3a779/attachment-0001.html>

From gmc at esilibrary.com  Mon Nov  7 22:42:15 2016
From: gmc at esilibrary.com (Galen Charlton)
Date: Mon, 7 Nov 2016 16:42:15 -0500
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <CAAh7Ud=ShU4cS0hGu2-fvZKCbLNOcOJUNWRYtVx=_6ra=-zvWQ@mail.gmail.com>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
	<CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
	<CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>
	<CAAh7Ud=ShU4cS0hGu2-fvZKCbLNOcOJUNWRYtVx=_6ra=-zvWQ@mail.gmail.com>
Message-ID: <CAPLnt67txtbBB9hn=Gw_oXuZTKyJBz=+K-OqZH3h-CMKpbekdg@mail.gmail.com>

Hi,

On Mon, Nov 7, 2016 at 4:36 PM, Michael Hafen <michael.hafen at washk12.org> wrote:
> Has anyone tried access Zebra through a network socket instead of the unix
> one?  I was under the impression that that was possible.

It is, and it's as easy as changing the following lines in koha-conf.xml from:

<listen id="biblioserver" >unix:/var/run/koha/SITE/bibliosocket</listen>
<listen id="authorityserver" >unix:/var/run/koha/SITE/authoritysocket</listen>

to

<listen id="biblioserver" >tcp:HOST_OR_IP:PORT</listen>
<listen id="authorityserver" >tcp:HOST_OR_IP:ANOTHER_PORT</listen>

Of course, depending on how you arrange things, local tweaks to the
indexer jobs would be required to ensure that all of the copies of the
Zebra databases got updated.

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Software, Inc. / Open Your Library
email:  gmc at esilibrary.com
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org

From arthur.suzuki at univ-lyon3.fr  Tue Nov  8 10:11:43 2016
From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur)
Date: Tue, 8 Nov 2016 10:11:43 +0100
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <CAPLnt67txtbBB9hn=Gw_oXuZTKyJBz=+K-OqZH3h-CMKpbekdg@mail.gmail.com>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
	<CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
	<CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>
	<CAAh7Ud=ShU4cS0hGu2-fvZKCbLNOcOJUNWRYtVx=_6ra=-zvWQ@mail.gmail.com>
	<CAPLnt67txtbBB9hn=Gw_oXuZTKyJBz=+K-OqZH3h-CMKpbekdg@mail.gmail.com>
Message-ID: <68a04dcb-9b6d-ef7c-6b4c-505ca4e71033@univ-lyon3.fr>

Hi,

For Zebra and Web-server, this could be a good use case for HA-Proxy.

Never used this myself but I have read some documentations about how it 
can be used to setup redundancy and/or load-balancing between servers 
for applications that doesn't support this feature out-of the box.

For file storage distributed across multiple nodes there is this 
newcomer called Tahoe-LAFS :

https://tahoe-lafs.org/trac/tahoe-lafs

Hope this help your purpose.

I have to say I've some interests into the question myself, don't 
hesitate to share your results!

Regards,

Arthur


Le 07/11/2016 ? 22:42, Galen Charlton a ?crit :
> Hi,
>
> On Mon, Nov 7, 2016 at 4:36 PM, Michael Hafen <michael.hafen at washk12.org> wrote:
>> Has anyone tried access Zebra through a network socket instead of the unix
>> one?  I was under the impression that that was possible.
> It is, and it's as easy as changing the following lines in koha-conf.xml from:
>
> <listen id="biblioserver" >unix:/var/run/koha/SITE/bibliosocket</listen>
> <listen id="authorityserver" >unix:/var/run/koha/SITE/authoritysocket</listen>
>
> to
>
> <listen id="biblioserver" >tcp:HOST_OR_IP:PORT</listen>
> <listen id="authorityserver" >tcp:HOST_OR_IP:ANOTHER_PORT</listen>
>
> Of course, depending on how you arrange things, local tweaks to the
> indexer jobs would be required to ensure that all of the copies of the
> Zebra databases got updated.
>
> Regards,
>
> Galen

-- 
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 tomascohen at gmail.com  Tue Nov  8 15:11:29 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Tue, 08 Nov 2016 14:11:29 +0000
Subject: [Koha-devel] KohaDevBox v2.0 released
Message-ID: <CABZfb=UTCaPKD+0BNGAEE57iHcC6sVj08eLvwWM_ZrrpC=wSZQ@mail.gmail.com>

After lots of months of work and people's contributions, we finally reached
our milestone for v2.0.

The original KohaDevBox functionalities are all implemented on the
Ansible-driven one, and we can now focus on making it even better (we
already have Elasticsearch integration, automatic superlibrarian user
creation, and lots of configuration options).

It can be used on Linux, Mac OS and Windows. It provides a full development
and testing environment for people willing to work on the project.

Read the README.md[1] file to get an idea of how easy is to get a full
development environment, and the flexibility you can get with all the
options we provide.

Please enjoy it, and fill issues for any problem you might have. It can be
improved, and we count on you to help us :-D

Koha Development Team

[1] https://github.com/digibib/kohadevbox
-- 
Tom?s Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161108/51cb4403/attachment.html>

From michael.hafen at washk12.org  Tue Nov  8 18:33:44 2016
From: michael.hafen at washk12.org (Michael Hafen)
Date: Tue, 8 Nov 2016 10:33:44 -0700
Subject: [Koha-devel] [Koha] Redundant infrastructure for Koha
In-Reply-To: <68a04dcb-9b6d-ef7c-6b4c-505ca4e71033@univ-lyon3.fr>
References: <CAGbk3pTXyQ5ui5EBazv8rtdiGC5KC0jLg2BH0EmhGEvKk9PyVg@mail.gmail.com>
	<51053889-a4e1-08a7-c195-3a550e808099@gmail.com>
	<CAFHDGYUFtj5VswuncEH0AwMGNtWGwpw-dxCw0KnFeAs_ASekZg@mail.gmail.com>
	<a4c1a632-5e11-7861-1cac-62ee9a280f7a@adminkuhn.ch>
	<CA+95qVTJ7+Bv3HrcEKvHhpRCftu58eaHJ5fC8RxA00aaAaLMYA@mail.gmail.com>
	<CABndEwScB3bF35U8GsN0t9_vqidhhv_xa5yjiwVcKwt1BEbNYA@mail.gmail.com>
	<CA+95qVSmPriXZkH-BHi5gN0EJ9efWzyXb9C1G54RZaJ2T21_Sw@mail.gmail.com>
	<CAAh7Ud=ShU4cS0hGu2-fvZKCbLNOcOJUNWRYtVx=_6ra=-zvWQ@mail.gmail.com>
	<CAPLnt67txtbBB9hn=Gw_oXuZTKyJBz=+K-OqZH3h-CMKpbekdg@mail.gmail.com>
	<68a04dcb-9b6d-ef7c-6b4c-505ca4e71033@univ-lyon3.fr>
Message-ID: <CAAh7Ud=CuqBy=+1OWn1v8+hgkX=JC=DRV6WP4pa08z5YgM6p1A@mail.gmail.com>

Tahoe-lafs looks interesting if one where locked to cloud storage.  I'm
planning to deal with storage on the local level, where a simple
copy-on-write style system is sufficient.  I don't anticipate needing the
kind of security provided by Tahoe-lafs, so it seems like overkill to me.

As for HA-Proxy, that might be good for client requests to Zebra.  The real
problem is handling writes to Zebra.  Using the queue table in the database
would keep one copy up to date, but short of a copy-on-write system I have
my doubts about being able to cluster Zebra.  Even with a shared file
system I expect Zebra tries to lock it's files, which would mean more than
one Zebra server on the same directory of the same file system probably
wouldn't work.  ( I ran into that with Mysql in an earlier attempt at
redundancy, and it corrupted many tables when both servers were access the
same files at the same time. )


On Tue, Nov 8, 2016 at 2:11 AM, SUZUKI Arthur <arthur.suzuki at univ-lyon3.fr>
wrote:

> Hi,
>
> For Zebra and Web-server, this could be a good use case for HA-Proxy.
>
> Never used this myself but I have read some documentations about how it
> can be used to setup redundancy and/or load-balancing between servers for
> applications that doesn't support this feature out-of the box.
>
> For file storage distributed across multiple nodes there is this newcomer
> called Tahoe-LAFS :
>
> https://tahoe-lafs.org/trac/tahoe-lafs
>
> Hope this help your purpose.
>
> I have to say I've some interests into the question myself, don't hesitate
> to share your results!
>
> Regards,
>
> Arthur
>
>
> Le 07/11/2016 ? 22:42, Galen Charlton a ?crit :
>
>> Hi,
>>
>> On Mon, Nov 7, 2016 at 4:36 PM, Michael Hafen <michael.hafen at washk12.org>
>> wrote:
>>
>>> Has anyone tried access Zebra through a network socket instead of the
>>> unix
>>> one?  I was under the impression that that was possible.
>>>
>> It is, and it's as easy as changing the following lines in koha-conf.xml
>> from:
>>
>> <listen id="biblioserver" >unix:/var/run/koha/SITE/bibliosocket</listen>
>> <listen id="authorityserver" >unix:/var/run/koha/SITE/autho
>> ritysocket</listen>
>>
>> to
>>
>> <listen id="biblioserver" >tcp:HOST_OR_IP:PORT</listen>
>> <listen id="authorityserver" >tcp:HOST_OR_IP:ANOTHER_PORT</listen>
>>
>> Of course, depending on how you arrange things, local tweaks to the
>> indexer jobs would be required to ensure that all of the copies of the
>> Zebra databases got updated.
>>
>> Regards,
>>
>> Galen
>>
>
> --
> 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/
>



-- 
Michael Hafen
Washington County School District Technology Department
Systems Analyst
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161108/00b69c54/attachment.html>

From nick at bywatersolutions.com  Tue Nov  8 21:23:00 2016
From: nick at bywatersolutions.com (Nick Clemens)
Date: Tue, 08 Nov 2016 20:23:00 +0000
Subject: [Koha-devel] Koha development meeting reminder - 9 November 2016
Message-ID: <CAA_eX3Ojt=7w6oW6UqQOCje+P1uyMZpbBKRPpe5y7neY8i=Qzg@mail.gmail.com>

Hi All,

The next Koha development meeting is on IRC tomorrow 9 November 2016 at
19: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=20161109T19

Agenda is here:
https://wiki.koha-community.org/wiki/Development_IRC_meeting_9_November_2016

Please make sure to add any topics you wish to discuss.

I will be chairing the meeting so I can learn, so attend and be nice :-)

-Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161108/7e8fd058/attachment.html>

From kyle.m.hall at gmail.com  Fri Nov 11 04:20:02 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Thu, 10 Nov 2016 22:20:02 -0500
Subject: [Koha-devel] Koha 16.11 Release Notes ( 2nd Draft )
In-Reply-To: <CACpVHfy2KAeSemEQsrruzt+WpRbXREDvgpcW=2Fw0vyX_W8SCQ@mail.gmail.com>
References: <CACpVHfy2KAeSemEQsrruzt+WpRbXREDvgpcW=2Fw0vyX_W8SCQ@mail.gmail.com>
Message-ID: <CACpVHfz+-b25W5NygTowPeYrMGuDr=dak5KDW-Top4Z1Tg8HcQ@mail.gmail.com>

I've already noticed the "new feature" count is off. I'll fix that in the
next revision.

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Thu, Nov 10, 2016 at 10:18 PM, Kyle Hall <kyle.m.hall at gmail.com> wrote:

> Hey All!
>
> Here is the second draft of the release notes for Koha 16.11!
>
> Additional bugs pushed since then have been added and I've made some
> manual changes based on feedback kindly made by Katrin. Thanks Katrin!
>
> The HTML is attached, and you can find them on GitHub here
> <https://github.com/kylemhall/Koha/commits/rel16_11_00_release_notes_draft_2>
> .
>
> Kyle
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161110/f04f1670/attachment.html>

From katrin.fischer.83 at web.de  Fri Nov 11 06:46:21 2016
From: katrin.fischer.83 at web.de (Katrin)
Date: Fri, 11 Nov 2016 06:46:21 +0100
Subject: [Koha-devel] Koha 16.11 Release Notes ( 2nd Draft )
In-Reply-To: <CACpVHfz+-b25W5NygTowPeYrMGuDr=dak5KDW-Top4Z1Tg8HcQ@mail.gmail.com>
References: <CACpVHfy2KAeSemEQsrruzt+WpRbXREDvgpcW=2Fw0vyX_W8SCQ@mail.gmail.com>
	<CACpVHfz+-b25W5NygTowPeYrMGuDr=dak5KDW-Top4Z1Tg8HcQ@mail.gmail.com>
Message-ID: <bd07961d-5161-1662-b403-52eca3c423f1@web.de>

I changed them all to 'new feature' on bugzilla now too, so they will 
move into place automatically next run.

The paragraph: "It will be possible to send order information to the 
vendor by e-mail. For now this feature can be triggered manually with a 
button before closing the basket. The order e-mail is based on the 
acquisition claim feature, but uses a new notice template: ACQORDER." on 
top of acquisitions belongs to bug 5260

Should we try and add short descriptions to the other new features in 
bugzilla too?

Katrin

On 11.11.2016 04:20, Kyle Hall wrote:
> I've already noticed the "new feature" count is off. I'll fix that in 
> the next revision.
>
> Kyle
>
> <https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
> On Thu, Nov 10, 2016 at 10:18 PM, Kyle Hall <kyle.m.hall at gmail.com 
> <mailto:kyle.m.hall at gmail.com>> wrote:
>
>     Hey All!
>
>     Here is the second draft of the release notes for Koha 16.11!
>
>     Additional bugs pushed since then have been added and I've made
>     some manual changes based on feedback kindly made by Katrin.
>     Thanks Katrin!
>
>     The HTML is attached, and you can find them on GitHub here
>     <https://github.com/kylemhall/Koha/commits/rel16_11_00_release_notes_draft_2>.
>
>     Kyle
>
>     http://www.kylehall.info
>     ByWater Solutions ( http://bywatersolutions.com )
>     Meadville Public Library ( http://www.meadvillelibrary.org
>     <http://www.meadvillelibrary.org> )
>     Crawford County Federated Library System ( http://www.ccfls.org )
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161111/171382a9/attachment.html>

From jonathan.druart at bugs.koha-community.org  Fri Nov 11 12:34:42 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Fri, 11 Nov 2016 11:34:42 +0000
Subject: [Koha-devel] Koha misc4dev
Message-ID: <CAJzKNY5WTwfdPiTQnYkcjQjoggaZBnMUZYK+U8vS_gjTHEfPjQ@mail.gmail.com>

Hi devs,

Just to let you know that I have created a new repo for handy scripts I use
everyday.
A couple of weeks ago I decided to submit stuffs on bugzilla to have more
scripts in the misc/devel directory.
But actually it takes me too much time trying to integrate them into the
Koha codebase (I always need to apply my patches locally when I need them,
fix conflicts, etc.)

I have closed these 2 bugs:
   Bug 17529 - Add a --with-records option to populate_db.pl
   Bug 17534 - Press a button and get a fresh DB
And move these changes outside of bugzilla.
I prefer to create my own repo, it will be easier and quicker to maintain.
You can have a look on https://github.com/joubu/koha-misc4dev
It just does a few stuffs so far:
- populate the DB with all sample data
- create a superlibrarian user
- insert some data (this is new):
    * insert records
    * insert a default circ rule
    * configure the self registration and self-checkout features
    * insert acquisition data (budget, fund, vendor and basket)
- rebuild zebra

I should not have submitted populate_db.pl and create_superlibrarian.pl,
but they have already been backported to stable so it seems easier to let
them in the Koha codebase.

Feel free to fork or pull request!

Cheers,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161111/cfae9782/attachment.html>

From tomascohen at gmail.com  Sun Nov 13 15:26:17 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Sun, 13 Nov 2016 14:26:17 +0000
Subject: [Koha-devel] KohaDevBox and Xenial
Message-ID: <CABZfb=XxUhDG3AGDgTNyqieRPXR-2-AN2FkFgQZte_A4UtdHmA@mail.gmail.com>

Hi everyone, recently I changed the Xenial box that KohaDevBox has
configured. But it seems I didn't find (yet) the right box. I managed to
have it working by upgrading to Virtualbox 5.1, and using the latest
Vagrant from their site (1.8.7).
If you find a better packaged Xenial image, please let me know, or fill an
issue to talk about it on KohaDevBox's github site.
-- 
Tom?s Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161113/d6b36bc9/attachment.html>

From rsantellan at gmail.com  Mon Nov 14 13:50:10 2016
From: rsantellan at gmail.com (Rodrigo Santellan)
Date: Mon, 14 Nov 2016 09:50:10 -0300
Subject: [Koha-devel] KohaDevBox and Xenial
In-Reply-To: <CABZfb=XxUhDG3AGDgTNyqieRPXR-2-AN2FkFgQZte_A4UtdHmA@mail.gmail.com>
References: <CABZfb=XxUhDG3AGDgTNyqieRPXR-2-AN2FkFgQZte_A4UtdHmA@mail.gmail.com>
Message-ID: <CABndEwSA9NR-qm-q0=UJz6prdwfNZQG9LJJ47+oEKVm3mMBnwQ@mail.gmail.com>

Thomas,

Have you try "bento/ubuntu-16.04" for me was the only Xenial that had
worked.

Regards!

On Sun, Nov 13, 2016 at 11:26 AM, Tomas Cohen Arazi <tomascohen at gmail.com>
wrote:

> Hi everyone, recently I changed the Xenial box that KohaDevBox has
> configured. But it seems I didn't find (yet) the right box. I managed to
> have it working by upgrading to Virtualbox 5.1, and using the latest
> Vagrant from their site (1.8.7).
> If you find a better packaged Xenial image, please let me know, or fill an
> issue to talk about it on KohaDevBox's github site.
> --
> Tom?s Cohen Arazi
> Theke Solutions (https://theke.io <http://theke.io/>)
> ? +54 9351 3513384
> GPG: B2F3C15F
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161114/ebd25530/attachment.html>

From jonathan.druart at bugs.koha-community.org  Tue Nov 15 09:58:19 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Tue, 15 Nov 2016 08:58:19 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
Message-ID: <CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>

I have opened bug 17626 and attached a patch.
I have removed all the INSTALL.distri files and replace the content of
INSTALL with 3 links to the wiki:
- koha on ubuntu - packages
- koha on debian
- a link to kohadevbox for developers
Feel free to provide a more complete patch if you like.

Cheers,
Jonathan

On Thu, 12 Nov 2015 at 11:06 Jonathan Druart <
jonathan.druart at bugs.koha-community.org> wrote:

> 2015-11-11 22:37 GMT+00:00 Robin Sheat <robin at catalyst.net.nz>:
> > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
> >> I followed the official instructions:
> >>
> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
> >
> > We need to delete those, they're from 2012 and are super out of date.
>
> Shall we 1) delete them, 2)replace them with the content of the wiki
> page or 3) just put a link to the wiki page?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/58503820/attachment.html>

From jonathan.druart at bugs.koha-community.org  Tue Nov 15 10:08:09 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Tue, 15 Nov 2016 09:08:09 +0000
Subject: [Koha-devel] What's on in Koha devel #7
Message-ID: <CAJzKNY5bU6AA5hPYjaV9w1NiYn1KHVpTtt=VZQC44JZJNhDoMg@mail.gmail.com>

Hello librarians and developers,

Koha 16.11 will be released soon, in 1 week only (November 22nd). We are
entering the string freeze which means that only bug fixes without string
changes will get pushed.

But developers are already focused on 16.12, the next development version :)
Note that we have a blocker (for the release) and we should get a signoff
on it ASAP, see bug 17522.

= Refactoring =
I have continued to move the C4::Members code to the Koha namespace. It's
quite easy code and so easy to rewrite, but I tried to cut it into small
chunks of code and it's very hard to create a tree of bug dependencies.
You can help me testing the orange boxes of this dependency graph:
https://bugs.koha-community.org/bugzilla3/showdependencygraph.cgi?id=16846
(scroll to the right!)

The shifting of the biblioitems.marcxml field to another table (bug 17196)
is still in the needs sign off queue.

= Elastic search =
We are adapting our code to the new 2.4 version of Elastic search, see bug
17255.
This can be tested on kohadevbox (Search for "elasticsearch_version" in the
README file)

= Developer tools =
== KohaDevBox ==
KohaDevBox 2.0 has been released. It now works under Windows and Mac OS.
See the announcement on koha-devel:
http://lists.koha-community.org/pipermail/koha-devel/2016-November/043272.html
Thanks Tomas for the great work!

== Koha misc4dev ==
I will maintain an external repository where I will write some misc for
dev. The goal is to provide useful scripts to fill the database with extra
data, auto configure features,etc. See the announcement on koha-devel:
http://lists.koha-community.org/pipermail/koha-devel/2016-November/043277.html


The next dev meeting is on December 14th
https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_December_2016
13UTC.
You can still fill the poll to find the best 2 slots for dev meetings:
https://framadate.org/3dAEB8zqQLzzTptD

Cheers,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/66695ad4/attachment.html>

From fridolin.somers at biblibre.com  Tue Nov 15 12:24:34 2016
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Tue, 15 Nov 2016 12:24:34 +0100
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
Message-ID: <560b8a31-8f7a-f0f0-d567-3a232a8ce47f@biblibre.com>

+1

Le 15/11/2016 ? 09:58, Jonathan Druart a ?crit :
> I have opened bug 17626 and attached a patch.
> I have removed all the INSTALL.distri files and replace the content of
> INSTALL with 3 links to the wiki:
> - koha on ubuntu - packages
> - koha on debian
> - a link to kohadevbox for developers
> Feel free to provide a more complete patch if you like.
>
> Cheers,
> Jonathan
>
> On Thu, 12 Nov 2015 at 11:06 Jonathan Druart <
> jonathan.druart at bugs.koha-community.org> wrote:
>
>> 2015-11-11 22:37 GMT+00:00 Robin Sheat <robin at catalyst.net.nz>:
>>> Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
>>>> I followed the official instructions:
>>>>
>> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
>>>
>>> We need to delete those, they're from 2012 and are super out of date.
>>
>> Shall we 1) delete them, 2)replace them with the content of the wiki
>> page or 3) just put a link to the wiki page?
>>
>
>
>
> _______________________________________________
> 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/
>

-- 
Fridolin SOMERS
Biblibre - P?les support et syst?me
fridolin.somers at biblibre.com

From mtompset at hotmail.com  Tue Nov 15 14:31:45 2016
From: mtompset at hotmail.com (Mark Tompsett)
Date: Tue, 15 Nov 2016 13:31:45 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
Message-ID: <BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>

Greetings,

While I agree with the concept, and probably should be done, I have one concern.

The problem is, this moves us more towards being Debianist. We do need instructions to install from source, particularly for those of non-Debian distributions (e.g. RedHat, Fedora, CentOS, etc.). Failure to accommodate reduces the freedom.

GPML,
Mark Tompsett

From: Jonathan Druart<mailto:jonathan.druart at bugs.koha-community.org>
Sent: Tuesday, November 15, 2016 3:58 AM
To: koha-devel at lists.koha-community.org<mailto:koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] INSTALL.debian is outdated

I have opened bug 17626 and attached a patch.
I have removed all the INSTALL.distri files and replace the content of INSTALL with 3 links to the wiki:
- koha on ubuntu - packages
- koha on debian
- a link to kohadevbox for developers
Feel free to provide a more complete patch if you like.

Cheers,
Jonathan

On Thu, 12 Nov 2015 at 11:06 Jonathan Druart <jonathan.druart at bugs.koha-community.org<mailto:jonathan.druart at bugs.koha-community.org>> wrote:
2015-11-11 22:37 GMT+00:00 Robin Sheat <robin at catalyst.net.nz<mailto:robin at catalyst.net.nz>>:
> Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
>> I followed the official instructions:
>> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
>
> We need to delete those, they're from 2012 and are super out of date.

Shall we 1) delete them, 2)replace them with the content of the wiki
page or 3) just put a link to the wiki page?

________________________________
_______________________________________________
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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/9103379c/attachment.html>

From jonathan.druart at bugs.koha-community.org  Tue Nov 15 15:29:17 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Tue, 15 Nov 2016 14:29:17 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CAJzKNY5Jg9o_aEvZ4L5uhTGBLBN5ZJDEU9U7viZaxVH1k8_1yA@mail.gmail.com>

I totally agree, thanks to volunteer! :)

On Tue, 15 Nov 2016 at 14:31 Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> While I agree with the concept, and probably should be done, I have one
> concern.
>
> The problem is, this moves us more towards being Debianist. We do need
> instructions to install from source, particularly for those of non-Debian
> distributions (e.g. RedHat, Fedora, CentOS, etc.). Failure to accommodate
> reduces the freedom.
>
> GPML,
> Mark Tompsett
>
> *From:* Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> *Sent:* Tuesday, November 15, 2016 3:58 AM
> *To:* koha-devel at lists.koha-community.org
> *Subject:* Re: [Koha-devel] INSTALL.debian is outdated
>
> I have opened bug 17626 and attached a patch.
> I have removed all the INSTALL.distri files and replace the content of
> INSTALL with 3 links to the wiki:
> - koha on ubuntu - packages
> - koha on debian
> - a link to kohadevbox for developers
> Feel free to provide a more complete patch if you like.
>
> Cheers,
> Jonathan
>
> On Thu, 12 Nov 2015 at 11:06 Jonathan Druart <
> jonathan.druart at bugs.koha-community.org> wrote:
>
> 2015-11-11 22:37 GMT+00:00 Robin Sheat <robin at catalyst.net.nz>:
> > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
> >> I followed the official instructions:
> >>
> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
> >
> > We need to delete those, they're from 2012 and are super out of date.
>
> Shall we 1) delete them, 2)replace them with the content of the wiki
> page or 3) just put a link to the wiki page?
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/c5de3d1e/attachment-0001.html>

From martin.renvoize at ptfs-europe.com  Tue Nov 15 15:29:17 2016
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Tue, 15 Nov 2016 14:29:17 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>

+1 to this cleanup, and also to a link to 'installing from source'.. though
which version of that is most up to date is a mystery to me.

*Martin Renvoize*

Development Manager




*T:* +44 (0) 1483 378728

*F:* +44 (0) 800 756 6384

*E:* martin.renvoize at ptfs-europe.com

www.ptfs-europe.com



<https://www.ptfs-europe.com>



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

The information contained in this email message may be privileged,
confidential and protected from disclosure. If you are not the intended
recipient, any dissemination, distribution or copying is strictly
prohibited. If you think that you have received this email message in
error, please email the sender at info at ptfs-europe.com


On 15 November 2016 at 13:31, Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> While I agree with the concept, and probably should be done, I have one
> concern.
>
> The problem is, this moves us more towards being Debianist. We do need
> instructions to install from source, particularly for those of non-Debian
> distributions (e.g. RedHat, Fedora, CentOS, etc.). Failure to accommodate
> reduces the freedom.
>
> GPML,
> Mark Tompsett
>
> *From:* Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> *Sent:* Tuesday, November 15, 2016 3:58 AM
> *To:* koha-devel at lists.koha-community.org
> *Subject:* Re: [Koha-devel] INSTALL.debian is outdated
>
> I have opened bug 17626 and attached a patch.
> I have removed all the INSTALL.distri files and replace the content of
> INSTALL with 3 links to the wiki:
> - koha on ubuntu - packages
> - koha on debian
> - a link to kohadevbox for developers
> Feel free to provide a more complete patch if you like.
>
> Cheers,
> Jonathan
>
> On Thu, 12 Nov 2015 at 11:06 Jonathan Druart <jonathan.druart at bugs.koha-
> community.org> wrote:
>
>> 2015-11-11 22:37 GMT+00:00 Robin Sheat <robin at catalyst.net.nz>:
>> > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
>> >> I followed the official instructions:
>> >> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=
>> INSTALL.debian;hb=HEAD
>> >
>> > We need to delete those, they're from 2012 and are super out of date.
>>
>> Shall we 1) delete them, 2)replace them with the content of the wiki
>> page or 3) just put a link to the wiki page?
>>
> ------------------------------
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/ee3b5d7f/attachment.html>

From mtompset at hotmail.com  Tue Nov 15 18:51:25 2016
From: mtompset at hotmail.com (Mark Tompsett)
Date: Tue, 15 Nov 2016 17:51:25 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>
Message-ID: <BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>

Greetings,

Renvoize, Martin<mailto:martin.renvoize at ptfs-europe.com> wrote:
>
+1 to this cleanup, and also to a link to 'installing from source'.
> [T]hough which version of that is most up to date is a mystery to me.

And that is why Jonathan jokingly suggested that if the issue is near and dear to my heart he was glad I volunteered to clean up a single source install related page. Sadly, I would rather refactor Koha such that default CentOS, Fedora, and/or Red Hat installs would work. The PDF libraries are a mess, and a part of this problem. And it should be noted, still not volunteering now, but may in the future ? no promises (insert Candi?s Love Makes No Promises musical flashback).

GPML,
Mark Tompsett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161115/79b5a1d0/attachment.html>

From kohanews at gmail.com  Wed Nov 16 17:56:38 2016
From: kohanews at gmail.com (kohanews)
Date: Wed, 16 Nov 2016 08:56:38 -0800
Subject: [Koha-devel] Call for news: November 2016 Newsletter
Message-ID: <6d9a5979-e714-a8ec-4f63-2b3d3a422d8e@gmail.com>

Fellow Koha users ~

I'm collecting news for the November 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 kyle.m.hall at gmail.com  Thu Nov 17 18:40:09 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Thu, 17 Nov 2016 12:40:09 -0500
Subject: [Koha-devel] Koha 16.11 Release Notes ( 2nd Draft )
In-Reply-To: <bd07961d-5161-1662-b403-52eca3c423f1@web.de>
References: <CACpVHfy2KAeSemEQsrruzt+WpRbXREDvgpcW=2Fw0vyX_W8SCQ@mail.gmail.com>
	<CACpVHfz+-b25W5NygTowPeYrMGuDr=dak5KDW-Top4Z1Tg8HcQ@mail.gmail.com>
	<bd07961d-5161-1662-b403-52eca3c423f1@web.de>
Message-ID: <CACpVHfyYkVB3FFGJy3tV8x-yxrL=0WVsh4Qcdq90jdYYEkj-4A@mail.gmail.com>

I'll try to remember to do that for the final draft!

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Fri, Nov 11, 2016 at 12:46 AM, Katrin <katrin.fischer.83 at web.de> wrote:

> I changed them all to 'new feature' on bugzilla now too, so they will move
> into place automatically next run.
>
> The paragraph: "It will be possible to send order information to the
> vendor by e-mail. For now this feature can be triggered manually with a
> button before closing the basket. The order e-mail is based on the
> acquisition claim feature, but uses a new notice template: ACQORDER." on
> top of acquisitions belongs to bug 5260
>
> Should we try and add short descriptions to the other new features in
> bugzilla too?
>
> Katrin
> On 11.11.2016 04:20, Kyle Hall wrote:
>
> I've already noticed the "new feature" count is off. I'll fix that in the
> next revision.
>
> Kyle
>
>
> <https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
> On Thu, Nov 10, 2016 at 10:18 PM, Kyle Hall <kyle.m.hall at gmail.com> wrote:
>
>> Hey All!
>>
>> Here is the second draft of the release notes for Koha 16.11!
>>
>> Additional bugs pushed since then have been added and I've made some
>> manual changes based on feedback kindly made by Katrin. Thanks Katrin!
>>
>> The HTML is attached, and you can find them on GitHub here
>> <https://github.com/kylemhall/Koha/commits/rel16_11_00_release_notes_draft_2>
>> .
>>
>> Kyle
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161117/74a2b0ac/attachment.html>

From chrisc at catalyst.net.nz  Thu Nov 17 19:20:15 2016
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Fri, 18 Nov 2016 07:20:15 +1300
Subject: [Koha-devel] Koha 16.11 Release Notes ( 2nd Draft )
In-Reply-To: <CACpVHfyYkVB3FFGJy3tV8x-yxrL=0WVsh4Qcdq90jdYYEkj-4A@mail.gmail.com>
References: <CACpVHfy2KAeSemEQsrruzt+WpRbXREDvgpcW=2Fw0vyX_W8SCQ@mail.gmail.com>
	<CACpVHfz+-b25W5NygTowPeYrMGuDr=dak5KDW-Top4Z1Tg8HcQ@mail.gmail.com>
	<bd07961d-5161-1662-b403-52eca3c423f1@web.de>
	<CACpVHfyYkVB3FFGJy3tV8x-yxrL=0WVsh4Qcdq90jdYYEkj-4A@mail.gmail.com>
Message-ID: <5588708B-776C-42F7-BB6D-4EFF7EF4EDAA@catalyst.net.nz>

I'll try to update the manual to match too.

But any help is appreciated, if people want they can check out the sphinx branch from git.koha-community.org/kohadocs.git

The files to change live in en/source and have .rst endings. Patches happily accepted.

Or if it is easier, I also accept merge requests at https://gitlab.com/koha-community-devs-users/kohadocs/

Again to the sphinx branch. 

I will move the branches around post the release and send another email but for now please send any changes you have. Everything is gratefully received

Chris

On 18 November 2016 6:40:09 AM NZDT, Kyle Hall <kyle.m.hall at gmail.com> wrote:
>I'll try to remember to do that for the final draft!
>
>Kyle
>
><https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>
>http://www.kylehall.info
>ByWater Solutions ( http://bywatersolutions.com )
>Meadville Public Library ( http://www.meadvillelibrary.org )
>Crawford County Federated Library System ( http://www.ccfls.org )
>
>On Fri, Nov 11, 2016 at 12:46 AM, Katrin <katrin.fischer.83 at web.de>
>wrote:
>
>> I changed them all to 'new feature' on bugzilla now too, so they will
>move
>> into place automatically next run.
>>
>> The paragraph: "It will be possible to send order information to the
>> vendor by e-mail. For now this feature can be triggered manually with
>a
>> button before closing the basket. The order e-mail is based on the
>> acquisition claim feature, but uses a new notice template: ACQORDER."
>on
>> top of acquisitions belongs to bug 5260
>>
>> Should we try and add short descriptions to the other new features in
>> bugzilla too?
>>
>> Katrin
>> On 11.11.2016 04:20, Kyle Hall wrote:
>>
>> I've already noticed the "new feature" count is off. I'll fix that in
>the
>> next revision.
>>
>> Kyle
>>
>>
>>
><https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>>
>> On Thu, Nov 10, 2016 at 10:18 PM, Kyle Hall <kyle.m.hall at gmail.com>
>wrote:
>>
>>> Hey All!
>>>
>>> Here is the second draft of the release notes for Koha 16.11!
>>>
>>> Additional bugs pushed since then have been added and I've made some
>>> manual changes based on feedback kindly made by Katrin. Thanks
>Katrin!
>>>
>>> The HTML is attached, and you can find them on GitHub here
>>>
><https://github.com/kylemhall/Koha/commits/rel16_11_00_release_notes_draft_2>
>>> .
>>>
>>> Kyle
>>>
>>> http://www.kylehall.info
>>> ByWater Solutions ( http://bywatersolutions.com )
>>> Meadville Public Library ( http://www.meadvillelibrary.org )
>>> Crawford County Federated Library System ( http://www.ccfls.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/

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161118/0ffff0b0/attachment.html>

From roger.grossmann at lmscloud.de  Fri Nov 18 16:12:02 2016
From: roger.grossmann at lmscloud.de (Roger Grossmann)
Date: Fri, 18 Nov 2016 16:12:02 +0100
Subject: [Koha-devel] Questions regarding localization
Message-ID: <16CC5887-3414-4B4C-96FD-B408FDE39655@lmscloud.de>

Hi all,

as a Koha development newbie I am having a few questions especially with localization. 
I am developing enhancements which I plan to bring in to the community hopefully soon. Your answers will help to make progress with it.

1st question
----------------
After looking at much Koha code I did not find a solution to build server side localized strings to persist localized text in the database. 
What do you recommend to use here?

Background: 
As you know, fines and fees are a sensitive area. Borrowers like to know exactly why they are charged and for what exactly. 
Lets assume, you want to store good localized name for the type of an overdue fine. 
It was for instance planned for function "UpdateFine" in C4::Overdues but the parameter $type is never filled as originally planned.
If an additional type name would be passed here, it needed to be a localized string since borrowers want to read the charge reason in their language.
As this is just an example for the use of a localized server text, the question is, whether there is already an approach to manage localised server side texts.
Ideally, server side texts would support parameter replacement that is not dependent of the position in the text as for instance with %s using sprintf.

2nd question
-----------------
I want to build some new UI functionality. The procedure how to do that with templates in english first is clear to me.
As I am German, I would like to build during development a first German version of the template as well and would like to extend the related German .po file.
How can I add the texts for a specific language in my development environment? 
Is there a way to extract the new texts of templates and add them to an existing .po file with a script and use poedit to translate them?
How do you do that?

Thanks in advance for your help.

Best regards,
Roger


--
Roger Gro?mann
LMSCloud GmbH
Konrad-Zuse-Platz 8 - D-81829 M?nchen
t +49 (0)89 207042-620  m +49 (0)171-2194775 f +49 (0)89 207042-623
e roger.grossmann at lmscloud.de
w www.lmscloud.de


From mtompset at hotmail.com  Mon Nov 21 20:28:16 2016
From: mtompset at hotmail.com (Mark Tompsett)
Date: Mon, 21 Nov 2016 19:28:16 +0000
Subject: [Koha-devel] Failed QA number over 200.
Message-ID: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>

Greetings,

The number of Failed QA?s has significantly grown in the last few months. And while this is a good problem (congrats QA Team), perhaps there are some that should be either closed or revisited. I just dealt with one of mine, after a long while, and I?m wondering if others have accidentally forgotten theirs as well.

GPML,
Mark Tompsett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161121/8269dc04/attachment.html>

From katrin.fischer.83 at web.de  Mon Nov 21 22:40:27 2016
From: katrin.fischer.83 at web.de (Katrin)
Date: Mon, 21 Nov 2016 22:40:27 +0100
Subject: [Koha-devel] Questions regarding localization
In-Reply-To: <16CC5887-3414-4B4C-96FD-B408FDE39655@lmscloud.de>
References: <16CC5887-3414-4B4C-96FD-B408FDE39655@lmscloud.de>
Message-ID: <995a239d-dca5-bc62-a819-a8d6e0fd2215@web.de>

Hi Roger,

strings in Koha are either stored in the database (authorised values, 
item type descriptions, MARC field and subfield descriptions, etc.) or 
are part of the templates.

Strings in the templates are translated via the po files you have 
already seen. They are updated pre-release using the translation scripts 
- no manual editing is required. I think on the packages it works with: 
sudo koha-translate -u <langcode>. Or in koha-shell: cd misc translator, 
perl translate update <langcode>. TT variables will be automatically 
replaced by %s. For JavaScript there is a special syntax you can use 
that has the same effect.

You can find additional information about the translation process on the 
wiki:

https://wiki.koha-community.org/wiki/Translating_Koha
https://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client

There are also some coding guidelines concerning translation:

https://wiki.koha-community.org/wiki/Coding_Guidelines

As you have written the $type parameter is currently not used. The 
different fines and fees are differentiated in the database by their 
accounttype in accountlines. The code is translated into a description 
in the templates, which means there can be a translation for every 
installed language.

Hope this helps,

Katrin

On 18.11.2016 16:12, Roger Grossmann wrote:
> Hi all,
>
> as a Koha development newbie I am having a few questions especially with localization.
> I am developing enhancements which I plan to bring in to the community hopefully soon. Your answers will help to make progress with it.
>
> 1st question
> ----------------
> After looking at much Koha code I did not find a solution to build server side localized strings to persist localized text in the database.
> What do you recommend to use here?
>
> Background:
> As you know, fines and fees are a sensitive area. Borrowers like to know exactly why they are charged and for what exactly.
> Lets assume, you want to store good localized name for the type of an overdue fine.
> It was for instance planned for function "UpdateFine" in C4::Overdues but the parameter $type is never filled as originally planned.
> If an additional type name would be passed here, it needed to be a localized string since borrowers want to read the charge reason in their language.
> As this is just an example for the use of a localized server text, the question is, whether there is already an approach to manage localised server side texts.
> Ideally, server side texts would support parameter replacement that is not dependent of the position in the text as for instance with %s using sprintf.
>
> 2nd question
> -----------------
> I want to build some new UI functionality. The procedure how to do that with templates in english first is clear to me.
> As I am German, I would like to build during development a first German version of the template as well and would like to extend the related German .po file.
> How can I add the texts for a specific language in my development environment?
> Is there a way to extract the new texts of templates and add them to an existing .po file with a script and use poedit to translate them?
> How do you do that?
>
> Thanks in advance for your help.
>
> Best regards,
> Roger
>
>
> --
> Roger Gro?mann
> LMSCloud GmbH
> Konrad-Zuse-Platz 8 - D-81829 M?nchen
> t +49 (0)89 207042-620  m +49 (0)171-2194775 f +49 (0)89 207042-623
> e roger.grossmann at lmscloud.de
> w www.lmscloud.de
>
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161121/f0e8975e/attachment.html>

From paul.poulain at biblibre.com  Tue Nov 22 13:37:00 2016
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 22 Nov 2016 13:37:00 +0100
Subject: [Koha-devel] Next hackfestv(2017) in Marseille, proposed dates
Message-ID: <b2469a05-9bca-b79e-d45d-597aa606b770@biblibre.com>

Hello,

I'm planning to switch back to march for the Hackfest in Marseille. What 
about Week #11 (march 20th-24th) or #12 (march 27th-31th) ? Any problem 
or collisions with those dates ?


-- 
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 paul.poulain at biblibre.com  Tue Nov 22 15:17:23 2016
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 22 Nov 2016 15:17:23 +0100
Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin
Message-ID: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>

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)


-- 
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 arthur.suzuki at univ-lyon3.fr  Tue Nov 22 15:49:48 2016
From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur)
Date: Tue, 22 Nov 2016 15:49:48 +0100
Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin
In-Reply-To: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>
References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>
Message-ID: <b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>

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


From arthur.suzuki at univ-lyon3.fr  Tue Nov 22 16:07:27 2016
From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur)
Date: Tue, 22 Nov 2016 16:07:27 +0100
Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin
In-Reply-To: <b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>
References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>
	<b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>
Message-ID: <60c9ba23-5c6f-7a01-2ab9-9441d1467895@univ-lyon3.fr>

Also, I've just noticed that EDS Plugin doesn't work with Koha:master:

https://github.com/ebsco/edsapi-koha-plugin/issues/15


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


From paul.poulain at biblibre.com  Tue Nov 22 16:12:20 2016
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 22 Nov 2016 16:12:20 +0100
Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin
In-Reply-To: <b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>
References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>
	<b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>
Message-ID: <c1723cc0-086a-5b9d-683e-71da2c2a18f1@biblibre.com>

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)
>>
>>
>

-- 
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 arthur.suzuki at univ-lyon3.fr  Tue Nov 22 16:33:51 2016
From: arthur.suzuki at univ-lyon3.fr (SUZUKI Arthur)
Date: Tue, 22 Nov 2016 16:33:51 +0100
Subject: [Koha-devel] Koha 3.22, Plack & EDS plugin
In-Reply-To: <c1723cc0-086a-5b9d-683e-71da2c2a18f1@biblibre.com>
References: <538c2d8f-866a-1d24-a7a7-bb80c752e4a2@biblibre.com>
	<b6f67db6-e420-8510-d9ea-82a07391ad22@univ-lyon3.fr>
	<c1723cc0-086a-5b9d-683e-71da2c2a18f1@biblibre.com>
Message-ID: <fb2efeaf-f837-7ef3-2555-4c26f633be8a@univ-lyon3.fr>

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


From rsantellan at gmail.com  Tue Nov 22 19:58:30 2016
From: rsantellan at gmail.com (Rodrigo Santellan)
Date: Tue, 22 Nov 2016 15:58:30 -0300
Subject: [Koha-devel] OAI-PMH filter data
Message-ID: <CABndEwQuYtwu0YeXBD_gFiRs+wJOu5cbEAAkmqFzrj0q1o9g8A@mail.gmail.com>

Hi,

I been reading about how to connect with the OAI protocol. My problem is
that I want to publish only a result set of data, per example only the
biblios that are on a specific framework with and author starting with a
specific letter.

I look on the OAI pages and there is nothing like that, and the google
group is almost dead. Does anybody can give me a clue for where to start
looking to accomplish that?

I believe could be a nice resource to add to the wiki!

Regards and thanks for any help!

Rodrigo Santellan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161122/91a3d8cd/attachment.html>

From tomascohen at gmail.com  Wed Nov 23 10:12:52 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Wed, 23 Nov 2016 09:12:52 +0000
Subject: [Koha-devel] OAI-PMH filter data
In-Reply-To: <CABndEwQuYtwu0YeXBD_gFiRs+wJOu5cbEAAkmqFzrj0q1o9g8A@mail.gmail.com>
References: <CABndEwQuYtwu0YeXBD_gFiRs+wJOu5cbEAAkmqFzrj0q1o9g8A@mail.gmail.com>
Message-ID: <CABZfb=XG=FUxCz=T+WxOd=cmMB84PBvqBmpCnoEbiQkmOny7kw@mail.gmail.com>

Look at the 'OAI sets' section in the admin page. In Koha of course.

El mar., 22 de nov. de 2016 3:58 PM, Rodrigo Santellan <rsantellan at gmail.com>
escribi?:

> Hi,
>
> I been reading about how to connect with the OAI protocol. My problem is
> that I want to publish only a result set of data, per example only the
> biblios that are on a specific framework with and author starting with a
> specific letter.
>
> I look on the OAI pages and there is nothing like that, and the google
> group is almost dead. Does anybody can give me a clue for where to start
> looking to accomplish that?
>
> I believe could be a nice resource to add to the wiki!
>
> Regards and thanks for any help!
>
> Rodrigo Santellan
> _______________________________________________
> 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 <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/ab5dc021/attachment-0001.html>

From kyle.m.hall at gmail.com  Wed Nov 23 11:54:05 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Wed, 23 Nov 2016 05:54:05 -0500
Subject: [Koha-devel] Koha 16.11.00 released!
In-Reply-To: <CACpVHfwo32Y5UKng51Zd880PM-n=3_-aj95cHiU=j0RhkBW7rQ@mail.gmail.com>
References: <CACpVHfwo32Y5UKng51Zd880PM-n=3_-aj95cHiU=j0RhkBW7rQ@mail.gmail.com>
Message-ID: <CACpVHfy6CTXpo4CdcR5nzSS4vXgddquYKpq2hbR9jzvVGGqAKw@mail.gmail.com>

Here is a link to the original text version, as I've been told that my
attachment has been stripped out!

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Tue, Nov 22, 2016 at 2:05 PM, Kyle Hall <kyle.m.hall at gmail.com> wrote:

> It is my great pleasure to announce the release of Koha 16.11.00!
>
> Thanks be to everyone involved in getting 16.11 out the door!
>
> Attached are the release notes.
>
> Kyle
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/530fe0e9/attachment.html>

From kyle.m.hall at gmail.com  Wed Nov 23 11:54:29 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Wed, 23 Nov 2016 05:54:29 -0500
Subject: [Koha-devel] Koha 16.11.00 released!
In-Reply-To: <CACpVHfy6CTXpo4CdcR5nzSS4vXgddquYKpq2hbR9jzvVGGqAKw@mail.gmail.com>
References: <CACpVHfwo32Y5UKng51Zd880PM-n=3_-aj95cHiU=j0RhkBW7rQ@mail.gmail.com>
	<CACpVHfy6CTXpo4CdcR5nzSS4vXgddquYKpq2hbR9jzvVGGqAKw@mail.gmail.com>
Message-ID: <CACpVHfztPj=TEsY7pQaUTyEvrB6GsseF+9bE9wfevCn0+pd6oQ@mail.gmail.com>

Here is a link to the original text version, as I've been told that my
attachment has been stripped out!

http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=misc/release_notes/release_notes_16_11_00.md;hb=HEAD

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Wed, Nov 23, 2016 at 5:54 AM, Kyle Hall <kyle.m.hall at gmail.com> wrote:

> Here is a link to the original text version, as I've been told that my
> attachment has been stripped out!
>
> Kyle
>
>
> <https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
> On Tue, Nov 22, 2016 at 2:05 PM, Kyle Hall <kyle.m.hall at gmail.com> wrote:
>
>> It is my great pleasure to announce the release of Koha 16.11.00!
>>
>> Thanks be to everyone involved in getting 16.11 out the door!
>>
>> Attached are the release notes.
>>
>> Kyle
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/e247dd12/attachment.html>

From kyle.m.hall at gmail.com  Wed Nov 23 11:59:01 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Wed, 23 Nov 2016 05:59:01 -0500
Subject: [Koha-devel] Failed QA number over 200.
In-Reply-To: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CACpVHfzirws45Wo=nQTgZ-3rE19CK6BSdh96g47nGkv4YqYkjw@mail.gmail.com>

I agree. I know I have many failed qa bugs, some of which are still works
in progress, but others that are years out of date and should be closed or
dealt with otherwise.

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Mon, Nov 21, 2016 at 2:28 PM, Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> The number of Failed QA?s has significantly grown in the last few months.
> And while this is a good problem (congrats QA Team), perhaps there are some
> that should be either closed or revisited. I just dealt with one of mine,
> after a long while, and I?m wondering if others have accidentally forgotten
> theirs as well.
>
> GPML,
> Mark Tompsett
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/f871474f/attachment.html>

From hagud at orex.es  Wed Nov 23 11:59:05 2016
From: hagud at orex.es (Hugo Agud)
Date: Wed, 23 Nov 2016 11:59:05 +0100
Subject: [Koha-devel] [Koha] Koha 16.11.00 released!
In-Reply-To: <CACpVHfztPj=TEsY7pQaUTyEvrB6GsseF+9bE9wfevCn0+pd6oQ@mail.gmail.com>
References: <CACpVHfwo32Y5UKng51Zd880PM-n=3_-aj95cHiU=j0RhkBW7rQ@mail.gmail.com>
	<CACpVHfy6CTXpo4CdcR5nzSS4vXgddquYKpq2hbR9jzvVGGqAKw@mail.gmail.com>
	<CACpVHfztPj=TEsY7pQaUTyEvrB6GsseF+9bE9wfevCn0+pd6oQ@mail.gmail.com>
Message-ID: <CADT_QRQ+EcLfmBf=_ZAnhtAk+MwuhZG=MkR_MFww9vvcP4TMGA@mail.gmail.com>

Great work! thanks a lot to all

2016-11-23 11:54 GMT+01:00 Kyle Hall <kyle.m.hall at gmail.com>:

> Here is a link to the original text version, as I've been told that my
> attachment has been stripped out!
>
> http://git.koha-community.org/gitweb/?p=koha.git;a=blob_
> plain;f=misc/release_notes/release_notes_16_11_00.md;hb=HEAD
>
> Kyle
>
> <https://secure2.convio.net/cffh/site/Donation2?df_id=
> 1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.
> donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
> On Wed, Nov 23, 2016 at 5:54 AM, Kyle Hall <kyle.m.hall at gmail.com> wrote:
>
> > Here is a link to the original text version, as I've been told that my
> > attachment has been stripped out!
> >
> > Kyle
> >
> >
> > <https://secure2.convio.net/cffh/site/Donation2?df_id=
> 1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.
> donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
> >
> > http://www.kylehall.info
> > ByWater Solutions ( http://bywatersolutions.com )
> > Meadville Public Library ( http://www.meadvillelibrary.org )
> > Crawford County Federated Library System ( http://www.ccfls.org )
> >
> > On Tue, Nov 22, 2016 at 2:05 PM, Kyle Hall <kyle.m.hall at gmail.com>
> wrote:
> >
> >> It is my great pleasure to announce the release of Koha 16.11.00!
> >>
> >> Thanks be to everyone involved in getting 16.11 out the door!
> >>
> >> Attached are the release notes.
> >>
> >> Kyle
> >>
> >> http://www.kylehall.info
> >> ByWater Solutions ( http://bywatersolutions.com )
> >> Meadville Public Library ( http://www.meadvillelibrary.org )
> >> Crawford County Federated Library System ( http://www.ccfls.org )
> >>
> >
> >
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 

*Hugo Agud - Orex Digital *

*www.orex.es <http://www.orex.es>*


<http://www.orex.es/>    [image: www.orex.es/koha] <http://www.orex.es/koha>
   [image: www.orex.es/vufind] <http://www.orex.es/vufind>
<http://www.orex.es/omeka>


Director

Calle Sant Joaquin,117, 2?-3? ? 08922 Santa Coloma de Gramanet - Tel: 933
856 138   hagud at orex.es ? http://www.orex.es/



No imprima este mensaje a no ser que sea necesario. Una tonelada de papel
implica la tala de 15 ?rboles y el consumo de 250.000 litros de agua.



Aviso de confidencialidad
Este mensaje contiene informaci?n que puede ser CONFIDENCIAL y/o de USO
RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni
est? autorizado a recibirlo por el remitente), no est? autorizado a copiar,
reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje
por error, por favor, notif?quenoslo inmediatamente y b?rrelo de su sistema.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/17fd48a9/attachment-0001.html>

From gkm at igidr.ac.in  Wed Nov 23 14:25:00 2016
From: gkm at igidr.ac.in (G.K.MANJUNATH)
Date: Wed, 23 Nov 2016 18:55:00 +0530 (India Standard Time)
Subject: [Koha-devel] Extracting sub-title from the field marc in Koha table
	biblioitem.
In-Reply-To: <Pine.WNT.4.64.1610281129240.4064@ManjunathPC>
References: <Pine.WNT.4.64.1610281129240.4064@ManjunathPC>
Message-ID: <Pine.WNT.4.64.1611231830580.2596@ManjunathPC>


dear all,

I refer to an email dated Sept 9, 2013 posted by Mathieu Saby regarding 
storing the sub-title in sql table biblio. I think this genuine 
requirement has not been addressed in the later versions.

However, I would like to know whether there is any way to extract the 
sub-title from the field marc using sql statement ?

I endorse Saby's view that this important information needs to be stored 
in the sql table biblio.

thanks,
       G.K.Manjunath
       Chief Librarian
       Indira Gandhi Inst of Development Research
       Film City Road
       Santosh Nagar
       Goregaon(East )
       MUMBAI - 400 065
       India
                   Phone:        022-28416528
                   email:         gkm at igidr.ac.in

From oleonard at myacpl.org  Wed Nov 23 14:45:41 2016
From: oleonard at myacpl.org (Owen Leonard)
Date: Wed, 23 Nov 2016 08:45:41 -0500
Subject: [Koha-devel] Extracting sub-title from the field marc in Koha
 table biblioitem.
In-Reply-To: <Pine.WNT.4.64.1611231830580.2596@ManjunathPC>
References: <Pine.WNT.4.64.1610281129240.4064@ManjunathPC>
	<Pine.WNT.4.64.1611231830580.2596@ManjunathPC>
Message-ID: <CAO4qe2M8B2t4fLKMShZQcSTTqhFcmP7Br8V4ZC_dSPA6qhDk8A@mail.gmail.com>

> However, I would like to know whether there is any way to extract the
> sub-title from the field marc using sql statement ?

Yes. See this example in the SQL reports library:

https://wiki.koha-community.org/wiki/SQL_Reports_Library#Title.2FSubtitle_List

  -- Owen

-- 
Web Developer
Athens County Public Libraries
http://www.myacpl.org

From gkm at igidr.ac.in  Thu Nov 24 09:32:43 2016
From: gkm at igidr.ac.in (G.K.MANJUNATH)
Date: Thu, 24 Nov 2016 14:02:43 +0530 (India Standard Time)
Subject: [Koha-devel] Extracting sub-title from the field marc in Koha
 table biblioitem.
In-Reply-To: <CAO4qe2M8B2t4fLKMShZQcSTTqhFcmP7Br8V4ZC_dSPA6qhDk8A@mail.gmail.com>
References: <Pine.WNT.4.64.1610281129240.4064@ManjunathPC>
	<Pine.WNT.4.64.1611231830580.2596@ManjunathPC>
	<CAO4qe2M8B2t4fLKMShZQcSTTqhFcmP7Br8V4ZC_dSPA6qhDk8A@mail.gmail.com>
Message-ID: <Pine.WNT.4.64.1611241402370.3264@manjunath-home>


thanks to Owen. It worked.

regards,

g.k.manjunath
igidr, Mumbai



On Wed, 23 Nov 2016, Owen Leonard wrote:

>> However, I would like to know whether there is any way to extract the
>> sub-title from the field marc using sql statement ?
>
> Yes. See this example in the SQL reports library:
>
> https://wiki.koha-community.org/wiki/SQL_Reports_Library#Title.2FSubtitle_List
>
>  -- Owen
>
> -- 
> Web Developer
> Athens County Public Libraries
> http://www.myacpl.org
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>

From jonathan.druart at bugs.koha-community.org  Wed Nov 23 17:47:29 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Wed, 23 Nov 2016 16:47:29 +0000
Subject: [Koha-devel] Failed QA number over 200.
In-Reply-To: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CAJzKNY6+997Rb8uWaBUqvTyubCv9QkO-QyZmD2+=rYa0URNmcA@mail.gmail.com>

Report by assignees:
https://bugs.koha-community.org/bugzilla3/report.cgi?bug_status=Failed%20QA&cumulate=0&x_axis_field=bug_status&y_axis_field=assigned_to&width=1560&height=600&action=wrap&format=table

On Mon, 21 Nov 2016 at 20:28 Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> The number of Failed QA?s has significantly grown in the last few months.
> And while this is a good problem (congrats QA Team), perhaps there are some
> that should be either closed or revisited. I just dealt with one of mine,
> after a long while, and I?m wondering if others have accidentally forgotten
> theirs as well.
>
> GPML,
> Mark Tompsett
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/5e5608a4/attachment.html>

From jonathan.druart at bugs.koha-community.org  Wed Nov 23 17:51:52 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Wed, 23 Nov 2016 16:51:52 +0000
Subject: [Koha-devel] Failed QA number over 200.
In-Reply-To: <CAJzKNY6+997Rb8uWaBUqvTyubCv9QkO-QyZmD2+=rYa0URNmcA@mail.gmail.com>
References: <BY2PR0401MB1752872F27DA8698C590B9DFC6B50@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAJzKNY6+997Rb8uWaBUqvTyubCv9QkO-QyZmD2+=rYa0URNmcA@mail.gmail.com>
Message-ID: <CAJzKNY70wwqC9U52ReYO2cE_S_VCO3GucYbAGH6F3yeQN676kA@mail.gmail.com>

And a more complete one, with other statuses:
https://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=bug_status&y_axis_field=assigned_to&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=In+Discussion&bug_status=Failed+QA&bug_status=Patch+doesn%27t+apply&bug_status=BLOCKED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap

Oops, a bit long :)

On Wed, 23 Nov 2016 at 17:47 Jonathan Druart <
jonathan.druart at bugs.koha-community.org> wrote:

> Report by assignees:
> https://bugs.koha-community.org/bugzilla3/report.cgi?bug_status=Failed%20QA&cumulate=0&x_axis_field=bug_status&y_axis_field=assigned_to&width=1560&height=600&action=wrap&format=table
>
>
> On Mon, 21 Nov 2016 at 20:28 Mark Tompsett <mtompset at hotmail.com> wrote:
>
> Greetings,
>
> The number of Failed QA?s has significantly grown in the last few months.
> And while this is a good problem (congrats QA Team), perhaps there are some
> that should be either closed or revisited. I just dealt with one of mine,
> after a long while, and I?m wondering if others have accidentally forgotten
> theirs as well.
>
> GPML,
> Mark Tompsett
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/52e1d2a4/attachment-0001.html>

From tomascohen at gmail.com  Wed Nov 23 21:21:19 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Wed, 23 Nov 2016 20:21:19 +0000
Subject: [Koha-devel] [Koha] Koha 16.11.00 released!
In-Reply-To: <CADT_QRQ+EcLfmBf=_ZAnhtAk+MwuhZG=MkR_MFww9vvcP4TMGA@mail.gmail.com>
References: <CACpVHfwo32Y5UKng51Zd880PM-n=3_-aj95cHiU=j0RhkBW7rQ@mail.gmail.com>
	<CACpVHfy6CTXpo4CdcR5nzSS4vXgddquYKpq2hbR9jzvVGGqAKw@mail.gmail.com>
	<CACpVHfztPj=TEsY7pQaUTyEvrB6GsseF+9bE9wfevCn0+pd6oQ@mail.gmail.com>
	<CADT_QRQ+EcLfmBf=_ZAnhtAk+MwuhZG=MkR_MFww9vvcP4TMGA@mail.gmail.com>
Message-ID: <CABZfb=V-0S5XbtgZ8kzy8QC0Hr=o=YV1Jg7KqtgiU4K+3hqd-g@mail.gmail.com>

Congratulations Kyle, Brendan and the whole team!

El mi?., 23 de nov. de 2016 7:59 AM, Hugo Agud <hagud at orex.es> escribi?:

> Great work! thanks a lot to all
>
> 2016-11-23 11:54 GMT+01:00 Kyle Hall <kyle.m.hall at gmail.com>:
>
> > Here is a link to the original text version, as I've been told that my
> > attachment has been stripped out!
> >
> > http://git.koha-community.org/gitweb/?p=koha.git;a=blob_
> > plain;f=misc/release_notes/release_notes_16_11_00.md;hb=HEAD
> >
> > Kyle
> >
> > <https://secure2.convio.net/cffh/site/Donation2?df_id=
> > 1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.
> > donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
> >
> > http://www.kylehall.info
> > ByWater Solutions ( http://bywatersolutions.com )
> > Meadville Public Library ( http://www.meadvillelibrary.org )
> > Crawford County Federated Library System ( http://www.ccfls.org )
> >
> > On Wed, Nov 23, 2016 at 5:54 AM, Kyle Hall <kyle.m.hall at gmail.com>
> wrote:
> >
> > > Here is a link to the original text version, as I've been told that my
> > > attachment has been stripped out!
> > >
> > > Kyle
> > >
> > >
> > > <https://secure2.convio.net/cffh/site/Donation2?df_id=
> > 1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.
> > donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>
> > >
> > > http://www.kylehall.info
> > > ByWater Solutions ( http://bywatersolutions.com )
> > > Meadville Public Library ( http://www.meadvillelibrary.org )
> > > Crawford County Federated Library System ( http://www.ccfls.org )
> > >
> > > On Tue, Nov 22, 2016 at 2:05 PM, Kyle Hall <kyle.m.hall at gmail.com>
> > wrote:
> > >
> > >> It is my great pleasure to announce the release of Koha 16.11.00!
> > >>
> > >> Thanks be to everyone involved in getting 16.11 out the door!
> > >>
> > >> Attached are the release notes.
> > >>
> > >> Kyle
> > >>
> > >> http://www.kylehall.info
> > >> ByWater Solutions ( http://bywatersolutions.com )
> > >> Meadville Public Library ( http://www.meadvillelibrary.org )
> > >> Crawford County Federated Library System ( http://www.ccfls.org )
> > >>
> > >
> > >
> > _______________________________________________
> > Koha mailing list  http://koha-community.org
> > Koha at lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
>
>
>
> --
>
> *Hugo Agud - Orex Digital *
>
> *www.orex.es <http://www.orex.es>*
>
>
> <http://www.orex.es/>    [image: www.orex.es/koha] <
> http://www.orex.es/koha>
>    [image: www.orex.es/vufind] <http://www.orex.es/vufind>
> <http://www.orex.es/omeka>
>
>
> Director
>
> Calle Sant Joaquin,117, 2?-3? ? 08922 Santa Coloma de Gramanet - Tel: 933
> 856 138   hagud at orex.es ? http://www.orex.es/
>
>
>
> No imprima este mensaje a no ser que sea necesario. Una tonelada de papel
> implica la tala de 15 ?rboles y el consumo de 250.000 litros de agua.
>
>
>
> Aviso de confidencialidad
> Este mensaje contiene informaci?n que puede ser CONFIDENCIAL y/o de USO
> RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni
> est? autorizado a recibirlo por el remitente), no est? autorizado a copiar,
> reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje
> por error, por favor, notif?quenoslo inmediatamente y b?rrelo de su
> sistema.
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tom?s Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161123/1f92915c/attachment.html>

From colin.campbell at ptfs-europe.com  Thu Nov 24 17:32:03 2016
From: colin.campbell at ptfs-europe.com (Colin Campbell)
Date: Thu, 24 Nov 2016 16:32:03 +0000
Subject: [Koha-devel] proper sorting order and search for Swedish
 characters and ISBN search
In-Reply-To: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com>
References: <2c48ae9f-437b-328e-f86d-ef81e589456e@biblibre.com>
Message-ID: <20161124163203.GA26313@zazou.cscnet.co.uk>

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

From roger.grossmann at lmscloud.de  Fri Nov 25 10:38:29 2016
From: roger.grossmann at lmscloud.de (Roger Grossmann)
Date: Fri, 25 Nov 2016 10:38:29 +0100
Subject: [Koha-devel] Questions regarding localization
In-Reply-To: <995a239d-dca5-bc62-a819-a8d6e0fd2215@web.de>
References: <16CC5887-3414-4B4C-96FD-B408FDE39655@lmscloud.de>
	<995a239d-dca5-bc62-a819-a8d6e0fd2215@web.de>
Message-ID: <912757DE-8292-4C2C-B040-EA4FBE587C56@lmscloud.de>

Hi Kathrin,

thank's a lot for the information regarding localization.

> They are updated pre-release using the translation scripts - no manual editing is required.
Is there a documentation for the use of the translation scripts?

Best regards,
Roger

> Am 21.11.2016 um 22:40 schrieb Katrin <katrin.fischer.83 at web.de>:
> 
> Hi Roger,
> 
> strings in Koha are either stored in the database (authorised values, item type descriptions, MARC field and subfield descriptions, etc.) or are part of the templates.
> 
> Strings in the templates are translated via the po files you have already seen. They are updated pre-release using the translation scripts - no manual editing is required. I think on the packages it works with: sudo koha-translate -u <langcode>. Or in koha-shell: cd misc translator, perl translate update <langcode>. TT variables will be automatically replaced by %s. For JavaScript there is a special syntax you can use that has the same effect.
> 
> You can find additional information about the translation process on the wiki: 
> 
> https://wiki.koha-community.org/wiki/Translating_Koha <https://wiki.koha-community.org/wiki/Translating_Koha>
> https://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client <https://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client>
> There are also some coding guidelines concerning translation:
> 
> https://wiki.koha-community.org/wiki/Coding_Guidelines <https://wiki.koha-community.org/wiki/Coding_Guidelines>
> As you have written the $type parameter is currently not used. The different fines and fees are differentiated in the database by their accounttype in accountlines. The code is translated into a description in the templates, which means there can be a translation for every installed language.
> 
> Hope this helps,
> 
> Katrin
> 
> On 18.11.2016 16:12, Roger Grossmann wrote:
>> Hi all,
>> 
>> as a Koha development newbie I am having a few questions especially with localization. 
>> I am developing enhancements which I plan to bring in to the community hopefully soon. Your answers will help to make progress with it.
>> 
>> 1st question
>> ----------------
>> After looking at much Koha code I did not find a solution to build server side localized strings to persist localized text in the database. 
>> What do you recommend to use here?
>> 
>> Background: 
>> As you know, fines and fees are a sensitive area. Borrowers like to know exactly why they are charged and for what exactly. 
>> Lets assume, you want to store good localized name for the type of an overdue fine. 
>> It was for instance planned for function "UpdateFine" in C4::Overdues but the parameter $type is never filled as originally planned.
>> If an additional type name would be passed here, it needed to be a localized string since borrowers want to read the charge reason in their language.
>> As this is just an example for the use of a localized server text, the question is, whether there is already an approach to manage localised server side texts.
>> Ideally, server side texts would support parameter replacement that is not dependent of the position in the text as for instance with %s using sprintf.
>> 
>> 2nd question
>> -----------------
>> I want to build some new UI functionality. The procedure how to do that with templates in english first is clear to me.
>> As I am German, I would like to build during development a first German version of the template as well and would like to extend the related German .po file.
>> How can I add the texts for a specific language in my development environment? 
>> Is there a way to extract the new texts of templates and add them to an existing .po file with a script and use poedit to translate them?
>> How do you do that?
>> 
>> Thanks in advance for your help.
>> 
>> Best regards,
>> Roger
>> 
>> 
>> --
>> Roger Gro?mann
>> LMSCloud GmbH
>> Konrad-Zuse-Platz 8 - D-81829 M?nchen
>> t +49 (0)89 207042-620  m +49 (0)171-2194775 f +49 (0)89 207042-623
>> e roger.grossmann at lmscloud.de <mailto:roger.grossmann at lmscloud.de>
>> w www.lmscloud.de <http://www.lmscloud.de/>
>> 
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org <mailto:Koha-devel at lists.koha-community.org>
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
>> website : http://www.koha-community.org/ <http://www.koha-community.org/>
>> git : http://git.koha-community.org/ <http://git.koha-community.org/>
>> bugs : http://bugs.koha-community.org/ <http://bugs.koha-community.org/>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161125/385583ec/attachment.html>

From M.de.Rooy at rijksmuseum.nl  Fri Nov 25 13:49:39 2016
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Fri, 25 Nov 2016 12:49:39 +0000
Subject: [Koha-devel] Bug 17624: Hide (some) not-for-loan items on search
 results' availability
Message-ID: <VI1PR0501MB2591EC07572E901109DB9ADDCE890@VI1PR0501MB2591.eurprd05.prod.outlook.com>

Hi all,

What about the question on this report:

Hide Staff Collection only?


Note: See item field notforloan, value 2 == Staff Collection.

Authorised value category NOT_LOAN.


Any feedback appreciated. Here or on the report.


Thx

Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161125/697ad4cf/attachment.html>

From liw at qvarnlabs.com  Fri Nov 25 15:56:01 2016
From: liw at qvarnlabs.com (Lars Wirzenius)
Date: Fri, 25 Nov 2016 16:56:01 +0200
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
Message-ID: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>

Hi, Koha developers,

some of you may remember me from the Debian packaging of Koha I made
in 2010 for Catalyst IT. I've never looked much at the actual code
base of Koha, but one thing that even a quick grep reveals is that SQL
code is sprinkled all over the code base. To me, this indicates that
the application code ("business logic") and the way data is stored are
closely coupled, and that's generally not a good thing. Among other
things, if there's a need so change the database schema, or database
engine, the whole code base might be affected.

In my current job we develop a storage system (roughly, "database, but
with better access control") with an emphasis on privacy. Our software
is free software released under the Affero GPL, version 3 or later. I
suggest that our software (called Qvarn) would be worth considering
for Koha.

A summary of my impression of the situation:

* Koha stores very sensitive information about people's reading
  habits.

* In the EU the new General Data Protection Regulation (GDPR) is in
  effect (with a transition period until some time in 2014), which
  requires everyone who collects or stores personal information to
  take good care so the data doesn't leak and violate people's
  privacy. Koha, or at least libraries using Koha, would seem to fall
  under this (IANAL, TINLA, AYOL).

* At minimum, a "privacy impact assessment" needs to be made.
  Basically, think about what the happens to the people whose data it
  is that gets leaked. (Best to assume it will be.)

* Koha stores all its data (including the personal stuff) in
  MySQL/MariaDB. There is no clean abstraction layer, which means SQL
  is all over the code base, making things harder to change. I think
  it would be good for Koha to add an abstraction layer even if Koha
  stays with MySQL.

* Qvarn was designed from the ground up with privacy and security in
  mind. It is meant to be the least weak link in the chain to protect
  privacy of the data it stores. It's still under active development,
  and doesn't have all the planned features yet. It's backed by my new
  company, QvarnLabs, and is in production use already, storing around
  a million personal identities.

* Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
  per-client/per-user session state on the Qvarn side. Makes it really
  easy to use, from the client, in my opinion. All data is in JSON
  form, which also makes things easier to use, in my opinion. It's
  conceptually JSON objects, not tables/columns. Qvarn uses Postgres
  behind the scenes, at least for now, but that's not visible to API
  clients (read: we could replace it with individual files on disk and
  you'd not notice).

* Qvarn requires the use of Gluu (see gluu.org) for authentication and
  authorization. Gluu is an identity management server, which is also
  free software. We aim to hide Gluu entirely behind the Qvarn API,
  and already mostly do that, so it's not something you need to know
  much about, except that operationally it's a bit tricky, since it's
  harder to deploy than Qvarn itself it (Qvarn comes as a .deb).

Here's my thoughts about Koha using Qvarn:

* First step would be to change Koha to have a suitable abstraction
  layer for storing data. I imagine this will be a big job.

* Second step would be to model the data Koha stores in Qvarn resource
  types, i.e., decide which types of records should be and what they
  should contain.

* Third step is ...

* Fourth step is profit.

Benefits to Koha as far as I can see:

* Abstraction layer: cleaner code, easier database related changes in
  the future, possibly a better test suite as a side effect.

* Qvarn: more privacy protection for user data, maybe (this is my
  highly personal and biased opinion) a nicer way to store/access the
  data.

What do you think? Is this something that the Koha community might
want? I don't want to waste your time or anyone else's time if it's
not interesting. However, if it is interesting, QvarnLabs is willing
to work on making sure Qvarn is good for Koha.

Note: though both Qvarn and Koha are developed/supported by companies,
they're free software and also free to use. This is not unlike Koha
itself.

I'm happy to answer any questions you may have, preferably on the
koha-devel list.

From katrin.fischer.83 at web.de  Sat Nov 26 15:33:51 2016
From: katrin.fischer.83 at web.de (Katrin)
Date: Sat, 26 Nov 2016 15:33:51 +0100
Subject: [Koha-devel] Bug 17624: Hide (some) not-for-loan items on
 search results' availability
In-Reply-To: <VI1PR0501MB2591EC07572E901109DB9ADDCE890@VI1PR0501MB2591.eurprd05.prod.outlook.com>
References: <VI1PR0501MB2591EC07572E901109DB9ADDCE890@VI1PR0501MB2591.eurprd05.prod.outlook.com>
Message-ID: <1e82d4d3-f318-b3b8-3d1c-fc3b1e5f5f99@web.de>

Hi Marcel,


I left a note on the report:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17624#c6


Katrin



On 25.11.2016 13:49, Marcel de Rooy wrote:
>
> Hi all,
>
> What about the question on this report:
>
> Hide Staff Collection only?
>
>
> Note: See item field notforloan, value 2 == Staff Collection.
>
> Authorised value category NOT_LOAN.
>
>
> Any feedback appreciated. Here or on the report.
>
>
> Thx
>
> Marcel
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161126/f81cd6bd/attachment.html>

From reed at typist.geek.nz  Sat Nov 26 23:41:22 2016
From: reed at typist.geek.nz (Reed Wade)
Date: Sun, 27 Nov 2016 11:41:22 +1300
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
In-Reply-To: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
Message-ID: <CAMjHDpQHTEtSLOKwv4Mv=iTsELQJqtzVTy5txB7cdD9OW=scvw@mail.gmail.com>

LARS!

I have not been very involved in Koha work lately but remain a faithful
lurker.

The first thing that comes to mind which might be an obstacle to adopting
something like this is the library of SQL reports. I think this is a
collection of value that the community has created and maintains and gets a
lot out of.

I'm wondering if stepping away from that would be too great a loss / too
disruptive.

I'm totally out of date on this topic but that's just what comes to mind
first.

-reed


On 26 November 2016 at 03:56, Lars Wirzenius <liw at qvarnlabs.com> wrote:

> Hi, Koha developers,
>
> some of you may remember me from the Debian packaging of Koha I made
> in 2010 for Catalyst IT. I've never looked much at the actual code
> base of Koha, but one thing that even a quick grep reveals is that SQL
> code is sprinkled all over the code base. To me, this indicates that
> the application code ("business logic") and the way data is stored are
> closely coupled, and that's generally not a good thing. Among other
> things, if there's a need so change the database schema, or database
> engine, the whole code base might be affected.
>
> In my current job we develop a storage system (roughly, "database, but
> with better access control") with an emphasis on privacy. Our software
> is free software released under the Affero GPL, version 3 or later. I
> suggest that our software (called Qvarn) would be worth considering
> for Koha.
>
> A summary of my impression of the situation:
>
> * Koha stores very sensitive information about people's reading
>   habits.
>
> * In the EU the new General Data Protection Regulation (GDPR) is in
>   effect (with a transition period until some time in 2014), which
>   requires everyone who collects or stores personal information to
>   take good care so the data doesn't leak and violate people's
>   privacy. Koha, or at least libraries using Koha, would seem to fall
>   under this (IANAL, TINLA, AYOL).
>
> * At minimum, a "privacy impact assessment" needs to be made.
>   Basically, think about what the happens to the people whose data it
>   is that gets leaked. (Best to assume it will be.)
>
> * Koha stores all its data (including the personal stuff) in
>   MySQL/MariaDB. There is no clean abstraction layer, which means SQL
>   is all over the code base, making things harder to change. I think
>   it would be good for Koha to add an abstraction layer even if Koha
>   stays with MySQL.
>
> * Qvarn was designed from the ground up with privacy and security in
>   mind. It is meant to be the least weak link in the chain to protect
>   privacy of the data it stores. It's still under active development,
>   and doesn't have all the planned features yet. It's backed by my new
>   company, QvarnLabs, and is in production use already, storing around
>   a million personal identities.
>
> * Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
>   per-client/per-user session state on the Qvarn side. Makes it really
>   easy to use, from the client, in my opinion. All data is in JSON
>   form, which also makes things easier to use, in my opinion. It's
>   conceptually JSON objects, not tables/columns. Qvarn uses Postgres
>   behind the scenes, at least for now, but that's not visible to API
>   clients (read: we could replace it with individual files on disk and
>   you'd not notice).
>
> * Qvarn requires the use of Gluu (see gluu.org) for authentication and
>   authorization. Gluu is an identity management server, which is also
>   free software. We aim to hide Gluu entirely behind the Qvarn API,
>   and already mostly do that, so it's not something you need to know
>   much about, except that operationally it's a bit tricky, since it's
>   harder to deploy than Qvarn itself it (Qvarn comes as a .deb).
>
> Here's my thoughts about Koha using Qvarn:
>
> * First step would be to change Koha to have a suitable abstraction
>   layer for storing data. I imagine this will be a big job.
>
> * Second step would be to model the data Koha stores in Qvarn resource
>   types, i.e., decide which types of records should be and what they
>   should contain.
>
> * Third step is ...
>
> * Fourth step is profit.
>
> Benefits to Koha as far as I can see:
>
> * Abstraction layer: cleaner code, easier database related changes in
>   the future, possibly a better test suite as a side effect.
>
> * Qvarn: more privacy protection for user data, maybe (this is my
>   highly personal and biased opinion) a nicer way to store/access the
>   data.
>
> What do you think? Is this something that the Koha community might
> want? I don't want to waste your time or anyone else's time if it's
> not interesting. However, if it is interesting, QvarnLabs is willing
> to work on making sure Qvarn is good for Koha.
>
> Note: though both Qvarn and Koha are developed/supported by companies,
> they're free software and also free to use. This is not unlike Koha
> itself.
>
> I'm happy to answer any questions you may have, preferably on the
> koha-devel list.
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161127/fc45db71/attachment.html>

From reed at typist.geek.nz  Sun Nov 27 08:30:26 2016
From: reed at typist.geek.nz (Reed Wade)
Date: Sun, 27 Nov 2016 20:30:26 +1300
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>
	<BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com>

I've been dealing with centos a lot at my current job and learning how to
make rpms for all our bits.

If I had some spare time, what would a minimally useful koha related redhat
style something look like? Is it the packaging or the build recipe or both?

-reed



On 16 November 2016 at 06:51, Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> Renvoize, Martin <martin.renvoize at ptfs-europe.com> wrote:
> *> *
> +1 to this cleanup, and also to a link to 'installing from source'.
> > [T]hough which version of that is most up to date is a mystery to me.
>
> And that is why Jonathan jokingly suggested that if the issue is near and
> dear to my heart he was glad I volunteered to clean up a single source
> install related page. Sadly, I would rather refactor Koha such that default
> CentOS, Fedora, and/or Red Hat installs would work. The PDF libraries are a
> mess, and a part of this problem. And it should be noted, still not
> volunteering now, but may in the future ? no promises (insert Candi?s Love
> Makes No Promises musical flashback).
>
> GPML,
> Mark Tompsett
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161127/928fab48/attachment-0001.html>

From mtompset at hotmail.com  Sun Nov 27 10:34:42 2016
From: mtompset at hotmail.com (Mark Tompsett)
Date: Sun, 27 Nov 2016 09:34:42 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com><CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com><BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com><CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com><BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com>
Message-ID: <BY2PR0401MB1752A757E35C04B3EA4EEECDC68B0@BY2PR0401MB1752.namprd04.prod.outlook.com>

Greetings,

Reed Wade asked:
> If I had some spare time, what would a minimally useful koha
> related redhat style something look like?
> Is it the packaging or the build recipe or both?

Given that koha is generally installed for production with: sudo apt-get install koha-common
(plus the other steps)
The ability to: yum install koha-common
Because an RPM existed would be nice, plus RPMs for the 18ish
(it was around that number last I checked) libraries that are not
available in the default CentOS repos.

Granted, I do not use CentOS regularly, but I was crazy enough to try non-Debian installs with it and even attempted a native Windows install a while back. Sadly, Windows natively is just too painful to succeed.

GPML,
Mark Tompsett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161127/6a4ec6da/attachment.html>

From reed at typist.geek.nz  Sun Nov 27 11:24:46 2016
From: reed at typist.geek.nz (Reed Wade)
Date: Sun, 27 Nov 2016 23:24:46 +1300
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <BY2PR0401MB1752A757E35C04B3EA4EEECDC68B0@BY2PR0401MB1752.namprd04.prod.outlook.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>
	<BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com>
	<BY2PR0401MB1752A757E35C04B3EA4EEECDC68B0@BY2PR0401MB1752.namprd04.prod.outlook.com>
Message-ID: <CAMjHDpToRX+4aGxAg8a252ghydapUtwr+yTjvHxwdPTM1PtuwQ@mail.gmail.com>

Yes... I have some memory now of Lars getting some large set of non-debian
packaged dependent products debian packaged before he was able to package
up Koha.

I'll make some experiments..

-reed


On 27 November 2016 at 22:34, Mark Tompsett <mtompset at hotmail.com> wrote:

> Greetings,
>
> Reed Wade asked:
> > If I had some spare time, what would a minimally useful koha
> > related redhat style something look like?
> > Is it the packaging or the build recipe or both?
>
> Given that koha is generally installed for production with: sudo apt-get
> install koha-common
> (plus the other steps)
> The ability to: yum install koha-common
> Because an RPM existed would be nice, plus RPMs for the 18ish
> (it was around that number last I checked) libraries that are not
> available in the default CentOS repos.
>
> Granted, I do not use CentOS regularly, but I was crazy enough to try
> non-Debian installs with it and even attempted a native Windows install a
> while back. Sadly, Windows natively is just too painful to succeed.
>
> GPML,
> Mark Tompsett
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161127/a24b9287/attachment.html>

From reed at typist.geek.nz  Sun Nov 27 12:07:24 2016
From: reed at typist.geek.nz (Reed Wade)
Date: Mon, 28 Nov 2016 00:07:24 +1300
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAMjHDpToRX+4aGxAg8a252ghydapUtwr+yTjvHxwdPTM1PtuwQ@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com>
	<CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com>
	<BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com>
	<BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com>
	<BY2PR0401MB1752A757E35C04B3EA4EEECDC68B0@BY2PR0401MB1752.namprd04.prod.outlook.com>
	<CAMjHDpToRX+4aGxAg8a252ghydapUtwr+yTjvHxwdPTM1PtuwQ@mail.gmail.com>
Message-ID: <CAMjHDpRraADZ91k69bsDMdoyoRmu6HCUOqG1Kjm+j=nxCiVSEQ@mail.gmail.com>

And, so, actually, I have to wonder if putting together a redhat style
installation is a long term good or not.

I recall that someone a million years ago made a windows installer for Koha
and released it into the wild and so now every few months someone finds it
and tries to use it and gets confused.

I don't predict being able to support a full on always current redhat
collection of packages -- so maybe the world is safer as things stand now?

-reed



On 27 November 2016 at 23:24, Reed Wade <reed at typist.geek.nz> wrote:

>
> Yes... I have some memory now of Lars getting some large set of non-debian
> packaged dependent products debian packaged before he was able to package
> up Koha.
>
> I'll make some experiments..
>
> -reed
>
>
> On 27 November 2016 at 22:34, Mark Tompsett <mtompset at hotmail.com> wrote:
>
>> Greetings,
>>
>> Reed Wade asked:
>> > If I had some spare time, what would a minimally useful koha
>> > related redhat style something look like?
>> > Is it the packaging or the build recipe or both?
>>
>> Given that koha is generally installed for production with: sudo apt-get
>> install koha-common
>> (plus the other steps)
>> The ability to: yum install koha-common
>> Because an RPM existed would be nice, plus RPMs for the 18ish
>> (it was around that number last I checked) libraries that are not
>> available in the default CentOS repos.
>>
>> Granted, I do not use CentOS regularly, but I was crazy enough to try
>> non-Debian installs with it and even attempted a native Windows install a
>> while back. Sadly, Windows natively is just too painful to succeed.
>>
>> GPML,
>> Mark Tompsett
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/29fa6231/attachment.html>

From z.tajoli at cineca.it  Sun Nov 27 12:58:27 2016
From: z.tajoli at cineca.it (Zeno Tajoli)
Date: Sun, 27 Nov 2016 12:58:27 +0100 (CET)
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAMjHDpRraADZ91k69bsDMdoyoRmu6HCUOqG1Kjm+j=nxCiVSEQ@mail.gmail.com>
Message-ID: <1229231314.119704969.1480247907799.JavaMail.root@cineca.it>

Hi Reed,

>And, so, actually, I have to wonder if putting together a redhat style installation is a long term good or not. 

I think that the best option to start is to see those two documents:
https://wiki.koha-community.org/wiki/Koha_3.10_on_Centos_6.3_x86_64_en
https://wiki.koha-community.org/wiki/Koha_3.22_on_Fedora_23

and after to write an Koha_on_Centos_HowTo in which do you explain how to
 find the missing perl modules and system utilities .
A good plus is to write an  Ansible task  for all the requirements in Centos 7.x for Koha 16.05 and 16.11

Bye
Zeno Tajoli

From reed at typist.geek.nz  Sun Nov 27 13:12:22 2016
From: reed at typist.geek.nz (Reed Wade)
Date: Mon, 28 Nov 2016 01:12:22 +1300
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <1229231314.119704969.1480247907799.JavaMail.root@cineca.it>
References: <CAMjHDpRraADZ91k69bsDMdoyoRmu6HCUOqG1Kjm+j=nxCiVSEQ@mail.gmail.com>
	<1229231314.119704969.1480247907799.JavaMail.root@cineca.it>
Message-ID: <CAMjHDpS-E8ZeFgUusz8DWjWf4p3uwtXtHWO-0_zEJLJAKipfcw@mail.gmail.com>

makes sense, yes

-reed

On 28 November 2016 at 00:58, Zeno Tajoli <z.tajoli at cineca.it> wrote:

> Hi Reed,
>
> >And, so, actually, I have to wonder if putting together a redhat style
> installation is a long term good or not.
>
> I think that the best option to start is to see those two documents:
> https://wiki.koha-community.org/wiki/Koha_3.10_on_Centos_6.3_x86_64_en
> https://wiki.koha-community.org/wiki/Koha_3.22_on_Fedora_23
>
> and after to write an Koha_on_Centos_HowTo in which do you explain how to
>  find the missing perl modules and system utilities .
> A good plus is to write an  Ansible task  for all the requirements in
> Centos 7.x for Koha 16.05 and 16.11
>
> Bye
> Zeno Tajoli
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/cd713be0/attachment.html>

From mtompset at hotmail.com  Sun Nov 27 17:00:08 2016
From: mtompset at hotmail.com (Mark Tompsett)
Date: Sun, 27 Nov 2016 16:00:08 +0000
Subject: [Koha-devel] INSTALL.debian is outdated
In-Reply-To: <CAMjHDpRraADZ91k69bsDMdoyoRmu6HCUOqG1Kjm+j=nxCiVSEQ@mail.gmail.com>
References: <CAJzKNY6aRmHmQ4tPZbu3CxhAC+Y+JGca3Pkk_=c5W+XjEqkdTA@mail.gmail.com><CAJzKNY6mZ+0kKENygqRApOSEe8NCM+UbyBkD+qg4xM0ZHpuCtg@mail.gmail.com><BY2PR0401MB1752E6F9E1F976DE803DAF73C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com><CAB7SL8CZi2X-E-DRg1reNQgu+zN_=2UfpeNa9qWkvxD6UTcHWg@mail.gmail.com><BY2PR0401MB17520DF74D1F1CDCC01B6DD9C6BF0@BY2PR0401MB1752.namprd04.prod.outlook.com><CAMjHDpQso7xzF5XUnE4y7zV4pyUk7qeF4bc8xNXQ_Vh98xac8g@mail.gmail.com><BY2PR0401MB1752A757E35C04B3EA4EEECDC68B0@BY2PR0401MB1752.namprd04.prod.outlook.com><CAMjHDpToRX+4aGxAg8a252ghydapUtwr+yTjvHxwdPTM1PtuwQ@mail.gmail.com>
	<CAMjHDpRraADZ91k69bsDMdoyoRmu6HCUOqG1Kjm+j=nxCiVSEQ@mail.gmail.com>
Message-ID: <BY2PR0401MB1752A93AAACA659B138667B3C68B0@BY2PR0401MB1752.namprd04.prod.outlook.com>

Greetings,

Reed Wade pondered:
> And, so, actually, I have to wonder if putting together a redhat style 
> installation
> is a long term good or not.

A full koha-common RPM, perhaps not. That would need updating each release.
But all the parts (libXXX-perl) that are missing would be good if hosted by 
the community.
Generally the minimum required for a library doesn?t change long term.


Reed Wade inquired:
> I don't predict being able to support a full on always current redhat
> collection of packages -- so maybe the world is safer as things stand now?

Providing just the missing pieces to be hosted by the community would never 
go out of
worth, because if the default repos caught up and/or surpassed, they would 
get used.


Zeno Tajoli suggested:
> A good plus is to write an  Ansible task  for all the requirements
> in Centos 7.x for Koha 16.05 and 16.11

I would think that such a task would also have merit.
I suspect that something might be adaptable from ansible script on 
kohadevbox.

GPML,
Mark Tompsett


From M.de.Rooy at rijksmuseum.nl  Mon Nov 28 09:06:45 2016
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Mon, 28 Nov 2016 08:06:45 +0000
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
In-Reply-To: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
Message-ID: <VI1PR0501MB25914FAF26356EF0A5D94888CE8A0@VI1PR0501MB2591.eurprd05.prod.outlook.com>

Hi Lars,
We are moving - slowly - away from SQL all over the place with DBIx and Koha::Object[s].
At the same time moving code from C4 to these Koha objects.
This is a huge operation.
Another ongoing project is the extension of the RESTful API (using Mojolicious and Swagger).

So, things are already moving..

Marcel

-----Oorspronkelijk bericht-----
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Lars Wirzenius
Verzonden: vrijdag 25 november 2016 15:56
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] Koha and Qvarn, a suggestion (also too long for anyone to finish reading)

Hi, Koha developers,

some of you may remember me from the Debian packaging of Koha I made in 2010 for Catalyst IT. I've never looked much at the actual code base of Koha, but one thing that even a quick grep reveals is that SQL code is sprinkled all over the code base. To me, this indicates that the application code ("business logic") and the way data is stored are closely coupled, and that's generally not a good thing. Among other things, if there's a need so change the database schema, or database engine, the whole code base might be affected.

In my current job we develop a storage system (roughly, "database, but with better access control") with an emphasis on privacy. Our software is free software released under the Affero GPL, version 3 or later. I suggest that our software (called Qvarn) would be worth considering for Koha.

A summary of my impression of the situation:

* Koha stores very sensitive information about people's reading
  habits.

* In the EU the new General Data Protection Regulation (GDPR) is in
  effect (with a transition period until some time in 2014), which
  requires everyone who collects or stores personal information to
  take good care so the data doesn't leak and violate people's
  privacy. Koha, or at least libraries using Koha, would seem to fall
  under this (IANAL, TINLA, AYOL).

* At minimum, a "privacy impact assessment" needs to be made.
  Basically, think about what the happens to the people whose data it
  is that gets leaked. (Best to assume it will be.)

* Koha stores all its data (including the personal stuff) in
  MySQL/MariaDB. There is no clean abstraction layer, which means SQL
  is all over the code base, making things harder to change. I think
  it would be good for Koha to add an abstraction layer even if Koha
  stays with MySQL.

* Qvarn was designed from the ground up with privacy and security in
  mind. It is meant to be the least weak link in the chain to protect
  privacy of the data it stores. It's still under active development,
  and doesn't have all the planned features yet. It's backed by my new
  company, QvarnLabs, and is in production use already, storing around
  a million personal identities.

* Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
  per-client/per-user session state on the Qvarn side. Makes it really
  easy to use, from the client, in my opinion. All data is in JSON
  form, which also makes things easier to use, in my opinion. It's
  conceptually JSON objects, not tables/columns. Qvarn uses Postgres
  behind the scenes, at least for now, but that's not visible to API
  clients (read: we could replace it with individual files on disk and
  you'd not notice).

* Qvarn requires the use of Gluu (see gluu.org) for authentication and
  authorization. Gluu is an identity management server, which is also
  free software. We aim to hide Gluu entirely behind the Qvarn API,
  and already mostly do that, so it's not something you need to know
  much about, except that operationally it's a bit tricky, since it's
  harder to deploy than Qvarn itself it (Qvarn comes as a .deb).

Here's my thoughts about Koha using Qvarn:

* First step would be to change Koha to have a suitable abstraction
  layer for storing data. I imagine this will be a big job.

* Second step would be to model the data Koha stores in Qvarn resource
  types, i.e., decide which types of records should be and what they
  should contain.

* Third step is ...

* Fourth step is profit.

Benefits to Koha as far as I can see:

* Abstraction layer: cleaner code, easier database related changes in
  the future, possibly a better test suite as a side effect.

* Qvarn: more privacy protection for user data, maybe (this is my
  highly personal and biased opinion) a nicer way to store/access the
  data.

What do you think? Is this something that the Koha community might want? I don't want to waste your time or anyone else's time if it's not interesting. However, if it is interesting, QvarnLabs is willing to work on making sure Qvarn is good for Koha.

Note: though both Qvarn and Koha are developed/supported by companies, they're free software and also free to use. This is not unlike Koha itself.

I'm happy to answer any questions you may have, preferably on the koha-devel list.
_______________________________________________
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 chrisc at catalyst.net.nz  Mon Nov 28 09:14:42 2016
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Mon, 28 Nov 2016 21:14:42 +1300
Subject: [Koha-devel] Koha and Qvarn,
	a suggestion (also too long for anyone to finish reading)
In-Reply-To: <VI1PR0501MB25914FAF26356EF0A5D94888CE8A0@VI1PR0501MB2591.eurprd05.prod.outlook.com>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
	<VI1PR0501MB25914FAF26356EF0A5D94888CE8A0@VI1PR0501MB2591.eurprd05.prod.outlook.com>
Message-ID: <B1947EFD-2BF6-4F1D-B41C-6FB974800399@catalyst.net.nz>

Hi All

With the move to DBIx::Class we do gain some db independence. But we don't improve privacy much. This is where Qvarn would come in, if I am understanding correctly, the back end some of our stuff would become Qvarn, if we implement it correctly it would be handled by the Object level code and nothing higher up would need to know.

At least I think so anyway, hopefully Lars can put me right if I have misunderstood

Chris

On 28 November 2016 9:06:45 PM NZDT, Marcel de Rooy <M.de.Rooy at rijksmuseum.nl> wrote:
>Hi Lars,
>We are moving - slowly - away from SQL all over the place with DBIx and
>Koha::Object[s].
>At the same time moving code from C4 to these Koha objects.
>This is a huge operation.
>Another ongoing project is the extension of the RESTful API (using
>Mojolicious and Swagger).
>
>So, things are already moving..
>
>Marcel
>
>-----Oorspronkelijk bericht-----
>Van: koha-devel-bounces at lists.koha-community.org
>[mailto:koha-devel-bounces at lists.koha-community.org] Namens Lars
>Wirzenius
>Verzonden: vrijdag 25 november 2016 15:56
>Aan: koha-devel at lists.koha-community.org
>Onderwerp: [Koha-devel] Koha and Qvarn, a suggestion (also too long for
>anyone to finish reading)
>
>Hi, Koha developers,
>
>some of you may remember me from the Debian packaging of Koha I made in
>2010 for Catalyst IT. I've never looked much at the actual code base of
>Koha, but one thing that even a quick grep reveals is that SQL code is
>sprinkled all over the code base. To me, this indicates that the
>application code ("business logic") and the way data is stored are
>closely coupled, and that's generally not a good thing. Among other
>things, if there's a need so change the database schema, or database
>engine, the whole code base might be affected.
>
>In my current job we develop a storage system (roughly, "database, but
>with better access control") with an emphasis on privacy. Our software
>is free software released under the Affero GPL, version 3 or later. I
>suggest that our software (called Qvarn) would be worth considering for
>Koha.
>
>A summary of my impression of the situation:
>
>* Koha stores very sensitive information about people's reading
>  habits.
>
>* In the EU the new General Data Protection Regulation (GDPR) is in
>  effect (with a transition period until some time in 2014), which
>  requires everyone who collects or stores personal information to
>  take good care so the data doesn't leak and violate people's
>  privacy. Koha, or at least libraries using Koha, would seem to fall
>  under this (IANAL, TINLA, AYOL).
>
>* At minimum, a "privacy impact assessment" needs to be made.
>  Basically, think about what the happens to the people whose data it
>  is that gets leaked. (Best to assume it will be.)
>
>* Koha stores all its data (including the personal stuff) in
>  MySQL/MariaDB. There is no clean abstraction layer, which means SQL
>  is all over the code base, making things harder to change. I think
>  it would be good for Koha to add an abstraction layer even if Koha
>  stays with MySQL.
>
>* Qvarn was designed from the ground up with privacy and security in
>  mind. It is meant to be the least weak link in the chain to protect
>  privacy of the data it stores. It's still under active development,
>  and doesn't have all the planned features yet. It's backed by my new
>  company, QvarnLabs, and is in production use already, storing around
>  a million personal identities.
>
>* Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
>  per-client/per-user session state on the Qvarn side. Makes it really
>  easy to use, from the client, in my opinion. All data is in JSON
>  form, which also makes things easier to use, in my opinion. It's
>  conceptually JSON objects, not tables/columns. Qvarn uses Postgres
>  behind the scenes, at least for now, but that's not visible to API
>  clients (read: we could replace it with individual files on disk and
>  you'd not notice).
>
>* Qvarn requires the use of Gluu (see gluu.org) for authentication and
>  authorization. Gluu is an identity management server, which is also
>  free software. We aim to hide Gluu entirely behind the Qvarn API,
>  and already mostly do that, so it's not something you need to know
>  much about, except that operationally it's a bit tricky, since it's
>  harder to deploy than Qvarn itself it (Qvarn comes as a .deb).
>
>Here's my thoughts about Koha using Qvarn:
>
>* First step would be to change Koha to have a suitable abstraction
>  layer for storing data. I imagine this will be a big job.
>
>* Second step would be to model the data Koha stores in Qvarn resource
>  types, i.e., decide which types of records should be and what they
>  should contain.
>
>* Third step is ...
>
>* Fourth step is profit.
>
>Benefits to Koha as far as I can see:
>
>* Abstraction layer: cleaner code, easier database related changes in
>  the future, possibly a better test suite as a side effect.
>
>* Qvarn: more privacy protection for user data, maybe (this is my
>  highly personal and biased opinion) a nicer way to store/access the
>  data.
>
>What do you think? Is this something that the Koha community might
>want? I don't want to waste your time or anyone else's time if it's not
>interesting. However, if it is interesting, QvarnLabs is willing to
>work on making sure Qvarn is good for Koha.
>
>Note: though both Qvarn and Koha are developed/supported by companies,
>they're free software and also free to use. This is not unlike Koha
>itself.
>
>I'm happy to answer any questions you may have, preferably on the
>koha-devel list.
>_______________________________________________
>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/

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/717b7b57/attachment.html>

From petter.goksoyr.asen at kul.oslo.kommune.no  Mon Nov 28 09:17:28 2016
From: petter.goksoyr.asen at kul.oslo.kommune.no (=?iso-8859-1?Q?Petter_Goks=F8yr_=C5sen?=)
Date: Mon, 28 Nov 2016 08:17:28 +0000
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
In-Reply-To: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
Message-ID: <a150ffe257be4e2bb562a80b23fc8d6d@MAIL231608.oslofelles.oslo.kommune.no>

Hi,

>From my brief reading of the Qvarn documentation it seems like a solid piece of
well-thought out enginerring.

However, to replace Koha's database interaction with Qvarn would be an enourmus
task, as well as increasing the complexity of the deployment manyfold with additional
layers, servers and programming languages.

If I where to design a library system from scratch today, Qvarn is something to consider,
but to rewrite 60% (a wild guess) of Koha codebase now seems quite a challenge!

I am by no means negative, just trying to look realsitic at it - who is going to put
in all theese hours to do the work?

Petter Goks?yr ?sen
Deichmanske bibliotek / Oslo Public Library
________________________________________
Fra: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] p? vegne av Lars Wirzenius [liw at qvarnlabs.com]
Sendt: 25. november 2016 15:56
Til: koha-devel at lists.koha-community.org
Emne: [Koha-devel] Koha and Qvarn, a suggestion (also too long for anyone to finish reading)

Hi, Koha developers,

some of you may remember me from the Debian packaging of Koha I made
in 2010 for Catalyst IT. I've never looked much at the actual code
base of Koha, but one thing that even a quick grep reveals is that SQL
code is sprinkled all over the code base. To me, this indicates that
the application code ("business logic") and the way data is stored are
closely coupled, and that's generally not a good thing. Among other
things, if there's a need so change the database schema, or database
engine, the whole code base might be affected.

In my current job we develop a storage system (roughly, "database, but
with better access control") with an emphasis on privacy. Our software
is free software released under the Affero GPL, version 3 or later. I
suggest that our software (called Qvarn) would be worth considering
for Koha.

A summary of my impression of the situation:

* Koha stores very sensitive information about people's reading
  habits.

* In the EU the new General Data Protection Regulation (GDPR) is in
  effect (with a transition period until some time in 2014), which
  requires everyone who collects or stores personal information to
  take good care so the data doesn't leak and violate people's
  privacy. Koha, or at least libraries using Koha, would seem to fall
  under this (IANAL, TINLA, AYOL).

* At minimum, a "privacy impact assessment" needs to be made.
  Basically, think about what the happens to the people whose data it
  is that gets leaked. (Best to assume it will be.)

* Koha stores all its data (including the personal stuff) in
  MySQL/MariaDB. There is no clean abstraction layer, which means SQL
  is all over the code base, making things harder to change. I think
  it would be good for Koha to add an abstraction layer even if Koha
  stays with MySQL.

* Qvarn was designed from the ground up with privacy and security in
  mind. It is meant to be the least weak link in the chain to protect
  privacy of the data it stores. It's still under active development,
  and doesn't have all the planned features yet. It's backed by my new
  company, QvarnLabs, and is in production use already, storing around
  a million personal identities.

* Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
  per-client/per-user session state on the Qvarn side. Makes it really
  easy to use, from the client, in my opinion. All data is in JSON
  form, which also makes things easier to use, in my opinion. It's
  conceptually JSON objects, not tables/columns. Qvarn uses Postgres
  behind the scenes, at least for now, but that's not visible to API
  clients (read: we could replace it with individual files on disk and
  you'd not notice).

* Qvarn requires the use of Gluu (see gluu.org) for authentication and
  authorization. Gluu is an identity management server, which is also
  free software. We aim to hide Gluu entirely behind the Qvarn API,
  and already mostly do that, so it's not something you need to know
  much about, except that operationally it's a bit tricky, since it's
  harder to deploy than Qvarn itself it (Qvarn comes as a .deb).

Here's my thoughts about Koha using Qvarn:

* First step would be to change Koha to have a suitable abstraction
  layer for storing data. I imagine this will be a big job.

* Second step would be to model the data Koha stores in Qvarn resource
  types, i.e., decide which types of records should be and what they
  should contain.

* Third step is ...

* Fourth step is profit.

Benefits to Koha as far as I can see:

* Abstraction layer: cleaner code, easier database related changes in
  the future, possibly a better test suite as a side effect.

* Qvarn: more privacy protection for user data, maybe (this is my
  highly personal and biased opinion) a nicer way to store/access the
  data.

What do you think? Is this something that the Koha community might
want? I don't want to waste your time or anyone else's time if it's
not interesting. However, if it is interesting, QvarnLabs is willing
to work on making sure Qvarn is good for Koha.

Note: though both Qvarn and Koha are developed/supported by companies,
they're free software and also free to use. This is not unlike Koha
itself.

I'm happy to answer any questions you may have, preferably on the
koha-devel list.
_______________________________________________
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  Mon Nov 28 09:26:27 2016
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Mon, 28 Nov 2016 08:26:27 +0000
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
In-Reply-To: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
Message-ID: <CAJzKNY6t0erSuNis-ouTGy0gDfHRo5kb1JB3oOm4sCbHCYN4xQ@mail.gmail.com>

Hi Lars,

Since 2010, a lot of things have changed and are currently going on.
We are moving our code from the legacy C4 to the new Koha namespace.
It might interest you to know that as I am currently moving the patron code
(see bug 16846). I personally don't thing it's conceivable to implement
Qvarn before we finish such job. Indeed the patron's info are retrieved
from different places and that will complicate its integration. Moreover it
will be much easier to do it when this rewrite is finished (it will depend
on the time it takes to make it in, it's hard to find testers for the
refactoring patches).
I don't think I understand all what it means to plug Qvarn and Koha, my
first questions would be:
What kind of data are we suppose to store into Qvarn. All the patron's
data? only a few personal data?
As Reed said: will it mean the patron's info will no longer be retrieved
from SQL reports?
How many times would it take to implement such changes?

Cheers,
Jonathan

On Fri, 25 Nov 2016 at 15:56 Lars Wirzenius <liw at qvarnlabs.com> wrote:

> Hi, Koha developers,
>
> some of you may remember me from the Debian packaging of Koha I made
> in 2010 for Catalyst IT. I've never looked much at the actual code
> base of Koha, but one thing that even a quick grep reveals is that SQL
> code is sprinkled all over the code base. To me, this indicates that
> the application code ("business logic") and the way data is stored are
> closely coupled, and that's generally not a good thing. Among other
> things, if there's a need so change the database schema, or database
> engine, the whole code base might be affected.
>
> In my current job we develop a storage system (roughly, "database, but
> with better access control") with an emphasis on privacy. Our software
> is free software released under the Affero GPL, version 3 or later. I
> suggest that our software (called Qvarn) would be worth considering
> for Koha.
>
> A summary of my impression of the situation:
>
> * Koha stores very sensitive information about people's reading
>   habits.
>
> * In the EU the new General Data Protection Regulation (GDPR) is in
>   effect (with a transition period until some time in 2014), which
>   requires everyone who collects or stores personal information to
>   take good care so the data doesn't leak and violate people's
>   privacy. Koha, or at least libraries using Koha, would seem to fall
>   under this (IANAL, TINLA, AYOL).
>
> * At minimum, a "privacy impact assessment" needs to be made.
>   Basically, think about what the happens to the people whose data it
>   is that gets leaked. (Best to assume it will be.)
>
> * Koha stores all its data (including the personal stuff) in
>   MySQL/MariaDB. There is no clean abstraction layer, which means SQL
>   is all over the code base, making things harder to change. I think
>   it would be good for Koha to add an abstraction layer even if Koha
>   stays with MySQL.
>
> * Qvarn was designed from the ground up with privacy and security in
>   mind. It is meant to be the least weak link in the chain to protect
>   privacy of the data it stores. It's still under active development,
>   and doesn't have all the planned features yet. It's backed by my new
>   company, QvarnLabs, and is in production use already, storing around
>   a million personal identities.
>
> * Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
>   per-client/per-user session state on the Qvarn side. Makes it really
>   easy to use, from the client, in my opinion. All data is in JSON
>   form, which also makes things easier to use, in my opinion. It's
>   conceptually JSON objects, not tables/columns. Qvarn uses Postgres
>   behind the scenes, at least for now, but that's not visible to API
>   clients (read: we could replace it with individual files on disk and
>   you'd not notice).
>
> * Qvarn requires the use of Gluu (see gluu.org) for authentication and
>   authorization. Gluu is an identity management server, which is also
>   free software. We aim to hide Gluu entirely behind the Qvarn API,
>   and already mostly do that, so it's not something you need to know
>   much about, except that operationally it's a bit tricky, since it's
>   harder to deploy than Qvarn itself it (Qvarn comes as a .deb).
>
> Here's my thoughts about Koha using Qvarn:
>
> * First step would be to change Koha to have a suitable abstraction
>   layer for storing data. I imagine this will be a big job.
>
> * Second step would be to model the data Koha stores in Qvarn resource
>   types, i.e., decide which types of records should be and what they
>   should contain.
>
> * Third step is ...
>
> * Fourth step is profit.
>
> Benefits to Koha as far as I can see:
>
> * Abstraction layer: cleaner code, easier database related changes in
>   the future, possibly a better test suite as a side effect.
>
> * Qvarn: more privacy protection for user data, maybe (this is my
>   highly personal and biased opinion) a nicer way to store/access the
>   data.
>
> What do you think? Is this something that the Koha community might
> want? I don't want to waste your time or anyone else's time if it's
> not interesting. However, if it is interesting, QvarnLabs is willing
> to work on making sure Qvarn is good for Koha.
>
> Note: though both Qvarn and Koha are developed/supported by companies,
> they're free software and also free to use. This is not unlike Koha
> itself.
>
> I'm happy to answer any questions you may have, preferably on the
> koha-devel list.
> _______________________________________________
> 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: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/62a73467/attachment-0001.html>

From kyle.m.hall at gmail.com  Mon Nov 28 17:33:12 2016
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Mon, 28 Nov 2016 11:33:12 -0500
Subject: [Koha-devel] Koha Wiki Facebook
Message-ID: <CACpVHfzHrQS73G8h7iYCM3vOK6UZ_=wxiPVGsx35RpWeOuMVEw@mail.gmail.com>

Hello All!

You can think Nick for finally pushing me to put up all the photos from the
HackFest!

For the uninitiated, for a long time I've been wanting to have a Koha
community facebook, in the original sense of the word.

So here it is!

https://wiki.koha-community.org/wiki/Community_Facebook

*Please* feel free to add and update this page. If you see any misspellings
or misinformation, please correct it! In particular, I wasn't able to add
the diacritics to names.

If you are not listed, please add yourself! You can upload a file and edit
the wiki page. If you need help doing so, please let me know!

Kyle

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/ab3874a9/attachment.html>

From tomascohen at gmail.com  Mon Nov 28 18:16:48 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 28 Nov 2016 17:16:48 +0000
Subject: [Koha-devel] Koha Wiki Facebook
In-Reply-To: <CACpVHfzHrQS73G8h7iYCM3vOK6UZ_=wxiPVGsx35RpWeOuMVEw@mail.gmail.com>
References: <CACpVHfzHrQS73G8h7iYCM3vOK6UZ_=wxiPVGsx35RpWeOuMVEw@mail.gmail.com>
Message-ID: <CABZfb=WLYk2Ee7VPMOinGTNXKPqHr+dey3SSjK2yx1ZvTY68PQ@mail.gmail.com>

Clap clap! Faces to nicknames!

El lun., 28 de nov. de 2016 1:33 PM, Kyle Hall <kyle.m.hall at gmail.com>
escribi?:

> Hello All!
>
> You can think Nick for finally pushing me to put up all the photos from
> the HackFest!
>
> For the uninitiated, for a long time I've been wanting to have a Koha
> community facebook, in the original sense of the word.
>
> So here it is!
>
> https://wiki.koha-community.org/wiki/Community_Facebook
>
> *Please* feel free to add and update this page. If you see any
> misspellings or misinformation, please correct it! In particular, I wasn't
> able to add the diacritics to names.
>
> If you are not listed, please add yourself! You can upload a file and edit
> the wiki page. If you need help doing so, please let me know!
>
> Kyle
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.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 <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161128/02482cd4/attachment.html>

From mirko at abunchofthings.net  Mon Nov 28 19:10:21 2016
From: mirko at abunchofthings.net (Mirko Tietgen)
Date: Mon, 28 Nov 2016 19:10:21 +0100
Subject: [Koha-devel] Koha 16.11.00 Debian package released
Message-ID: <16874c82-5083-2706-ac2b-55d67015d8f8@abunchofthings.net>

Hello everyone,

the Debian package for Koha, koha-common 16.11.00, is now available
from the community repository.

Please note that with the new release, the codename/version
relationship shifts to

stable		16.11
oldstable	16.05

Koha 3.22 is still maintained, but there won't be new Debian
packages for this branch an longer.

Koha 16.11 requires Debian Jessie. Debian Wheezy is not supported
any longer. The same goes for future versions of Koha 16.05.

We still have problems with Koha and MySQL 5.7. If you want to run
Koha 16.11 on Ubuntu, you will probably have the best experience
with Ubuntu 16.04 LTS and MariaDB instead of MySQL 5.7.

If you are running Koha 16.05 now and want to stay on this branch,
please make sure to change your apt configuration to use the
oldstable branch.

To upgrade to Koha 16.11, use stable in your apt configuration and do

apt-get update
apt-get upgrade
apt-get dist-upgrade

Please report any bugs you may encounter to
http://bugs.koha-community.org/

Cheers,

Mirko


-- 

Mirko Tietgen
mirko at abunchofthings.net
http://koha.abunchofthings.net
http://meinkoha.de


From katrin.fischer.83 at web.de  Tue Nov 29 08:15:50 2016
From: katrin.fischer.83 at web.de (Katrin)
Date: Tue, 29 Nov 2016 08:15:50 +0100
Subject: [Koha-devel] Questions regarding localization
In-Reply-To: <912757DE-8292-4C2C-B040-EA4FBE587C56@lmscloud.de>
References: <16CC5887-3414-4B4C-96FD-B408FDE39655@lmscloud.de>
	<995a239d-dca5-bc62-a819-a8d6e0fd2215@web.de>
	<912757DE-8292-4C2C-B040-EA4FBE587C56@lmscloud.de>
Message-ID: <6d6e7cb1-f542-c54b-55fc-c7f26095d7a7@web.de>

Hi Roger,

I have included the information on updating the po files for new strings 
in the e-mail as I didn't find a documentation right away with that bit 
included. For everything else please refer to the links.

Katrin

On 25.11.2016 10:38, Roger Grossmann wrote:
> Hi Kathrin,
>
> thank's a lot for the information regarding localization.
>
> > They are updated pre-release using the translation scripts - no 
> manual editing is required.
> Is there a documentation for the use of the translation scripts?
>
> Best regards,
> Roger
>
>> Am 21.11.2016 um 22:40 schrieb Katrin <katrin.fischer.83 at web.de 
>> <mailto:katrin.fischer.83 at web.de>>:
>>
>> Hi Roger,
>>
>> strings in Koha are either stored in the database (authorised values, 
>> item type descriptions, MARC field and subfield descriptions, etc.) 
>> or are part of the templates.
>>
>> Strings in the templates are translated via the po files you have 
>> already seen. They are updated pre-release using the translation 
>> scripts - no manual editing is required. I think on the packages it 
>> works with: sudo koha-translate -u <langcode>. Or in koha-shell: cd 
>> misc translator, perl translate update <langcode>. TT variables will 
>> be automatically replaced by %s. For JavaScript there is a special 
>> syntax you can use that has the same effect.
>>
>> You can find additional information about the translation process on 
>> the wiki:
>>
>> https://wiki.koha-community.org/wiki/Translating_Koha
>> https://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client
>>
>> There are also some coding guidelines concerning translation:
>>
>> https://wiki.koha-community.org/wiki/Coding_Guidelines
>>
>> As you have written the $type parameter is currently not used. The 
>> different fines and fees are differentiated in the database by their 
>> accounttype in accountlines. The code is translated into a 
>> description in the templates, which means there can be a translation 
>> for every installed language.
>>
>> Hope this helps,
>>
>> Katrin
>>
>> On 18.11.2016 16:12, Roger Grossmann wrote:
>>> Hi all,
>>>
>>> as a Koha development newbie I am having a few questions especially with localization.
>>> I am developing enhancements which I plan to bring in to the community hopefully soon. Your answers will help to make progress with it.
>>>
>>> 1st question
>>> ----------------
>>> After looking at much Koha code I did not find a solution to build server side localized strings to persist localized text in the database.
>>> What do you recommend to use here?
>>>
>>> Background:
>>> As you know, fines and fees are a sensitive area. Borrowers like to know exactly why they are charged and for what exactly.
>>> Lets assume, you want to store good localized name for the type of an overdue fine.
>>> It was for instance planned for function "UpdateFine" in C4::Overdues but the parameter $type is never filled as originally planned.
>>> If an additional type name would be passed here, it needed to be a localized string since borrowers want to read the charge reason in their language.
>>> As this is just an example for the use of a localized server text, the question is, whether there is already an approach to manage localised server side texts.
>>> Ideally, server side texts would support parameter replacement that is not dependent of the position in the text as for instance with %s using sprintf.
>>>
>>> 2nd question
>>> -----------------
>>> I want to build some new UI functionality. The procedure how to do that with templates in english first is clear to me.
>>> As I am German, I would like to build during development a first German version of the template as well and would like to extend the related German .po file.
>>> How can I add the texts for a specific language in my development environment?
>>> Is there a way to extract the new texts of templates and add them to an existing .po file with a script and use poedit to translate them?
>>> How do you do that?
>>>
>>> Thanks in advance for your help.
>>>
>>> Best regards,
>>> Roger
>>>
>>>
>>> --
>>> Roger Gro?mann
>>> LMSCloud GmbH
>>> Konrad-Zuse-Platz 8 - D-81829 M?nchen
>>> t +49 (0)89 207042-620  m +49 (0)171-2194775 f +49 (0)89 207042-623
>>> eroger.grossmann at lmscloud.de
>>> wwww.lmscloud.de
>>>
>>> _______________________________________________
>>> 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 
>> <mailto:Koha-devel at lists.koha-community.org>
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161129/e345e771/attachment-0001.html>

From petter.goksoyr.asen at kul.oslo.kommune.no  Mon Nov 28 09:18:42 2016
From: petter.goksoyr.asen at kul.oslo.kommune.no (=?iso-8859-1?Q?Petter_Goks=F8yr_=C5sen?=)
Date: Mon, 28 Nov 2016 08:18:42 +0000
Subject: [Koha-devel] Koha and Qvarn,
 a suggestion (also too long for anyone to finish reading)
In-Reply-To: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
References: <20161125145601.ulmeq6bmaiwwxfaw@exolobe3>
Message-ID: <0fc535bd95644a918b7df368e44622e5@MAIL231608.oslofelles.oslo.kommune.no>

Hi,

>From my brief reading of the Qvarn documentation it seems like a solid piece of
well-thought out enginerring.

However, to replace Koha's database interaction with Qvarn would be an enourmus
task, as well as increasing the complexity of the deployment manyfold with additional
layers, servers and programming languages.

If I where to design a library system from scratch today, Qvarn is something to consider,
but to rewrite a big portion of Koha codebase now seems quite a challenge!

I am by no means negative, just trying to look realsitic at it - who is going to put
in all theese hours to do the work?

Petter Goks?yr ?sen
Deichmanske bibliotek / Oslo Public Library
________________________________________
Fra: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] p? vegne av Lars Wirzenius [liw at qvarnlabs.com]
Sendt: 25. november 2016 15:56
Til: koha-devel at lists.koha-community.org
Emne: [Koha-devel] Koha and Qvarn, a suggestion (also too long for anyone to finish reading)

Hi, Koha developers,

some of you may remember me from the Debian packaging of Koha I made
in 2010 for Catalyst IT. I've never looked much at the actual code
base of Koha, but one thing that even a quick grep reveals is that SQL
code is sprinkled all over the code base. To me, this indicates that
the application code ("business logic") and the way data is stored are
closely coupled, and that's generally not a good thing. Among other
things, if there's a need so change the database schema, or database
engine, the whole code base might be affected.

In my current job we develop a storage system (roughly, "database, but
with better access control") with an emphasis on privacy. Our software
is free software released under the Affero GPL, version 3 or later. I
suggest that our software (called Qvarn) would be worth considering
for Koha.

A summary of my impression of the situation:

* Koha stores very sensitive information about people's reading
  habits.

* In the EU the new General Data Protection Regulation (GDPR) is in
  effect (with a transition period until some time in 2014), which
  requires everyone who collects or stores personal information to
  take good care so the data doesn't leak and violate people's
  privacy. Koha, or at least libraries using Koha, would seem to fall
  under this (IANAL, TINLA, AYOL).

* At minimum, a "privacy impact assessment" needs to be made.
  Basically, think about what the happens to the people whose data it
  is that gets leaked. (Best to assume it will be.)

* Koha stores all its data (including the personal stuff) in
  MySQL/MariaDB. There is no clean abstraction layer, which means SQL
  is all over the code base, making things harder to change. I think
  it would be good for Koha to add an abstraction layer even if Koha
  stays with MySQL.

* Qvarn was designed from the ground up with privacy and security in
  mind. It is meant to be the least weak link in the chain to protect
  privacy of the data it stores. It's still under active development,
  and doesn't have all the planned features yet. It's backed by my new
  company, QvarnLabs, and is in production use already, storing around
  a million personal identities.

* Qvarn provides a RESTful HTTP(S) JSON API, meaning there's no
  per-client/per-user session state on the Qvarn side. Makes it really
  easy to use, from the client, in my opinion. All data is in JSON
  form, which also makes things easier to use, in my opinion. It's
  conceptually JSON objects, not tables/columns. Qvarn uses Postgres
  behind the scenes, at least for now, but that's not visible to API
  clients (read: we could replace it with individual files on disk and
  you'd not notice).

* Qvarn requires the use of Gluu (see gluu.org) for authentication and
  authorization. Gluu is an identity management server, which is also
  free software. We aim to hide Gluu entirely behind the Qvarn API,
  and already mostly do that, so it's not something you need to know
  much about, except that operationally it's a bit tricky, since it's
  harder to deploy than Qvarn itself it (Qvarn comes as a .deb).

Here's my thoughts about Koha using Qvarn:

* First step would be to change Koha to have a suitable abstraction
  layer for storing data. I imagine this will be a big job.

* Second step would be to model the data Koha stores in Qvarn resource
  types, i.e., decide which types of records should be and what they
  should contain.

* Third step is ...

* Fourth step is profit.

Benefits to Koha as far as I can see:

* Abstraction layer: cleaner code, easier database related changes in
  the future, possibly a better test suite as a side effect.

* Qvarn: more privacy protection for user data, maybe (this is my
  highly personal and biased opinion) a nicer way to store/access the
  data.

What do you think? Is this something that the Koha community might
want? I don't want to waste your time or anyone else's time if it's
not interesting. However, if it is interesting, QvarnLabs is willing
to work on making sure Qvarn is good for Koha.

Note: though both Qvarn and Koha are developed/supported by companies,
they're free software and also free to use. This is not unlike Koha
itself.

I'm happy to answer any questions you may have, preferably on the
koha-devel list.
_______________________________________________
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 karenmyers1 at hotmail.com  Wed Nov 30 06:11:27 2016
From: karenmyers1 at hotmail.com (Karen Myers)
Date: Wed, 30 Nov 2016 05:11:27 +0000
Subject: [Koha-devel] 942 versus 952
Message-ID: <BLUPR15MB03221A1DC4C3004F10C01714FD8C0@BLUPR15MB0322.namprd15.prod.outlook.com>

Hi all


I am wanting to clarify the usage of the 942$c field versus the 952$y field as I am setting up a new bib framework.

I am wondering if it is necessary to have both the 942$c field and the 952$y field in the framework as they seem to record the same information i.e Koha item type. Is there an advantage to recording the same information in both fields and if not which is the preferred? We are using Koha 3.22
    thanks!
Karen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161130/6f397065/attachment.html>

From tomascohen at gmail.com  Wed Nov 30 11:56:10 2016
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Wed, 30 Nov 2016 10:56:10 +0000
Subject: [Koha-devel] 942 versus 952
In-Reply-To: <BLUPR15MB03221A1DC4C3004F10C01714FD8C0@BLUPR15MB0322.namprd15.prod.outlook.com>
References: <BLUPR15MB03221A1DC4C3004F10C01714FD8C0@BLUPR15MB0322.namprd15.prod.outlook.com>
Message-ID: <CABZfb=U0tc=d=p9hmAddT0HSECDGCROk56H5O3YcvrcK=36Hew@mail.gmail.com>

You only need 952$y. 942 is a fallback because all items need an phenotype,
but in the past it was not enforced, specially on import.

El mi?., 30 de nov. de 2016 2:11 AM, Karen Myers <karenmyers1 at hotmail.com>
escribi?:

Hi all


I am wanting to clarify the usage of the 942$c field versus the 952$y field
as I am setting up a new bib framework.

I am wondering if it is necessary to have both the 942$c field and the
952$y field in the framework as they seem to record the same information
i.e Koha item type. Is there an advantage to recording the same information
in both fields and if not which is the preferred? We are using Koha 3.22
    thanks!
Karen
_______________________________________________
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 <http://theke.io/>)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161130/61c5db27/attachment.html>

From francois.charbonnier at inlibro.com  Wed Nov 30 14:13:05 2016
From: francois.charbonnier at inlibro.com (Francois Charbonnier)
Date: Wed, 30 Nov 2016 08:13:05 -0500
Subject: [Koha-devel] 942 versus 952
In-Reply-To: <CABZfb=U0tc=d=p9hmAddT0HSECDGCROk56H5O3YcvrcK=36Hew@mail.gmail.com>
References: <BLUPR15MB03221A1DC4C3004F10C01714FD8C0@BLUPR15MB0322.namprd15.prod.outlook.com>
	<CABZfb=U0tc=d=p9hmAddT0HSECDGCROk56H5O3YcvrcK=36Hew@mail.gmail.com>
Message-ID: <f0eb97b4-c63a-d4da-d753-f0d12891f55b@inlibro.com>

Even if the 942 field is not mandatory, I think it's still a good 
practice to use it. The 942's itemtype allows you, when filtering by 
itemtype, to retrieve records that don't have items attached to it. 
Electronic resources for example.

Also, if you don't use the 942 field, be sure to set up the 
"item-level_itypes" system preference properly. In this case : 
item-level_itypes = specific item.

Hope it helps.

Fran?ois

Fran?ois Charbonnier,
Bibl. prof. / Chef de produits

T?l.  : (888) 604-2627
francois.charbonnier at inLibro.com <mailto:francois.charbonnier at inLibro.com>

inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com 
<http://www.inLibro.com>
Le 2016-11-30 ? 05:56, Tomas Cohen Arazi a ?crit :
> You only need 952$y. 942 is a fallback because all items need an 
> phenotype, but in the past it was not enforced, specially on import.
>
> El mi?., 30 de nov. de 2016 2:11 AM, Karen Myers 
> <karenmyers1 at hotmail.com <mailto:karenmyers1 at hotmail.com>> escribi?:
>
>     Hi all
>
>
>     I am wanting to clarify the usage of the 942$c field versus the
>     952$y field as I am setting up a new bib framework.
>
>     I am wondering if it is necessary to have both the 942$c field and
>     the 952$y field in the framework as they seem to record the same
>     information i.e Koha item type. Is there an advantage to recording
>     the same information in both fields and if not which is the
>     preferred? We are using Koha 3.22
>         thanks!
>     Karen
>
>     _______________________________________________
>     Koha-devel mailing list
>     Koha-devel at lists.koha-community.org
>     <mailto: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 <http://theke.io/>)
> ? +54 9351 3513384
> GPG: B2F3C15F
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161130/0d66e0a3/attachment.html>

From kohanews at gmail.com  Wed Nov 30 23:48:52 2016
From: kohanews at gmail.com (kohanews)
Date: Wed, 30 Nov 2016 14:48:52 -0800
Subject: [Koha-devel] Koha Community Newsletter:November 2016
Message-ID: <f9b6b556-fb5f-cfdd-1124-e871265b395c@gmail.com>

Fellow Koha users:

The Koha Community Newsletter for November 2016 is here:
https://koha-community.org/koha-community-newsletter-november-2016/

Many thanks to the folks who submitted articles and news to this month's 
newsletter.

Please feel free to email me with any corrections or suggestions.

Thanks!

-- 
Chad Roseburg
Editor, Koha Community Newsletter

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20161130/1830bfe3/attachment.html>