From martin.renvoize at ptfs-europe.com  Wed May  1 09:29:38 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Wed, 1 May 2019 08:29:38 +0100
Subject: [Koha-devel] DateTime->now usage
In-Reply-To: <CAJzKNY6Qswwr55Ymrb8czruTH06KN0AqeKtR=ZBSHVHy-zY74w@mail.gmail.com>
References: <CABZfb=UYz4MEVCg=K2gtz-BN2jPzOT1M6Cf0eTw7M5J8mD15yg@mail.gmail.com>
	<CAJzKNY6Qswwr55Ymrb8czruTH06KN0AqeKtR=ZBSHVHy-zY74w@mail.gmail.com>
Message-ID: <CAB7SL8AJKmAeXpnm-+hb0Nw-1n-VH+xE9VP7hRn6x27D+SCbBA@mail.gmail.com>

Yup,

I believe we should be consistently using dt_from_string too.

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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 Tue, 30 Apr 2019 at 18:45, Jonathan Druart <
jonathan.druart at bugs.koha-community.org> wrote:

> Hi,
>
> Yes, we must use dt_from_string.
> Note that some occurrences could stay as it: when the time_zone is passed.
>
> Cheers,
> Jonathan
>
> Le mar. 30 avr. 2019 ? 12:59, Tomas Cohen Arazi <tomascohen at gmail.com> a
> ?crit :
> >
> > Hi, on testnig bug 22453 [1] I noticed that we do the wrong thing in
> many places, actually:
> >
> > $ git grep 'DateTime\->new'
> >
> > Do you agree we should be using dt_from_string instead? The consequences
> are for those having the DB server and/or the plack server running on some
> timezone and having koha-conf.xml point to another one.
> >
> > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22453
> >
> > --
> > Tom?s Cohen Arazi
> > Theke Solutions (http://theke.io)
> > ? +54 9351 3513384
> > GPG: B2F3C15F
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : http://www.koha-community.org/
> > git : http://git.koha-community.org/
> > bugs : http://bugs.koha-community.org/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190501/2e74298b/attachment.html>

From martin.renvoize at ptfs-europe.com  Wed May  1 11:46:33 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Wed, 1 May 2019 10:46:33 +0100
Subject: [Koha-devel] Signoff request
In-Reply-To: <CADT_QRSeSLBS65EB3UygfPBMZVsJUarQN8g6s11MKBfxvKa5JA@mail.gmail.com>
References: <AM6PR05MB59763178C1FB5F4DBC89F8D0CE3E0@AM6PR05MB5976.eurprd05.prod.outlook.com>
	<CADT_QRSeSLBS65EB3UygfPBMZVsJUarQN8g6s11MKBfxvKa5JA@mail.gmail.com>
Message-ID: <CAB7SL8D29Ydi5CPd3HoNzqGKJGAOiMRmydN4TeOtZqgm7aMJUg@mail.gmail.com>

And QA'd too.

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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 Fri, 26 Apr 2019 at 07:38, Hugo Agud <info at orex.es> wrote:

> Hi Marcel
>
> thanks for the mail, I will do my best.. If I have any doubt I will mail
> you
>
> thanks
>
> El vie., 26 abr. 2019 a las 8:26, Marcel de Rooy (<
> M.de.Rooy at rijksmuseum.nl>) escribi?:
>
>> Hi all,
>>
>>
>> I have a few bugs waiting for quite some time in the queue and I need
>> your help to get them further.
>>
>>
>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20310
>>
>> Article requests
>>
>> Just 3 simple patches
>>
>> Wrote them more than a year ago, last rebase May 2018
>>
>>
>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21533
>>
>> Do not allow password recovery for administrative locked patrons
>>
>> Small follow-up on 21336, only one patch changing two lines
>>
>> Written in October, still applies
>>
>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21535
>>
>> Anonymize function in Patron should not scramble email addresses
>>
>> Small followup on 21336, just one patch, 5 insertions, 2 deletions
>>
>> Also written in October, rebased
>>
>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21036
>>
>> Fix a bunch of older warnings
>>
>> Three small patches, resolving a few warnings
>> Written July 2018, last change October
>>
>>
>> Thanks,
>>
>> Marcel
>>
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>
>
>
> --
>
> *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>
>
>
> Director
>
> Avda Josep Tarradelles, 134 (Centro de Negocios Infanta) 08029 - Barcelona
> - 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-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/20190501/56174a72/attachment-0001.html>

From martin.renvoize at ptfs-europe.com  Wed May  1 11:52:30 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Wed, 1 May 2019 10:52:30 +0100
Subject: [Koha-devel] Removal of hidelostitems syspref
In-Reply-To: <057b8546-5074-ffe7-79a1-352cee40e84f@biblibre.com>
References: <CABZfb=Xjp0rrOrwHZs3v_Y9_D7TqJp9D9SMQ=tmeCOrAGzKh7g@mail.gmail.com>
	<057b8546-5074-ffe7-79a1-352cee40e84f@biblibre.com>
Message-ID: <CAB7SL8BepUrBiUXMYC+J3-MjNDaOAOd5_zy5A49bX7ntdjcSqA@mail.gmail.com>

It gets the vote from me too so long as we can work out how to take into
account Katrins point on the bug.


*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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 Tue, 23 Apr 2019 at 16:38, Fridolin SOMERS <fridolin.somers at biblibre.com>
wrote:

> We at Biblibre have nearly 1 Koha on 2 that use this syspref.
>
> For moving this to OpacHiddenItems, i think we need a negativ condition
> saying "hide items not(itemlost=0)".
> Maybe some real administration page to manage this behavior.
>
> Regards,
>
> Le 22/04/2019 ? 18:56, Tomas Cohen Arazi a ?crit :
> > Hi all, I wanted to ask for opinions about removing the mentioned
> syspref.
> > This is proposed on bug 8619, in which Owen already made a proposal for
> an
> > enhancement so this is painless for users.
> >
> > Thanks for your feedback.
> >
> >
> > _______________________________________________
> > 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 <fridolin.somers at biblibre.com>
> BibLibre, France - software and system maintainer
> _______________________________________________
> 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/20190501/c9548282/attachment.html>

From martin.renvoize at ptfs-europe.com  Wed May  1 12:06:24 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Wed, 1 May 2019 11:06:24 +0100
Subject: [Koha-devel] Discussion of account types / labels
In-Reply-To: <080501d4ce5c$cb8bb1f0$62a315d0$@prosentient.com.au>
References: <CAMSJbVsybWA-Vg3raxGUB+kO0AeYDvHUKeEMeTeDDHLWWG6ANg@mail.gmail.com>
	<2bd2d26f-9583-c21d-7b8a-432394567e15@biblibre.com>
	<AEC156F2-DFD3-47A9-86FD-6C0C29461B09@catalyst.net.nz>
	<CAMSJbVtUC=vDGCFpJ_018qwTa6Mc9miH8J6kLx7oGNMk3Ugjhg@mail.gmail.com>
	<06ea01d4cd5f$5feb7280$1fc25780$@prosentient.com.au>
	<daa63e26-02eb-0da3-1b96-694d1555b891@web.de>
	<080501d4ce5c$cb8bb1f0$62a315d0$@prosentient.com.au>
Message-ID: <CAB7SL8Czw8aypds+MibD8obFk0ogbcnsSac1u3SWpxYKYz2C8w@mail.gmail.com>

I've been working on cleaning up these codes as a first step towards other
improvements in this area..

There are a few bugs still in the NSO stages and I think it would be really
beneficial to keep that tree moving forward as we're now in a half and half
state in master (and thus 19.05 if we don't push these through).. Any help
with the following bugs would be gratefully received.

Bug 22563 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22563>
- Convert lost handling to use 'status' instead of multiple accounttypes
Bug 11573 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11573>
- Fine descriptions related to Rentals are untranslatable
Bug 6759 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6759> -
Use a different account type for account renewals than for new accounts
Bug 22610 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22610>
- SIP Payment Types should be moved out of accountype

My hope is to get these one's in now to clear the way for working on
resurrecting "Bug 17702
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17702> - Create
configuration for account types" during the next cycle

Many thanks,

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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 Wed, 27 Feb 2019 at 05:25, David Cook <dcook at prosentient.com.au> wrote:

> Hi Katrin,
>
>
>
> I don?t understand your email. My suggestion would yield support for
> different languages (for anything using Template Toolkit templates). As far
> as I understand, that?s how we currently provide internationalization
> support in Koha. Am I missing something?
>
>
>
> Admittedly, I haven?t done much with the REST API yet, but I assume that
> the API would just deal with codes? And if we were calling the API from the
> OPAC, we?d just use templates that rely on the codes.
>
>
>
> David Cook
>
> Systems Librarian
>
> Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Direct: 02 8005 0595
>
>
>
> *From:* koha-devel-bounces at lists.koha-community.org [mailto:
> koha-devel-bounces at lists.koha-community.org] *On Behalf Of *Katrin Fischer
> *Sent:* Tuesday, 26 February 2019 5:28 PM
> *To:* koha-devel at lists.koha-community.org
> *Subject:* Re: [Koha-devel] Discussion of account types / labels
>
>
>
> Hi all,
>
> please keep in mind that 'translated' doesn't mean into one language, but
> should allow for supporting different languages at the same time,
> especially if those descriptions were to be used for APIs as well.
>
> Katrin
>
> On 26.02.19 00:11, David Cook wrote:
>
> I was pondering this yesterday as well.
>
>
>
> I figure a lookup table in the database that contains the code and a
> description (for reporting and administration purposes), but use
> translatable strings in templates using the code as hooks.
>
>
>
> David Cook
>
> Systems Librarian
>
> Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Direct: 02 8005 0595
>
>
>
> *From:* koha-devel-bounces at lists.koha-community.org [
> mailto:koha-devel-bounces at lists.koha-community.org
> <koha-devel-bounces at lists.koha-community.org>] *On Behalf Of *Barton
> Chittenden
> *Sent:* Tuesday, 26 February 2019 12:58 AM
> *To:* Chris Cormack <chrisc at catalyst.net.nz> <chrisc at catalyst.net.nz>
> *Cc:* Koha-devel <koha-devel at lists.koha-community.org>
> <koha-devel at lists.koha-community.org>
> *Subject:* Re: [Koha-devel] Discussion of account types / labels
>
>
>
>
>
>
>
> On Mon, Feb 25, 2019 at 6:51 AM Chris Cormack <chrisc at catalyst.net.nz>
> wrote:
>
>
> Whatever they are changed to needs to be translatable.
>
>
>
> Agreed. I suspect that the trade-offs between 'We would like this to be
> translatable' and 'we need these values to be un-editable' (I.e. not
> authorized values) are probably what's kept things as they are.
>
>
>
> _______________________________________________
>
> 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/20190501/46942bff/attachment.html>

From dcook at prosentient.com.au  Thu May  2 02:17:28 2019
From: dcook at prosentient.com.au (dcook at prosentient.com.au)
Date: Thu, 2 May 2019 10:17:28 +1000
Subject: [Koha-devel] DateTime->now usage
In-Reply-To: <CAB7SL8AJKmAeXpnm-+hb0Nw-1n-VH+xE9VP7hRn6x27D+SCbBA@mail.gmail.com>
References: <CABZfb=UYz4MEVCg=K2gtz-BN2jPzOT1M6Cf0eTw7M5J8mD15yg@mail.gmail.com>	<CAJzKNY6Qswwr55Ymrb8czruTH06KN0AqeKtR=ZBSHVHy-zY74w@mail.gmail.com>
	<CAB7SL8AJKmAeXpnm-+hb0Nw-1n-VH+xE9VP7hRn6x27D+SCbBA@mail.gmail.com>
Message-ID: <085401d5007c$6d532d50$47f987f0$@prosentient.com.au>

Great catch, Tomas. I totally agree. 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: koha-devel-bounces at lists.koha-community.org <koha-devel-bounces at lists.koha-community.org> On Behalf Of Renvoize, Martin
Sent: Wednesday, 1 May 2019 5:30 PM
To: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] DateTime->now usage

 

