I was just reading the article on LJ called Open Source Reality Check ( http://www.libraryjournal.com/lj/home/891350-264/open_source_reality_check.h...) which opens with "In 2009, East Brunswick <http://www.ebpl.org/> Public Library<http://www.ebpl.org/> (EBPL), NJ, switched from a proprietary integrated library system (ILS), SirsiDynix’s Horizon, to an open source Koha ILS. In 2010, it switched back." 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. Can anyone verify that it East Brunswick was indeed a Liblime customer and if so, when did that relationship begin and end? I'd like to set the record straight by commenting on the article but I want MY facts straight first! Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group Oversight Board & Communications Committee / Evergreen (707) 763-6869 // Lori.Ayre@galecia.com <Lori.Ayre@galecia.com>Specializing in open source ILS solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hi Lori They were a PTFS customer, before Liblime was sold to PTFS. http://www.librarytechnology.org/lwc-displaylibrary.pl?RC=1467 Chris 2011/8/25 Lori Bowen Ayre <lori.ayre@galecia.com>:
I was just reading the article on LJ called Open Source Reality Check (http://www.libraryjournal.com/lj/home/891350-264/open_source_reality_check.h...) which opens with "In 2009, East Brunswick Public Library (EBPL), NJ, switched from a proprietary integrated library system (ILS), SirsiDynix’s Horizon, to an open source Koha ILS. In 2010, it switched back." 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. Can anyone verify that it East Brunswick was indeed a Liblime customer and if so, when did that relationship begin and end? I'd like to set the record straight by commenting on the article but I want MY facts straight first!
Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group Oversight Board & Communications Committee / Evergreen (707) 763-6869 // Lori.Ayre@galecia.com Specializing in open source ILS solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
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
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 <robin@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. adegroff@liblime.com
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.Ayre@galecia.com <Lori.Ayre@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 <adegroff@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 <robin@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. adegroff@liblime.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I find it interesting that the only thing that will prompt Liblime's participation on this list is possible bad press.
We will soon be publishing a new release of LibLime Koha in download format as well as a unified git repository.
This is meaningless information for this list. We discuss Koha here. If you want to be lauded for your accomplishments, those accomplishments will have to be in the form of real collaboration. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Koha is Koha, LibLime Kohaproduct is a proprietary derivative. Nothing wrong with that - but lets not confuse the 2. On 26 August 2011 09:08, DeGroff, Amy <adegroff@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 <robin@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. adegroff@liblime.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust.
On 2011-08-26, at 9:08 AM, DeGroff, Amy wrote:
Hi everyone:
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.
wow, thats an impressive circ speed so, is there a PTFS/Liblime code repo for this Plack stuff, anyone? i'd be very keen to help get this submitted and accepted into Koha, if i could just find that repo....
As Amy's message says, the code will be available soon. It's in production now on several sites (including two large consortia) and in test on several more. As soon as we're sure it's ready, and the sponsoring organizations give approval, we'll put it on our public repo. On Fri, Aug 26, 2011 at 12:49 AM, Mason James <mtj@kohaaloha.com> wrote:
On 2011-08-26, at 9:08 AM, DeGroff, Amy wrote:
Hi everyone:
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.
wow, thats an impressive circ speed
so, is there a PTFS/Liblime code repo for this Plack stuff, anyone? i'd be very keen to help get this submitted and accepted into Koha, if i could just find that repo....
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@liblime.com
participants (8)
-
Chris Cormack -
DeGroff, Amy -
Joann Ransom -
Lori Bowen Ayre -
Mason James -
Owen Leonard -
Robin Sheat -
Wagner, Jane