Thanks, Amy.  I've already posted my comment in response to the article,
which overall, I thought was quite good.

Lori

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=
Lori Bowen Ayre //
Library Technology Consultant / The Galecia Group
Oversight Board & Communications Committee / Evergreen
(707) 763-6869 // lori.a...@galecia.com

<lori.a...@galecia.com>Specializing in open source ILS solutions, RFID,
filtering,
workflow optimization, and materials handling
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



On Thu, Aug 25, 2011 at 2:08 PM, DeGroff, Amy <adegr...@liblime.com> wrote:

> Hi everyone:
>
> As a former IT director for a library system that was planning to
> implement Koha, but subsequently chose an alternate path, I would
> recommend you approach this topic with delicacy,   What is said
> publicly and what truly happened is not always the same story. I would
> not publicly discuss all aspects of what occurred with me and my
> former site, and the same is true for any library in this situation.
>  It may be that discussing issues from two years ago  is not
> productive for anyone - especially the hard working librarians in New
> Jersey about whom you'd be speaking.
>
> East Brunswick was an early PTFS customer and contributed ideas and
> energy to Koha - ideas which we proudly made available to all -- via
> our public git hub.  Some features have been adopted by other Koha
> users -- some features have not.
>
> East Brunswick did indeed find Koha 3.x slow in areas related to
> circulation - we worked to address their concerns. They were a Horizon
> site and the speed of that thick client application was for them  too
> tantalizing and familiar to give up; a web application - like Koha -
> is in some cases - slower than a thick client - like Horizon.
>
> Despite the departure of a valued customer, we have continued to make
> significant improvements in response time, both with sponsored
> development from customers and sponsored development by PTFS.
>
> We will soon be publishing a new release of LibLime Koha in download
> format as well as a unified git repository.  This release includes the
> latest performance improvements we have made to the application
> including the use of the Plack environment which simulates a
> persistent run time environment for PERL.  In that release,
> circulation transactions are now  1/3 of a second.
>
> Lori - what else can I supply to help you set the record straight?
>
>
>
> --
>
> 2011/8/24 Robin Sheat <ro...@catalyst.net.nz>
> >
> > Lori Bowen Ayre schreef op wo 24-08-2011 om 16:17 [-0700]:
> > > As I read this, I recalled someone saying that the only library to
> > > have gone to Koha and then switched back was a Liblime customer
> >
> > I'm aware of one here in NZ (that I don't think was liblime), but they
> > were happily running Koha, and then joined/got absorbed into a
> > consortium that mandated something else, so it wasn't a switch due to
> > unhappiness with Koha.
> >
> > --
> > Robin Sheat
> > Catalyst IT Ltd.
> > ✆ +64 4 803 2204
> > GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
> >
> > _______________________________________________
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > http://lists.katipo.co.nz/mailman/listinfo/koha
> >
>
>
>
> --
> Amy Begg De Groff
> Product Manager
> LibLime, a Division of PTFS, Inc.
> adegr...@liblime.com
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Reply via email to