Yup, 

 

I believe we should be consistently using dt_from_string too.




	

 


Martin Renvoize

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


Development Team Manager


 


 


Phone: +44 (0) 1483 378728

Mobile: +44 (0) 7725 985 636


Email:  <mailto:martin.renvoize at ptfs-europe.com> martin.renvoize at ptfs-europe.com

Fax: +44 (0) 800 756 6384

	
 <https://www.ptfs-europe.com> 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 <mailto:info at ptfs-europe.com> 

 

 

 

On Tue, 30 Apr 2019 at 18:45, Jonathan Druart <jonathan.druart at bugs.koha-community.org <mailto:jonathan.druart at bugs.koha-community.org> > wrote:

Hi,

Yes, we must use dt_from_string.
Note that some occurrences could stay as it: when the time_zone is passed.

Cheers,
Jonathan

Le mar. 30 avr. 2019 ? 12:59, Tomas Cohen Arazi <tomascohen at gmail.com <mailto:tomascohen at gmail.com> > a ?crit :
>
> Hi, on testnig bug 22453 [1] I noticed that we do the wrong thing in many places, actually:
>
> $ git grep 'DateTime\->new'
>
> Do you agree we should be using dt_from_string instead? The consequences are for those having the DB server and/or the plack server running on some timezone and having koha-conf.xml point to another one.
>
> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22453
>
> --
> Tom?s Cohen Arazi
> Theke Solutions (http://theke.io)
> ? +54 9351 3513384
> GPG: B2F3C15F
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org <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 <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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190502/e15d6e0b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190502/e15d6e0b/attachment-0001.pgp>

From kohanews at gmail.com  Thu May  2 05:04:25 2019
From: kohanews at gmail.com (kohanews)
Date: Wed, 1 May 2019 20:04:25 -0700
Subject: [Koha-devel] Koha Community Newsletter: April 2019
Message-ID: <ca440678-ee52-7d2e-2645-744b7c99afd9@gmail.com>

The Koha Community Newsletter for April 2019 is here:
https://koha-community.org/koha-community-newsletter-april-2019/

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.

-- 
Chad Roseburg
Editor, Koha Community Newsletter

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

From martin.renvoize at ptfs-europe.com  Thu May  2 15:15:41 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Thu, 2 May 2019 14:15:41 +0100
Subject: [Koha-devel] Koha 18.11.05, 18.05.12 and 17.11.18 release
Message-ID: <CAB7SL8CXeTWsY27HUfAniavzFTKSMDghjS0z90YmetCzTAqEvg@mail.gmail.com>

The Koha community is proud to announce the release of Koha versions
18.11.05, 18.05.12 and 17.11.18.

These are combined security and maintenance releases and we recommend you
update your systems at your earliest convenience.

Debian packages have been uploaded and are available as of now, and
detailed release notes for each respective version can be found below:

18.11.05 - https://koha-community.org/koha-18-11-05-release/
18.05.12 - https://koha-community.org/koha-18-05-12-release/
17.11.18 - https://koha-community.org/koha-17-11-18-release/

My apologies for the delay in this release, we felt it pertinent to try and
avoid as many of the bank holidays as possible.

Many thanks to all who have contributed to these releases,

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190502/365053ff/attachment.html>

From fridolin.somers at biblibre.com  Thu May  2 15:57:48 2019
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Thu, 2 May 2019 15:57:48 +0200
Subject: [Koha-devel] Koha 18.11.05, 18.05.12 and 17.11.18 release
In-Reply-To: <CAB7SL8CXeTWsY27HUfAniavzFTKSMDghjS0z90YmetCzTAqEvg@mail.gmail.com>
References: <CAB7SL8CXeTWsY27HUfAniavzFTKSMDghjS0z90YmetCzTAqEvg@mail.gmail.com>
Message-ID: <d8d9c8eb-d4a2-ac15-dae2-f44407e32140@biblibre.com>

Thanks a lot Martin and other for this release.

Note that this aim to be 17.11.x last release.
I applyed for 19.05.x maintaining.

Best regards,

Le 02/05/2019 ? 15:15, Renvoize, Martin a ?crit?:
> The Koha community is proud to announce the release of Koha versions
> 18.11.05, 18.05.12 and 17.11.18.
> 
> These are combined security and maintenance releases and we recommend you
> update your systems at your earliest convenience.
> 
> Debian packages have been uploaded and are available as of now, and
> detailed release notes for each respective version can be found below:
> 
> 18.11.05 - https://koha-community.org/koha-18-11-05-release/
> 18.05.12 - https://koha-community.org/koha-18-05-12-release/
> 17.11.18 - https://koha-community.org/koha-17-11-18-release/
> 
> My apologies for the delay in this release, we felt it pertinent to try and
> avoid as many of the bank holidays as possible.
> 
> Many thanks to all who have contributed to these releases,
> 
> *Martin Renvoize*
> 
> <https://www.ptfs-europe.com>
> 
> Development Team Manager
> 
> 
> 
> 
> 
> *Phone:* +44 (0) 1483 378728
> 
> *Mobile:* +44 (0) 7725 985 636
> 
> *Email:* martin.renvoize at ptfs-europe.com
> 
> *Fax:* +44 (0) 800 756 6384
> 
> 
> 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
> 
> 
> _______________________________________________
> 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 <fridolin.somers at biblibre.com>
BibLibre, France - software and system maintainer

From kohanews at gmail.com  Wed May 15 01:17:47 2019
From: kohanews at gmail.com (kohanews)
Date: Tue, 14 May 2019 16:17:47 -0700
Subject: [Koha-devel] Call for News: May 2019 Newsletter
Message-ID: <afef6405-2131-2789-0502-e924f721101e@gmail.com>

Hello all!

I'm collecting news for the May 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.

Thank you!

-- 
Chad Roseburg
Editor, Koha Community Newsletter


From paul.poulain at biblibre.com  Fri May 17 09:46:06 2019
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Fri, 17 May 2019 09:46:06 +0200
Subject: [Koha-devel] app bureau jitsi
Message-ID: <0c751b79-8c48-4ee5-7851-ac6022db432b@biblibre.com>

Hello,

l'un d'entre vous connait il : 
https://jitsi.org/news/remote-desktop-control-and-always-on-top-view-with-the-new-jitsi-meet-desktop-app/ 
? d?j? essay? ? utilisable ?

-- 
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  Fri May 17 09:46:34 2019
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Fri, 17 May 2019 09:46:34 +0200
Subject: [Koha-devel] app bureau jitsi
In-Reply-To: <0c751b79-8c48-4ee5-7851-ac6022db432b@biblibre.com>
References: <0c751b79-8c48-4ee5-7851-ac6022db432b@biblibre.com>
Message-ID: <1de9cd0f-a3ef-f8f0-b391-5e2df06f8455@biblibre.com>

oups, sorry, wrong address...

Le 17/05/2019 ? 09:46, Paul Poulain a ?crit?:
> Hello,
>
> l'un d'entre vous connait il : 
> https://jitsi.org/news/remote-desktop-control-and-always-on-top-view-with-the-new-jitsi-meet-desktop-app/ 
> ? d?j? essay? ? utilisable ?
>
-- 
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 s.graham4 at herts.ac.uk  Mon May 20 13:17:50 2019
From: s.graham4 at herts.ac.uk (Stephen Graham)
Date: Mon, 20 May 2019 11:17:50 +0000
Subject: [Koha-devel] Restful API question
Message-ID: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>

Hi all - I know it's Kohacon this week so a lot of people will be busy there, but just in case ......... (also sorry for the length of the email!):

I testing creating a custom API endpoint using the Koha plugin system. I've been using the code in the Kitchen sink plugin as a template, and it seems to be working well apart from my lack of Swagger/OpenAPI knowledge - I think it's this I struggling with. I have three files:

koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm
koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm
koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json

The work is done in NotificationController.pm where I have a DBI call to get the following fields:

Borrower.userid
Message_queue.message_id
Message_queue.subject
Message_queue.content

I fetch the data, and convert into JSON (encode_json is a method from Mojo::JSON) like:

my $data = $sth->fetchall_arrayref({}); # return both fieldnames and values
my $json = encode_json($data);

if I then do (i.e. use text):

return $c->render( status => 200, text => $json)

it works fine. If I call https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I get json like:

[ {
               "body": "blah blah",
               "messageid": "1234567",
               "subject": "Important...",
               "userid":  99999999"
} {
               Etc etc
}]

So in Perl terms it's an array of hashes. Which is what I want. However, if I try and use the openapi way that all the current "official" Koha endpoints use e.g.

return $c->render( status => 200, openapi => { notices => $json } );

it just doesn't work. I have tried to map the field names with the appropriate types in openapi.json. I've tried object type with properties e.g.

"responses": {
        "200": {
          "description": "A list of pending notices",
          "schema": {
                "type": "object",
                "properties": {
                "userid": {
                        "type": "string",
                        "description": "Unique User ID"
                }, etc

, and I've tried array type with items:

"responses": {
        "200": {
          "description": "A list of pending notices",
          "schema": {
                "type": "array",
                "items": {
                "userid": {
                        "type": "string",
                        "description": "Unique User ID"
                }, etc

But I get a page not found error. When I pass my $json variable to the render method using openapi how do I get it to work? I'm happy to use the text way, but I want to understand where I'm going wrong. Any ideas, hints, tips would be most welcome!

Cheers, Stephen

--------------------------------------
Stephen Graham
Library Technology Consultant
Content and Collections Team
Library and Computing Services
University of Hertfordshire
Tel: 01707 286111
Ext: 77751
Email: s.graham4 at herts.ac.uk<mailto:s.graham4 at herts.ac.uk>

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

From tomascohen at gmail.com  Mon May 20 13:27:44 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 20 May 2019 08:27:44 -0300
Subject: [Koha-devel] Restful API question
In-Reply-To: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
References: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CABZfb=X4dL3EUjWPCCVhuubbwT58RW5KQNFHaXJdASs1mSEhsQ@mail.gmail.com>

The most probable problem is the OpenAPI spec is wrong, and then the plugin
API is skipped altogether.

If possible, share the openapi.json file in your plugin

El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4 at herts.ac.uk>
escribi?:

> Hi all ? I know it?s Kohacon this week so a lot of people will be busy
> there, but just in case ??? (also sorry for the length of the email!):
>
>
>
> I testing creating a custom API endpoint using the Koha plugin system.
> I?ve been using the code in the Kitchen sink plugin as a template, and it
> seems to be working well apart from my lack of Swagger/OpenAPI knowledge ?
> I think it?s this I struggling with. I have three files:
>
>
>
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm
>
>
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm
>
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json
>
>
>
> The work is done in NotificationController.pm where I have a DBI call to
> get the following fields:
>
>
>
> Borrower.userid
>
> Message_queue.message_id
>
> Message_queue.subject
>
> Message_queue.content
>
>
>
> I fetch the data, and convert into JSON (encode_json is a method from
> Mojo::JSON) like:
>
>
>
> my $data = $sth->fetchall_arrayref({}); # return both fieldnames and values
>
> my $json = encode_json($data);
>
>
>
> if I then do (i.e. use text):
>
>
>
> return $c->render( status => 200, text => $json)
>
>
>
> it works fine. If I call
> https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I
> get json like:
>
>
>
> [ {
>
>                ?body?: ?blah blah?,
>
>                ?messageid?: ?1234567?,
>
>                ?subject?: ?Important??,
>
>                ?userid?:  99999999?
>
> } {
>
>                Etc etc
>
> }]
>
>
>
> So in Perl terms it?s an array of hashes. Which is what I want. However,
> if I try and use the openapi way that all the current ?official? Koha
> endpoints use e.g.
>
>
>
> return $c->render( status => 200, openapi => { notices => $json } );
>
>
>
> it just doesn?t work. I have tried to map the field names with the
> appropriate types in openapi.json. I?ve tried object type with properties
> e.g.
>
>
>
> "responses": {
>
>         "200": {
>
>           "description": "A list of pending notices",
>
>           "schema": {
>
>                 "type": "object",
>
>                 "properties": {
>
>                 "userid": {
>
>                         "type": "string",
>
>                         "description": "Unique User ID"
>
>                 }, etc
>
>
>
> , and I?ve tried array type with items:
>
>
>
> "responses": {
>
>         "200": {
>
>           "description": "A list of pending notices",
>
>           "schema": {
>
>                 "type": "array",
>
>                 "items": {
>
>                 "userid": {
>
>                         "type": "string",
>
>                         "description": "Unique User ID"
>
>                 }, etc
>
>
>
> But I get a page not found error. When I pass my $json variable to the
> render method using openapi how do I get it to work? I?m happy to use the
> text way, but I want to understand where I?m going wrong. Any ideas, hints,
> tips would be most welcome!
>
>
>
> Cheers, Stephen
>
>
>
> --------------------------------------
>
> Stephen Graham
>
> Library Technology Consultant
>
> Content and Collections Team
>
> Library and Computing Services
>
> University of Hertfordshire
>
> Tel: 01707 286111
>
> Ext: 77751
>
> Email: s.graham4 at herts.ac.uk
>
>
> _______________________________________________
> 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/20190520/b9b5fa40/attachment-0001.html>

From tomascohen at gmail.com  Mon May 20 15:25:17 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 20 May 2019 10:25:17 -0300
Subject: [Koha-devel] Restful API question
In-Reply-To: <CWXP265MB1527F16A95517E5272574E60E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
References: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
	<CABZfb=X4dL3EUjWPCCVhuubbwT58RW5KQNFHaXJdASs1mSEhsQ@mail.gmail.com>
	<CWXP265MB1527F16A95517E5272574E60E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CABZfb=VL7Uu2dw_XV9Jxh5qRHibpzyUVXkSEiK+cDVTqyWrcWw@mail.gmail.com>

I think it should read like:

"200": {
    "description": "A list pending notifications",
    "schema": {
        "type": "array",
        "items": {
            "type": "object",
            "properties": {
                "userid": {
                        "type": "string",
                        "description": "Unique User ID"
                },
                ...
            }
        }
    }
}

You can of course under-specify it, just saying you return JSON or the way
you did it, just avoiding OpenAPI altogether, but you loose the ability for
consumers to have a well documented API, and also you loose data validation
(in and out), which is very important when implementing the API.

Happy to see others playing with this! Let me know how can I help1


El lun., 20 may. 2019 a las 10:05, Stephen Graham (<s.graham4 at herts.ac.uk>)
escribi?:
>
> Hi Tomas ? the below is what I have. When I do my sql select I?m doing:
>
>
>
> select b.userid as userid,
>
> mq.message_id as messageid,
>
> mq.subject as subject,
>
> mq.content as body
>
>
>
> ,so the field names should map to the item names in the openapi.json. I?m
just not sure what I should be passing to the render method, and how to
describe that in the openapi.json file. At the moment I?m passing a string
? it?s JSON ? but just a string. Maybe that isn?t right? When I look to see
how the Patrons API does it, it works like:
>
>
>
> my @patrons = $patrons->as_list;
>
> @patrons = map { _to_api( $_->TO_JSON ) } @patrons;
>
> return $c->render( status => 200, openapi => \@patrons );
>
>
>
> and then seems to say it?s an array of objects in their json files
(patron.json and patron.json).
>
>
>
> Here is my openapi.json file:
>
>
>
> {
>
>   "/notifications": {
>
>     "get": {
>
>       "x-mojo-to":
"Uk::Ac::Herts::Notifications::NotificationController#getPendingNotices",
>
>       "operationId": "PatronEmailNotice",
>
>       "tags": ["notifications"],
>
>       "produces": [
>
>         "application/json"
>
>       ],
>
>       "responses": {
>
>         "200": {
>
>           "description": "A list of pending notices",
>
>           "schema": {
>
>                 "type": "array",
>
>                 "items": {
>
>                 "userid": {
>
>                         "type": "string",
>
>                         "description": "Unique User ID"
>
>                 },
>
>                 "messageid": {
>
>                         "type": "string",
>
>                         "description": "Unique Notice ID"
>
>                 },
>
>                 "subject": {
>
>                         "type": "string",
>
>                         "description": "Notice Subject"
>
>                 },
>
>                 "body": {
>
>                         "type": "string",
>
>                         "description": "Notice Body"
>
>                 }
>
>                 }
>
>                 }
>
>         },
>
>         "404": {
>
>           "description": "An error occured",
>
>           "schema": {
>
>               "type": "object",
>
>                 "properties": {
>
>                   "error": {
>
>                     "description": "An explanation for the error",
>
>                     "type": "string"
>
>                   }
>
>                 }
>
>           }
>
>         }
>
>       },
>
>       "x-koha-authorization": {
>
>         "permissions": {
>
>           "borrowers": "1"
>
>         }
>
>       }
>
>     }
>
>   }
>
> }
>
>
>
> From: Tomas Cohen Arazi <tomascohen at gmail.com>
> Sent: 20 May 2019 12:28
> To: Stephen Graham <s.graham4 at herts.ac.uk>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: Re: [Koha-devel] Restful API question
>
>
>
> The most probable problem is the OpenAPI spec is wrong, and then the
plugin API is skipped altogether.
>
>
>
> If possible, share the openapi.json file in your plugin
>
>
>
> El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4 at herts.ac.uk>
escribi?:
>
> Hi all ? I know it?s Kohacon this week so a lot of people will be busy
there, but just in case ??? (also sorry for the length of the email!):
>
>
>
> I testing creating a custom API endpoint using the Koha plugin system.
I?ve been using the code in the Kitchen sink plugin as a template, and it
seems to be working well apart from my lack of Swagger/OpenAPI knowledge ?
I think it?s this I struggling with. I have three files:
>
>
>
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm
>
>
koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm
>
>
koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json
>
>
>
> The work is done in NotificationController.pm where I have a DBI call to
get the following fields:
>
>
>
> Borrower.userid
>
> Message_queue.message_id
>
> Message_queue.subject
>
> Message_queue.content
>
>
>
> I fetch the data, and convert into JSON (encode_json is a method from
Mojo::JSON) like:
>
>
>
> my $data = $sth->fetchall_arrayref({}); # return both fieldnames and
values
>
> my $json = encode_json($data);
>
>
>
> if I then do (i.e. use text):
>
>
>
> return $c->render( status => 200, text => $json)
>
>
>
> it works fine. If I call
https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I
get json like:
>
>
>
> [ {
>
>                ?body?: ?blah blah?,
>
>                ?messageid?: ?1234567?,
>
>                ?subject?: ?Important??,
>
>                ?userid?:  99999999?
>
> } {
>
>                Etc etc
>
> }]
>
>
>
> So in Perl terms it?s an array of hashes. Which is what I want. However,
if I try and use the openapi way that all the current ?official? Koha
endpoints use e.g.
>
>
>
> return $c->render( status => 200, openapi => { notices => $json } );
>
>
>
> it just doesn?t work. I have tried to map the field names with the
appropriate types in openapi.json. I?ve tried object type with properties
e.g.
>
>
>
> "responses": {
>
>         "200": {
>
>           "description": "A list of pending notices",
>
>           "schema": {
>
>                 "type": "object",
>
>                 "properties": {
>
>                 "userid": {
>
>                         "type": "string",
>
>                         "description": "Unique User ID"
>
>                 }, etc
>
>
>
> , and I?ve tried array type with items:
>
>
>
> "responses": {
>
>         "200": {
>
>           "description": "A list of pending notices",
>
>           "schema": {
>
>                 "type": "array",
>
>                 "items": {
>
>                 "userid": {
>
>                         "type": "string",
>
>                         "description": "Unique User ID"
>
>                 }, etc
>
>
>
> But I get a page not found error. When I pass my $json variable to the
render method using openapi how do I get it to work? I?m happy to use the
text way, but I want to understand where I?m going wrong. Any ideas, hints,
tips would be most welcome!
>
>
>
> Cheers, Stephen
>
>
>
> --------------------------------------
>
> Stephen Graham
>
> Library Technology Consultant
>
> Content and Collections Team
>
> Library and Computing Services
>
> University of Hertfordshire
>
> Tel: 01707 286111
>
> Ext: 77751
>
> Email: s.graham4 at herts.ac.uk
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/



--
Tom?s Cohen Arazi
Theke Solutions (http://theke.io)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190520/779aa0c4/attachment.html>

From tomascohen at gmail.com  Mon May 20 17:25:54 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 20 May 2019 12:25:54 -0300
Subject: [Koha-devel] Restful API question
In-Reply-To: <CWXP265MB1527BD3F1C488C96C4240057E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
References: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
	<CABZfb=X4dL3EUjWPCCVhuubbwT58RW5KQNFHaXJdASs1mSEhsQ@mail.gmail.com>
	<CWXP265MB1527F16A95517E5272574E60E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
	<CABZfb=VL7Uu2dw_XV9Jxh5qRHibpzyUVXkSEiK+cDVTqyWrcWw@mail.gmail.com>
	<CWXP265MB1527BD3F1C488C96C4240057E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CABZfb=W7twAopjOgB8_Zz9s-i1noZVxKet7bbtX03fAe9DoWQg@mail.gmail.com>

The _to_api method is required in patrons endpoint, only because we don't
want to expose exactly the same attribute names as the DB columns and some
others are just generated.

So you need to make the objects match your spec.

El lun., 20 de mayo de 2019 11:40, Stephen Graham <s.graham4 at herts.ac.uk>
escribi?:

> Hi Tomas ? the ability to extend the API with custom endpoints using the
> plugin system is a great Koha feature! ?
>
>
>
> If I change my openapi.json to what you suggest I get:
>
>
>
> {"errors":[{"message":"Expected array - got
> string.","path":"\/"}],"status":500}
>
>
>
> , so I guess I need to pass my data to the render method as an array and
> not as a JSON string? If I do this I?m getting a can?t call method on
> unblessed refence error:
>
>
>
> my @n = map { ( $_->encode_json ) } @{$notices};
>
> return $c->render( status => 200, openapi => \@n );
>
>
>
> I guess because @{$notices} is an array of hashes? I see in the Patrons.pm
> REST module, that they are using a method called _*to*_api, which
> according to the Perl doc:
>
>
>
> ?Helper function that maps unblessed Koha::Patron objects into REST api
> attribute names.?
>
>
>
> Sorry, it might be obvious, but do I need to iterate though my results and
> convert them into?. I?m not sure what really. Looking at the _*to*_api
>  method it just seems to be mapping the database column names to the API
> names, which I have done already in my initial sql query, and returns a
> Patron object. Should I be able to do what I want with the data structure I
> get from a fetchall_arrayref({})?
>
>
>
> Cheers, Stephen
>
>
>
>
>
> *From:* Tomas Cohen Arazi <tomascohen at gmail.com>
> *Sent:* 20 May 2019 14:25
> *To:* Stephen Graham <s.graham4 at herts.ac.uk>
> *Cc:* koha-devel <koha-devel at lists.koha-community.org>
> *Subject:* Re: [Koha-devel] Restful API question
>
>
>
> I think it should read like:
>
> "200": {
>     "description": "A list pending notifications",
>     "schema": {
>         "type": "array",
>         "items": {
>             "type": "object",
>             "properties": {
>                 "userid": {
>                         "type": "string",
>                         "description": "Unique User ID"
>                 },
>                 ...
>             }
>         }
>     }
> }
>
> You can of course under-specify it, just saying you return JSON or the way
> you did it, just avoiding OpenAPI altogether, but you loose the ability for
> consumers to have a well documented API, and also you loose data validation
> (in and out), which is very important when implementing the API.
>
>
>
> Happy to see others playing with this! Let me know how can I help1
>
>
>
> El lun., 20 may. 2019 a las 10:05, Stephen Graham (<s.graham4 at herts.ac.uk>)
> escribi?:
> >
> > Hi Tomas ? the below is what I have. When I do my sql select I?m doing:
> >
> >
> >
> > select b.userid as userid,
> >
> > mq.message_id as messageid,
> >
> > mq.subject as subject,
> >
> > mq.content as body
> >
> >
> >
> > ,so the field names should map to the item names in the openapi.json.
> I?m just not sure what I should be passing to the render method, and how to
> describe that in the openapi.json file. At the moment I?m passing a string
> ? it?s JSON ? but just a string. Maybe that isn?t right? When I look to see
> how the Patrons API does it, it works like:
> >
> >
> >
> > my @patrons = $patrons->as_list;
> >
> > @patrons = map { _to_api( $_->TO_JSON ) } @patrons;
> >
> > return $c->render( status => 200, openapi => \@patrons );
> >
> >
> >
> > and then seems to say it?s an array of objects in their json files
> (patron.json and patron.json).
> >
> >
> >
> > Here is my openapi.json file:
> >
> >
> >
> > {
> >
> >   "/notifications": {
> >
> >     "get": {
> >
> >       "x-mojo-to":
> "Uk::Ac::Herts::Notifications::NotificationController#getPendingNotices",
> >
> >       "operationId": "PatronEmailNotice",
> >
> >       "tags": ["notifications"],
> >
> >       "produces": [
> >
> >         "application/json"
> >
> >       ],
> >
> >       "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "array",
> >
> >                 "items": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 },
> >
> >                 "messageid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique Notice ID"
> >
> >                 },
> >
> >                 "subject": {
> >
> >                         "type": "string",
> >
> >                         "description": "Notice Subject"
> >
> >                 },
> >
> >                 "body": {
> >
> >                         "type": "string",
> >
> >                         "description": "Notice Body"
> >
> >                 }
> >
> >                 }
> >
> >                 }
> >
> >         },
> >
> >         "404": {
> >
> >           "description": "An error occured",
> >
> >           "schema": {
> >
> >               "type": "object",
> >
> >                 "properties": {
> >
> >                   "error": {
> >
> >                     "description": "An explanation for the error",
> >
> >                     "type": "string"
> >
> >                   }
> >
> >                 }
> >
> >           }
> >
> >         }
> >
> >       },
> >
> >       "x-koha-authorization": {
> >
> >         "permissions": {
> >
> >           "borrowers": "1"
> >
> >         }
> >
> >       }
> >
> >     }
> >
> >   }
> >
> > }
> >
> >
> >
> > From: Tomas Cohen Arazi <tomascohen at gmail.com>
> > Sent: 20 May 2019 12:28
> > To: Stephen Graham <s.graham4 at herts.ac.uk>
> > Cc: koha-devel <koha-devel at lists.koha-community.org>
> > Subject: Re: [Koha-devel] Restful API question
> >
> >
> >
> > The most probable problem is the OpenAPI spec is wrong, and then the
> plugin API is skipped altogether.
> >
> >
> >
> > If possible, share the openapi.json file in your plugin
> >
> >
> >
> > El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4 at herts.ac.uk>
> escribi?:
> >
> > Hi all ? I know it?s Kohacon this week so a lot of people will be busy
> there, but just in case ??? (also sorry for the length of the email!):
> >
> >
> >
> > I testing creating a custom API endpoint using the Koha plugin system.
> I?ve been using the code in the Kitchen sink plugin as a template, and it
> seems to be working well apart from my lack of Swagger/OpenAPI knowledge ?
> I think it?s this I struggling with. I have three files:
> >
> >
> >
> > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm
> >
> >
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm
> >
> >
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json
> >
> >
> >
> > The work is done in NotificationController.pm where I have a DBI call to
> get the following fields:
> >
> >
> >
> > Borrower.userid
> >
> > Message_queue.message_id
> >
> > Message_queue.subject
> >
> > Message_queue.content
> >
> >
> >
> > I fetch the data, and convert into JSON (encode_json is a method from
> Mojo::JSON) like:
> >
> >
> >
> > my $data = $sth->fetchall_arrayref({}); # return both fieldnames and
> values
> >
> > my $json = encode_json($data);
> >
> >
> >
> > if I then do (i.e. use text):
> >
> >
> >
> > return $c->render( status => 200, text => $json)
> >
> >
> >
> > it works fine. If I call
> https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I
> get json like:
> >
> >
> >
> > [ {
> >
> >                ?body?: ?blah blah?,
> >
> >                ?messageid?: ?1234567?,
> >
> >                ?subject?: ?Important??,
> >
> >                ?userid?:  99999999?
> >
> > } {
> >
> >                Etc etc
> >
> > }]
> >
> >
> >
> > So in Perl terms it?s an array of hashes. Which is what I want. However,
> if I try and use the openapi way that all the current ?official? Koha
> endpoints use e.g.
> >
> >
> >
> > return $c->render( status => 200, openapi => { notices => $json } );
> >
> >
> >
> > it just doesn?t work. I have tried to map the field names with the
> appropriate types in openapi.json. I?ve tried object type with properties
> e.g.
> >
> >
> >
> > "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "object",
> >
> >                 "properties": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 }, etc
> >
> >
> >
> > , and I?ve tried array type with items:
> >
> >
> >
> > "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "array",
> >
> >                 "items": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 }, etc
> >
> >
> >
> > But I get a page not found error. When I pass my $json variable to the
> render method using openapi how do I get it to work? I?m happy to use the
> text way, but I want to understand where I?m going wrong. Any ideas, hints,
> tips would be most welcome!
> >
> >
> >
> > Cheers, Stephen
> >
> >
> >
> > --------------------------------------
> >
> > Stephen Graham
> >
> > Library Technology Consultant
> >
> > Content and Collections Team
> >
> > Library and Computing Services
> >
> > University of Hertfordshire
> >
> > Tel: 01707 286111
> >
> > Ext: 77751
> >
> > Email: s.graham4 at herts.ac.uk
> >
> >
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : http://www.koha-community.org/
> > git : http://git.koha-community.org/
> > bugs : http://bugs.koha-community.org/
>
>
>
> --
> Tom?s Cohen Arazi
> Theke Solutions (http://theke.io)
> ? +54 9351 3513384
> GPG: B2F3C15F
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190520/7db74021/attachment-0001.html>

From tomascohen at gmail.com  Mon May 20 17:49:41 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 20 May 2019 12:49:41 -0300
Subject: [Koha-devel] Restful API question
In-Reply-To: <CWXP265MB1527BD3F1C488C96C4240057E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
References: <CWXP265MB15272460F92597E10957C75CE7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
	<CABZfb=X4dL3EUjWPCCVhuubbwT58RW5KQNFHaXJdASs1mSEhsQ@mail.gmail.com>
	<CWXP265MB1527F16A95517E5272574E60E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
	<CABZfb=VL7Uu2dw_XV9Jxh5qRHibpzyUVXkSEiK+cDVTqyWrcWw@mail.gmail.com>
	<CWXP265MB1527BD3F1C488C96C4240057E7060@CWXP265MB1527.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CABZfb=U6PJxhMgFCdTZewWwH7VEb29YgNJfVLoebmsFy5XPA5A@mail.gmail.com>

I misread your email while walking :-D

You are right, the render call on the OpenAPI plugin requires you to feed
it with a data structure that can be rendered as a JSON object. So what I'd
loop on the results using fetch_hashref, and then do what is needed on each
field (including mapping 1/0 into Mojo::JSON->true/Mojo::JSON->false if
boolean, making integers really be integers, etc.



El lun., 20 may. 2019 a las 11:40, Stephen Graham (<s.graham4 at herts.ac.uk>)
escribi?:

> Hi Tomas ? the ability to extend the API with custom endpoints using the
> plugin system is a great Koha feature! ?
>
>
>
> If I change my openapi.json to what you suggest I get:
>
>
>
> {"errors":[{"message":"Expected array - got
> string.","path":"\/"}],"status":500}
>
>
>
> , so I guess I need to pass my data to the render method as an array and
> not as a JSON string? If I do this I?m getting a can?t call method on
> unblessed refence error:
>
>
>
> my @n = map { ( $_->encode_json ) } @{$notices};
>
> return $c->render( status => 200, openapi => \@n );
>
>
>
> I guess because @{$notices} is an array of hashes? I see in the Patrons.pm
> REST module, that they are using a method called _*to*_api, which
> according to the Perl doc:
>
>
>
> ?Helper function that maps unblessed Koha::Patron objects into REST api
> attribute names.?
>
>
>
> Sorry, it might be obvious, but do I need to iterate though my results and
> convert them into?. I?m not sure what really. Looking at the _*to*_api
>  method it just seems to be mapping the database column names to the API
> names, which I have done already in my initial sql query, and returns a
> Patron object. Should I be able to do what I want with the data structure I
> get from a fetchall_arrayref({})?
>
>
>
> Cheers, Stephen
>
>
>
>
>
> *From:* Tomas Cohen Arazi <tomascohen at gmail.com>
> *Sent:* 20 May 2019 14:25
> *To:* Stephen Graham <s.graham4 at herts.ac.uk>
> *Cc:* koha-devel <koha-devel at lists.koha-community.org>
> *Subject:* Re: [Koha-devel] Restful API question
>
>
>
> I think it should read like:
>
> "200": {
>     "description": "A list pending notifications",
>     "schema": {
>         "type": "array",
>         "items": {
>             "type": "object",
>             "properties": {
>                 "userid": {
>                         "type": "string",
>                         "description": "Unique User ID"
>                 },
>                 ...
>             }
>         }
>     }
> }
>
> You can of course under-specify it, just saying you return JSON or the way
> you did it, just avoiding OpenAPI altogether, but you loose the ability for
> consumers to have a well documented API, and also you loose data validation
> (in and out), which is very important when implementing the API.
>
>
>
> Happy to see others playing with this! Let me know how can I help1
>
>
>
> El lun., 20 may. 2019 a las 10:05, Stephen Graham (<s.graham4 at herts.ac.uk>)
> escribi?:
> >
> > Hi Tomas ? the below is what I have. When I do my sql select I?m doing:
> >
> >
> >
> > select b.userid as userid,
> >
> > mq.message_id as messageid,
> >
> > mq.subject as subject,
> >
> > mq.content as body
> >
> >
> >
> > ,so the field names should map to the item names in the openapi.json.
> I?m just not sure what I should be passing to the render method, and how to
> describe that in the openapi.json file. At the moment I?m passing a string
> ? it?s JSON ? but just a string. Maybe that isn?t right? When I look to see
> how the Patrons API does it, it works like:
> >
> >
> >
> > my @patrons = $patrons->as_list;
> >
> > @patrons = map { _to_api( $_->TO_JSON ) } @patrons;
> >
> > return $c->render( status => 200, openapi => \@patrons );
> >
> >
> >
> > and then seems to say it?s an array of objects in their json files
> (patron.json and patron.json).
> >
> >
> >
> > Here is my openapi.json file:
> >
> >
> >
> > {
> >
> >   "/notifications": {
> >
> >     "get": {
> >
> >       "x-mojo-to":
> "Uk::Ac::Herts::Notifications::NotificationController#getPendingNotices",
> >
> >       "operationId": "PatronEmailNotice",
> >
> >       "tags": ["notifications"],
> >
> >       "produces": [
> >
> >         "application/json"
> >
> >       ],
> >
> >       "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "array",
> >
> >                 "items": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 },
> >
> >                 "messageid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique Notice ID"
> >
> >                 },
> >
> >                 "subject": {
> >
> >                         "type": "string",
> >
> >                         "description": "Notice Subject"
> >
> >                 },
> >
> >                 "body": {
> >
> >                         "type": "string",
> >
> >                         "description": "Notice Body"
> >
> >                 }
> >
> >                 }
> >
> >                 }
> >
> >         },
> >
> >         "404": {
> >
> >           "description": "An error occured",
> >
> >           "schema": {
> >
> >               "type": "object",
> >
> >                 "properties": {
> >
> >                   "error": {
> >
> >                     "description": "An explanation for the error",
> >
> >                     "type": "string"
> >
> >                   }
> >
> >                 }
> >
> >           }
> >
> >         }
> >
> >       },
> >
> >       "x-koha-authorization": {
> >
> >         "permissions": {
> >
> >           "borrowers": "1"
> >
> >         }
> >
> >       }
> >
> >     }
> >
> >   }
> >
> > }
> >
> >
> >
> > From: Tomas Cohen Arazi <tomascohen at gmail.com>
> > Sent: 20 May 2019 12:28
> > To: Stephen Graham <s.graham4 at herts.ac.uk>
> > Cc: koha-devel <koha-devel at lists.koha-community.org>
> > Subject: Re: [Koha-devel] Restful API question
> >
> >
> >
> > The most probable problem is the OpenAPI spec is wrong, and then the
> plugin API is skipped altogether.
> >
> >
> >
> > If possible, share the openapi.json file in your plugin
> >
> >
> >
> > El lun., 20 de mayo de 2019 08:18, Stephen Graham <s.graham4 at herts.ac.uk>
> escribi?:
> >
> > Hi all ? I know it?s Kohacon this week so a lot of people will be busy
> there, but just in case ??? (also sorry for the length of the email!):
> >
> >
> >
> > I testing creating a custom API endpoint using the Koha plugin system.
> I?ve been using the code in the Kitchen sink plugin as a template, and it
> seems to be working well apart from my lack of Swagger/OpenAPI knowledge ?
> I think it?s this I struggling with. I have three files:
> >
> >
> >
> > koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications.pm
> >
> >
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/NotificationController.pm
> >
> >
> koha-dev/var/lib/plugins/Koha/Plugin/Uk/Ac/Herts/Notifications/openapi.json
> >
> >
> >
> > The work is done in NotificationController.pm where I have a DBI call to
> get the following fields:
> >
> >
> >
> > Borrower.userid
> >
> > Message_queue.message_id
> >
> > Message_queue.subject
> >
> > Message_queue.content
> >
> >
> >
> > I fetch the data, and convert into JSON (encode_json is a method from
> Mojo::JSON) like:
> >
> >
> >
> > my $data = $sth->fetchall_arrayref({}); # return both fieldnames and
> values
> >
> > my $json = encode_json($data);
> >
> >
> >
> > if I then do (i.e. use text):
> >
> >
> >
> > return $c->render( status => 200, text => $json)
> >
> >
> >
> > it works fine. If I call
> https://herttest-staff.koha-ptfs.co.uk/api/v1/contrib/UH/notifications I
> get json like:
> >
> >
> >
> > [ {
> >
> >                ?body?: ?blah blah?,
> >
> >                ?messageid?: ?1234567?,
> >
> >                ?subject?: ?Important??,
> >
> >                ?userid?:  99999999?
> >
> > } {
> >
> >                Etc etc
> >
> > }]
> >
> >
> >
> > So in Perl terms it?s an array of hashes. Which is what I want. However,
> if I try and use the openapi way that all the current ?official? Koha
> endpoints use e.g.
> >
> >
> >
> > return $c->render( status => 200, openapi => { notices => $json } );
> >
> >
> >
> > it just doesn?t work. I have tried to map the field names with the
> appropriate types in openapi.json. I?ve tried object type with properties
> e.g.
> >
> >
> >
> > "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "object",
> >
> >                 "properties": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 }, etc
> >
> >
> >
> > , and I?ve tried array type with items:
> >
> >
> >
> > "responses": {
> >
> >         "200": {
> >
> >           "description": "A list of pending notices",
> >
> >           "schema": {
> >
> >                 "type": "array",
> >
> >                 "items": {
> >
> >                 "userid": {
> >
> >                         "type": "string",
> >
> >                         "description": "Unique User ID"
> >
> >                 }, etc
> >
> >
> >
> > But I get a page not found error. When I pass my $json variable to the
> render method using openapi how do I get it to work? I?m happy to use the
> text way, but I want to understand where I?m going wrong. Any ideas, hints,
> tips would be most welcome!
> >
> >
> >
> > Cheers, Stephen
> >
> >
> >
> > --------------------------------------
> >
> > Stephen Graham
> >
> > Library Technology Consultant
> >
> > Content and Collections Team
> >
> > Library and Computing Services
> >
> > University of Hertfordshire
> >
> > Tel: 01707 286111
> >
> > Ext: 77751
> >
> > Email: s.graham4 at herts.ac.uk
> >
> >
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : http://www.koha-community.org/
> > git : http://git.koha-community.org/
> > bugs : http://bugs.koha-community.org/
>
>
>
> --
> Tom?s Cohen Arazi
> Theke Solutions (http://theke.io)
> ? +54 9351 3513384
> GPG: B2F3C15F
>


-- 
Tom?s Cohen Arazi
Theke Solutions (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/20190520/f88db3a6/attachment-0001.html>

From fridolin.somers at biblibre.com  Wed May 22 14:19:20 2019
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Wed, 22 May 2019 14:19:20 +0200
Subject: [Koha-devel] Koha plugins on GitHub
Message-ID: <fcf303dd-43c5-1ca1-0cc8-4928abe7e838@biblibre.com>

Hi,

It is actually not easy to find all existing plugins for Koha.

Since a lot of them are on GitHub I propose the following guide lines :

1/ we name them koha-plugin-xxxx-yyyy
2/ we add the topic "koha-plugin", see https://github.com/topics/koha-plugin

We also may use GitLab in the future.

Regards,

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
BibLibre, France - software and system maintainer

From katrin.fischer.83 at web.de  Mon May 27 20:22:45 2019
From: katrin.fischer.83 at web.de (Katrin Fischer)
Date: Mon, 27 May 2019 20:22:45 +0200
Subject: [Koha-devel] Koha plugins on GitHub
In-Reply-To: <fcf303dd-43c5-1ca1-0cc8-4928abe7e838@biblibre.com>
References: <fcf303dd-43c5-1ca1-0cc8-4928abe7e838@biblibre.com>
Message-ID: <7fe967f2-dd44-8bdc-5f02-76a111c50724@web.de>

Hi all,

please also remember to add your plugins repositories to the wiki:

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

If Fridolin's proposed guidelines are adopted, maybe we could also add
them there as a help for searching?

Katrin

On 22.05.19 14:19, Fridolin SOMERS wrote:
> Hi,
>
> It is actually not easy to find all existing plugins for Koha.
>
> Since a lot of them are on GitHub I propose the following guide lines :
>
> 1/ we name them koha-plugin-xxxx-yyyy
> 2/ we add the topic "koha-plugin", see
> https://github.com/topics/koha-plugin
>
> We also may use GitLab in the future.
>
> Regards,
>

From tomascohen at gmail.com  Thu May 30 16:41:41 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Thu, 30 May 2019 11:41:41 -0300
Subject: [Koha-devel] Updates on koha-testing-docker
Message-ID: <CABZfb=UAR=dAJVewrYynDsHJf_kjJ3vg_SoGjp+b22T7Y7cHQg@mail.gmail.com>

Hi all, I've made some changes on the koha-testing-docker project to make
it even easier, following requests from community members:

- A file defining cool aliases is included and an be used very easily [1].
Thanks Liz and Nick for their suggestions.
- Now you can start koha-testing-docker without internet connection. You
need to have the docker images up to date and downloaded of course.

[1] https://gitlab.com/koha-community/koha-testing-docker#aliases
[2] docker-compose pull

-- 
Tom?s Cohen Arazi
Theke Solutions (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/20190530/e1249b3c/attachment.html>

From nick at bywatersolutions.com  Thu May 30 17:52:20 2019
From: nick at bywatersolutions.com (Nick Clemens)
Date: Thu, 30 May 2019 11:52:20 -0400
Subject: [Koha-devel] Koha 19.05.00 Released
Message-ID: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>

Hello everybody,

It is with great pleasure that the Koha community announces the release of
Koha 19.05, a major release of the Koha open source integrated library
system.

This release (as always) is the work of many librarians, developers, and
community members who donate their time and effort to the project. Their
contributions help shape the release, and the project going forward. None
of this would be possible without them, and my sincere thanks goes out to
everyone who had a hand in the project

Extra thanks to all who helped me with this release, and with getting here
to be the release manager for this version. I am so lucky to work with such
a great team on a wonderful project and look forward to helping make Koha
better on each release. Excelsior!

Read the full release notes here:
https://koha-community.org/koha-18-11-release/

Debian packages will be available shortly, if you are following a suite you
will
automatically upgrade to the next branch with this release, more info here:
https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6

Thank you all,
Nick (kidclamp)

-- 
Nick Clemens
ByWater Solutions
bywatersolutions.com
Phone: (888) 900-8944
Pronouns: (he/him/his)
Timezone: Eastern
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190530/241f859c/attachment.html>

From tomascohen at gmail.com  Thu May 30 17:56:06 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Thu, 30 May 2019 12:56:06 -0300
Subject: [Koha-devel] Koha 19.05.00 Released
In-Reply-To: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
Message-ID: <CABZfb=XN1K2-FqzRQbaiYjoO6c9LwijtF9hOMgynkJH0LT8eJw@mail.gmail.com>

Great job all! Congrats Nick!

El jue., 30 may. 2019 a las 12:52, Nick Clemens (<nick at bywatersolutions.com>)
escribi?:

> Hello everybody,
>
> It is with great pleasure that the Koha community announces the release of
> Koha 19.05, a major release of the Koha open source integrated library
> system.
>
> This release (as always) is the work of many librarians, developers, and
> community members who donate their time and effort to the project. Their
> contributions help shape the release, and the project going forward. None
> of this would be possible without them, and my sincere thanks goes out to
> everyone who had a hand in the project
>
> Extra thanks to all who helped me with this release, and with getting here
> to be the release manager for this version. I am so lucky to work with such
> a great team on a wonderful project and look forward to helping make Koha
> better on each release. Excelsior!
>
> Read the full release notes here:
> https://koha-community.org/koha-18-11-release/
>
> Debian packages will be available shortly, if you are following a suite
> you will
> automatically upgrade to the next branch with this release, more info here:
>
> https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
>
> Thank you all,
> Nick (kidclamp)
>
> --
> Nick Clemens
> ByWater Solutions
> bywatersolutions.com
> Phone: (888) 900-8944
> Pronouns: (he/him/his)
> Timezone: Eastern
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/



-- 
Tom?s Cohen Arazi
Theke Solutions (http://theke.io)
? +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190530/1aa2eafe/attachment.html>

From joy at bywatersolutions.com  Thu May 30 18:10:15 2019
From: joy at bywatersolutions.com (Joy Nelson)
Date: Thu, 30 May 2019 11:10:15 -0500
Subject: [Koha-devel] [Koha] Koha 19.05.00 Released
In-Reply-To: <CAL=v2SNHvjgM_ee+bSe6f3GSPncC72F9TaFJV-Fg8S=5z7Z7Pw@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
	<CAL=v2SNHvjgM_ee+bSe6f3GSPncC72F9TaFJV-Fg8S=5z7Z7Pw@mail.gmail.com>
Message-ID: <CAFpshE-=RSUCDOS2BxBv+kkS6gJpZnb5jhvMPqa9ybyQ=Dwy6A@mail.gmail.com>

Great work Nick!!

On Thu, May 30, 2019 at 11:00 AM Lucas Gass <lucas at bywatersolutions.com>
wrote:

> Great job Nick!!!
>
> On Thu, May 30, 2019 at 9:53 AM Nick Clemens <nick at bywatersolutions.com>
> wrote:
>
> > Hello everybody,
> >
> > It is with great pleasure that the Koha community announces the release
> of
> > Koha 19.05, a major release of the Koha open source integrated library
> > system.
> >
> > This release (as always) is the work of many librarians, developers, and
> > community members who donate their time and effort to the project. Their
> > contributions help shape the release, and the project going forward. None
> > of this would be possible without them, and my sincere thanks goes out to
> > everyone who had a hand in the project
> >
> > Extra thanks to all who helped me with this release, and with getting
> here
> > to be the release manager for this version. I am so lucky to work with
> such
> > a great team on a wonderful project and look forward to helping make Koha
> > better on each release. Excelsior!
> >
> > Read the full release notes here:
> > https://koha-community.org/koha-18-11-release/
> >
> > Debian packages will be available shortly, if you are following a suite
> you
> > will
> > automatically upgrade to the next branch with this release, more info
> here:
> >
> >
> https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
> >
> > Thank you all,
> > Nick (kidclamp)
> >
> > --
> > Nick Clemens
> > ByWater Solutions
> > bywatersolutions.com
> > Phone: (888) 900-8944
> > Pronouns: (he/him/his)
> > Timezone: Eastern
> > _______________________________________________
> > Koha mailing list  http://koha-community.org
> > Koha at lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>


-- 
Joy Nelson
President, Koha Division

ByWater Solutions <http://bywatersolutions.com>
Support and Consulting for Open Source Software
Phone/Fax (888)900-8944
What is Koha? <http://bywatersolutions.com/what-is-koha/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190530/c18a138d/attachment-0001.html>

From chrisc at catalyst.net.nz  Thu May 30 18:11:31 2019
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Fri, 31 May 2019 04:11:31 +1200
Subject: [Koha-devel] Koha 19.05.00 Released
In-Reply-To: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
Message-ID: <26DAF481-8DFB-4B17-9AB0-D570E6D0DC7E@catalyst.net.nz>

Well done all. 

Just a typo with the release notes,
https://koha-community.org/koha-19-05-release/

Is the correct url

Chris 

On 31 May 2019 3:52:20 AM NZST, Nick Clemens <nick at bywatersolutions.com> wrote:
>Hello everybody,
>
>It is with great pleasure that the Koha community announces the release
>of
>Koha 19.05, a major release of the Koha open source integrated library
>system.
>
>This release (as always) is the work of many librarians, developers,
>and
>community members who donate their time and effort to the project.
>Their
>contributions help shape the release, and the project going forward.
>None
>of this would be possible without them, and my sincere thanks goes out
>to
>everyone who had a hand in the project
>
>Extra thanks to all who helped me with this release, and with getting
>here
>to be the release manager for this version. I am so lucky to work with
>such
>a great team on a wonderful project and look forward to helping make
>Koha
>better on each release. Excelsior!
>
>Read the full release notes here:
>https://koha-community.org/koha-18-11-release/
>
>Debian packages will be available shortly, if you are following a suite
>you
>will
>automatically upgrade to the next branch with this release, more info
>here:
>https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
>
>Thank you all,
>Nick (kidclamp)
>
>-- 
>Nick Clemens
>ByWater Solutions
>bywatersolutions.com
>Phone: (888) 900-8944
>Pronouns: (he/him/his)
>Timezone: Eastern

-- 
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/20190531/6c610758/attachment.html>

From kohanews at gmail.com  Thu May 30 19:31:19 2019
From: kohanews at gmail.com (kohanews)
Date: Thu, 30 May 2019 10:31:19 -0700
Subject: [Koha-devel] Koha Community Newsletter: May 2019
Message-ID: <8af56c34-fcc7-3104-b2a5-25493e9ec001@gmail.com>

The Koha Community Newsletter for May 2019 is here:
https://koha-community.org/koha-community-newsletter-may-2019/

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.

-- 
Chad Roseburg
Editor, Koha Community Newsletter

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

From M.de.Rooy at rijksmuseum.nl  Fri May 31 07:44:31 2019
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Fri, 31 May 2019 05:44:31 +0000
Subject: [Koha-devel] [Koha] Koha 19.05.00 Released
In-Reply-To: <CAFpshE-=RSUCDOS2BxBv+kkS6gJpZnb5jhvMPqa9ybyQ=Dwy6A@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
	<CAL=v2SNHvjgM_ee+bSe6f3GSPncC72F9TaFJV-Fg8S=5z7Z7Pw@mail.gmail.com>,
	<CAFpshE-=RSUCDOS2BxBv+kkS6gJpZnb5jhvMPqa9ybyQ=Dwy6A@mail.gmail.com>
Message-ID: <AM6PR05MB5976CAE3272EDE444C3A26FBCE190@AM6PR05MB5976.eurprd05.prod.outlook.com>

Great, Nick. Congrats.

Please correct the link to the release notes btw.

https://koha-community.org/koha-19-05-release/


Marcel

________________________________
Van: koha-devel-bounces at lists.koha-community.org <koha-devel-bounces at lists.koha-community.org> namens Joy Nelson <joy at bywatersolutions.com>
Verzonden: donderdag 30 mei 2019 18:10
Aan: Lucas Gass
CC: Koha; Koha Devel
Onderwerp: Re: [Koha-devel] [Koha] Koha 19.05.00 Released

Great work Nick!!

On Thu, May 30, 2019 at 11:00 AM Lucas Gass <lucas at bywatersolutions.com<mailto:lucas at bywatersolutions.com>> wrote:
Great job Nick!!!

On Thu, May 30, 2019 at 9:53 AM Nick Clemens <nick at bywatersolutions.com<mailto:nick at bywatersolutions.com>>
wrote:

> Hello everybody,
>
> It is with great pleasure that the Koha community announces the release of
> Koha 19.05, a major release of the Koha open source integrated library
> system.
>
> This release (as always) is the work of many librarians, developers, and
> community members who donate their time and effort to the project. Their
> contributions help shape the release, and the project going forward. None
> of this would be possible without them, and my sincere thanks goes out to
> everyone who had a hand in the project
>
> Extra thanks to all who helped me with this release, and with getting here
> to be the release manager for this version. I am so lucky to work with such
> a great team on a wonderful project and look forward to helping make Koha
> better on each release. Excelsior!
>
> Read the full release notes here:
> https://koha-community.org/koha-18-11-release/
>
> Debian packages will be available shortly, if you are following a suite you
> will
> automatically upgrade to the next branch with this release, more info here:
>
> https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
>
> Thank you all,
> Nick (kidclamp)
>
> --
> Nick Clemens
> ByWater Solutions
> bywatersolutions.com<http://bywatersolutions.com>
> Phone: (888) 900-8944
> Pronouns: (he/him/his)
> Timezone: Eastern
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz<mailto:Koha at lists.katipo.co.nz>
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
_______________________________________________
Koha mailing list  http://koha-community.org
Koha at lists.katipo.co.nz<mailto:Koha at lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha


--
Joy Nelson
President, Koha Division

ByWater Solutions<http://bywatersolutions.com>
Support and Consulting for Open Source Software
Phone/Fax (888)900-8944
What is Koha? <http://bywatersolutions.com/what-is-koha/>

[https://docs.google.com/uc?export=download&id=1jnnA_xzxbRZWnIBkuEE-9Xvqe2eJUkLo&revid=0B5Y57KiwL9IEYm90eVZLVE9oTTN4aWJzRVUrZVJhK3lLaXlvPQ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190531/f8447502/attachment-0001.html>

From kohadevinim at devinim.com.tr  Fri May 31 08:06:17 2019
From: kohadevinim at devinim.com.tr (DevinimKoha)
Date: Fri, 31 May 2019 09:06:17 +0300
Subject: [Koha-devel] Koha 19.05.00 Released
In-Reply-To: <26DAF481-8DFB-4B17-9AB0-D570E6D0DC7E@catalyst.net.nz>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
	<26DAF481-8DFB-4B17-9AB0-D570E6D0DC7E@catalyst.net.nz>
Message-ID: <5e2d98c3-8dff-d266-33b3-a73c441a8349@devinim.com.tr>

Congrats Nick.

Thanks to everyone.

On 30.05.2019 19:11, Chris Cormack wrote:
> Well done all.
>
> Just a typo with the release notes,
> https://koha-community.org/koha-19-05-release/
>
> Is the correct url
>
> Chris
>
> On 31 May 2019 3:52:20 AM NZST, Nick Clemens 
> <nick at bywatersolutions.com> wrote:
>
>     Hello everybody,
>
>     It is with great pleasure that the Koha community announces the
>     release of
>     Koha 19.05, a major release of the Koha open source integrated library
>     system.
>
>     This release (as always) is the work of many librarians,
>     developers, and
>     community members who donate their time and effort to the project.
>     Their
>     contributions help shape the release, and the project going
>     forward. None
>     of this would be possible without them, and my sincere thanks goes
>     out to
>     everyone who had a hand in the project
>
>     Extra thanks to all who helped me with this release, and with
>     getting here to be the release manager for this version. I am so
>     lucky to work with such a great team on a wonderful project and
>     look forward to helping make Koha better on each release. Excelsior!
>
>     Read the full release notes here:
>     https://koha-community.org/koha-18-11-release/
>
>     Debian packages will be available shortly, if you are following a
>     suite you will
>     automatically upgrade to the next branch with this release, more
>     info here:
>     https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
>
>     Thank you all,
>     Nick (kidclamp)
>
>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> _______________________________________________
> 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/20190531/2f9998f3/attachment.html>

From martin.renvoize at ptfs-europe.com  Fri May 31 08:31:19 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Fri, 31 May 2019 07:31:19 +0100
Subject: [Koha-devel] Koha 19.05.00 Released
In-Reply-To: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
Message-ID: <CAB7SL8DCtKUSQ_-KUvWYuNN7ktARzNNh+V764S4CNyq5kVfV3Q@mail.gmail.com>

Thanks Nick,

It's looking like a great release and I'm looking forward to taking on the
batton from you for the next.

It's been a great experience working as a release maintainer under your
reign and I feel I've got a big pair of boots to fill stepping into the
role of the release manager.

Thanks for all the hard work and I'm looking forward to continued work
alongside you.

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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 Thu, 30 May 2019 at 16:52, Nick Clemens <nick at bywatersolutions.com>
wrote:

> Hello everybody,
>
> It is with great pleasure that the Koha community announces the release of
> Koha 19.05, a major release of the Koha open source integrated library
> system.
>
> This release (as always) is the work of many librarians, developers, and
> community members who donate their time and effort to the project. Their
> contributions help shape the release, and the project going forward. None
> of this would be possible without them, and my sincere thanks goes out to
> everyone who had a hand in the project
>
> Extra thanks to all who helped me with this release, and with getting here
> to be the release manager for this version. I am so lucky to work with such
> a great team on a wonderful project and look forward to helping make Koha
> better on each release. Excelsior!
>
> Read the full release notes here:
> https://koha-community.org/koha-18-11-release/
>
> Debian packages will be available shortly, if you are following a suite
> you will
> automatically upgrade to the next branch with this release, more info here:
>
> https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6
>
> Thank you all,
> Nick (kidclamp)
>
> --
> Nick Clemens
> ByWater Solutions
> bywatersolutions.com
> Phone: (888) 900-8944
> Pronouns: (he/him/his)
> Timezone: Eastern
>
> _______________________________________________
> 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/20190531/78c5f29b/attachment.html>

From martin.renvoize at ptfs-europe.com  Fri May 31 09:19:53 2019
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Fri, 31 May 2019 08:19:53 +0100
Subject: [Koha-devel] Koha 18.11.06 release
Message-ID: <CAB7SL8AO70kjyMqpGhwVHH7k7hC9aPMRxj3auYT32D+gsFcSjg@mail.gmail.com>

The Koha community is proud to announce the release of Koha 18.11.06.

This is a maintenance release and is my last release as the 18.11.x series
maintainer. The series is however in good hands going forward with Fridolin
Somers taking it on for the next cycle. I'm sure he'll do a great job!

Many thanks to all those who have supported the releases this cycle.

The full release notes are available at
https://koha-community.org/koha-18-11-06-release/

Debian packages will be uploaded in a few days.

Best regards and thanks to all those who have contributed to this release.

*Martin Renvoize*

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

Development Team Manager





*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

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

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


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190531/35b881f7/attachment-0001.html>

From M.de.Rooy at rijksmuseum.nl  Fri May 31 09:50:53 2019
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Fri, 31 May 2019 07:50:53 +0000
Subject: [Koha-devel] Koha 18.11.06 release
In-Reply-To: <CAB7SL8AO70kjyMqpGhwVHH7k7hC9aPMRxj3auYT32D+gsFcSjg@mail.gmail.com>
References: <CAB7SL8AO70kjyMqpGhwVHH7k7hC9aPMRxj3auYT32D+gsFcSjg@mail.gmail.com>
Message-ID: <AM6PR05MB5976DF8C023DEDAF58F37A9FCE190@AM6PR05MB5976.eurprd05.prod.outlook.com>

Thx Martin !


________________________________
Van: koha-devel-bounces at lists.koha-community.org <koha-devel-bounces at lists.koha-community.org> namens Renvoize, Martin <martin.renvoize at ptfs-europe.com>
Verzonden: vrijdag 31 mei 2019 09:19
Aan: Koha; Koha Devel
Onderwerp: [Koha-devel] Koha 18.11.06 release

The Koha community is proud to announce the release of Koha 18.11.06.

This is a maintenance release and is my last release as the 18.11.x series maintainer. The series is however in good hands going forward with Fridolin Somers taking it on for the next cycle. I'm sure he'll do a great job!

Many thanks to all those who have supported the releases this cycle.

The full release notes are available at
https://koha-community.org/koha-18-11-06-release/

Debian packages will be uploaded in a few days.

Best regards and thanks to all those who have contributed to this release.


Martin Renvoize

[https://www.ptfs-europe.com/wp-content/uploads/2018/10/ptfs-logo-full-email-sig.png]<https://www.ptfs-europe.com>

Development Team Manager





Phone: +44 (0) 1483 378728

Mobile: +44 (0) 7725 985 636

Email: martin.renvoize at ptfs-europe.com<mailto:martin.renvoize at ptfs-europe.com>

Fax: +44 (0) 800 756 6384


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<mailto:info at ptfs-europe.com>

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

From J.P.Knight at lboro.ac.uk  Fri May 31 12:24:37 2019
From: J.P.Knight at lboro.ac.uk (Jon Knight)
Date: Fri, 31 May 2019 10:24:37 +0000
Subject: [Koha-devel] Koha 19.05.00 Released
In-Reply-To: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
References: <CAA_eX3Om_HmKzkkHR3Yuip4oL=iVFWNfT5YN_wirnGyMO8D8Aw@mail.gmail.com>
Message-ID: <AM6PR0402MB33500F8D1F74BFD97B040EE197190@AM6PR0402MB3350.eurprd04.prod.outlook.com>

Probably worth noting that the 19.05 release notes are actually at: https://koha-community.org/koha-19-05-release/

Well done folks!

Jon
________________________________________
From: koha-devel-bounces at lists.koha-community.org <koha-devel-bounces at lists.koha-community.org> on behalf of Nick Clemens <nick at bywatersolutions.com>
Sent: 30 May 2019 16:52
To: Koha Devel; Koha
Subject: [Koha-devel] Koha 19.05.00 Released

Hello everybody,

It is with great pleasure that the Koha community announces the release of
Koha 19.05, a major release of the Koha open source integrated library
system.

This release (as always) is the work of many librarians, developers, and
community members who donate their time and effort to the project. Their
contributions help shape the release, and the project going forward. None
of this would be possible without them, and my sincere thanks goes out to
everyone who had a hand in the project

Extra thanks to all who helped me with this release, and with getting here to be the release manager for this version. I am so lucky to work with such a great team on a wonderful project and look forward to helping make Koha better on each release. Excelsior!

Read the full release notes here:
https://koha-community.org/koha-18-11-release/

Debian packages will be available shortly, if you are following a suite you will
automatically upgrade to the next branch with this release, more info here:
https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.2C_oldstable_.E2.80.A6

Thank you all,
Nick (kidclamp)

--
Nick Clemens
ByWater Solutions
bywatersolutions.com<http://bywatersolutions.com>
Phone: (888) 900-8944
Pronouns: (he/him/his)
Timezone: Eastern

[https://drive.google.com/a/bywatersolutions.com/uc?id=1KGn9r4PMKzZE1gjiHTfb0wQ5cNFMIX5g&export=download]

From tomascohen at gmail.com  Fri May 31 18:13:53 2019
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Fri, 31 May 2019 13:13:53 -0300
Subject: [Koha-devel] [Koha] Koha 18.05.13 release
In-Reply-To: <CAL=v2SM6iqSc7Jx-2E=B=LwBWZHta8qFxkLPd=PbA=e-XSiBcA@mail.gmail.com>
References: <CAL=v2SM6iqSc7Jx-2E=B=LwBWZHta8qFxkLPd=PbA=e-XSiBcA@mail.gmail.com>
Message-ID: <CABZfb=Uni+JF46z72bkvYQbtYZ0j2-aC=JMBnraZL=Yu9aXPYw@mail.gmail.com>

Congrats for the great work!

El vie., 31 may. 2019 a las 12:13, Lucas Gass (<lucas at bywatersolutions.com>)
escribi?:

> The Koha community is proud to announce the release of Koha 18.05.13.
>
> Many thanks to all those who have supported the releases this cycle.
>
> The full release notes are available at:
> https://koha-community.org/koha-18-05-13-release/
>
> Debian packages will be uploaded in a few days.
>
>
> Lucas
> _______________________________________________
> 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 (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/20190531/74bef50c/attachment.html>