To empower libraries and library consortia by encouraging participation and collaboration in open source software products generally, and encouraging them to consider an Open Source Library System such as Koha or Evergreen.

Moving Slowly

As mentioned earlier, our Koha Task Force is meeting weekly on Thursday afternoons from 1:30 to 2:30. It has taken us three meetings to get through a review of all our current (SirsiDynix Symphony) policies. Each Task Force member was given a stack of policies to review before the meetings.

I personally thought that we could go through all of these policies in an hour... no, this wasn't the case. As we worked through each list there was always a question on why did we have this?, is anyone still using that? And, can we delete it? It was surprising to me that I couldn't answer all the questions asked since I was there from the beginning of our SirsiDynix experience. I guess as time goes by staff uses what they need and nothing more.

As we reviewed the policies, we thought... "I wonder if Koha will do this?" (an example: we wanted to have the ILS automatically charge a fee to a patron's record when a hold was available for check out. We never could get this to work the way "we" wanted with SirsiDynix) so we have started making a list of questions to ask Brendan during our next conference call.

Once we went through each policy list, either Cathi or myself ran reports to see if we had items or patrons in the policy name that we decided to delete. These reports were made available to the members. Items and Users were moved or deleted. Staff is also searching for material that has been marked "Missing" in the database. There's no use moving over material that we no longer have on our shelves. Hopefully we will soon have a sleek database ready to migrate to Koha.
Jackie

SirsiDynix and the Ongoing FUD Factor

Two online tidbits led me to check in with the folks at SirsiDynix about what they are telling their customers about the viability of moving to an open source ILS.  Officially, SirsiDynix states that "we believe that competition is good. It challenges all vendors who are invested in the success of libraries to continuously improve our products and services, and fuels innovation that make libraries better for users around the world. Open source solutions, either independently or commercially developed and maintained, can be the right solution for a library for a number of reasons."

But privately, they are telling people that some unspecified number of SirsiDynix customers "who have left SirsiDynix solutions for an open source solution [ ] have since returned to SirsiDynix."  

So the burning question is this...what is that unspecified number?  According to Arcadia Library, their SirsiDynix Field Sales Consultant stated this number was 30% as in "30% of the libraries that left SirsiDynix for open source software ended up with SirsiDynix again." (Source: http://koha4arcadialibrary.blogspot.com/)

In other parts of the world (Washington), Kitsap Sun reporter Chris Henry interviewed SirsiDynix Global Marketing and Communications Manager, Julianne Hancock, who stated that "most of their customers who migrated to open-source software have since returned because they found managing the systems a drain on scarce resources." (Source: http://www.kitsapsun.com/news/2010/aug/30/kitsap-regional-library-catalog-system-ailing/)

I decided to pursue the matter further.  A PDF of my communications with Julianne are attached.

Besides, the one library that Julianne mentions in our email exchange (McMaster University)....do you know of a SirsiDynix customer that tried Koha or Evergreen and then decided to go back to SirsiDynix????  If most, or even just 30% switched back, there should be a whole bunch of you out there!  I mean they have 4,000 clients!  (Source: http://www.sirsidynix.com/company).

 

Where to Learn About PTFS' Harley

Northeast Kansas Library System (NEKLS) was one of those libraries that thought they were buying an open source product, Koha, but have ended up with a not-quite-open-source product, Harley.  If you want to learn more about their experience, you might want to follow their blog.  They are very diligent about reporting on their experiences.

This post, Known Issues Harley 1.1 Upgrade, is particularly revealing...

Koha Evergreen Cross Fertilization Begins....

Dan Scott, an Evergreen developer Systems Librarian at Laurentian University recently blogged about using code  developed in Koha for a routine he developed in Evergreen which will enable LC call numbers to sort correctly (Dewey works okay today but LC numbers don't).

Questions about Koha from TLC Libraries Thinking of "Unionizing"

I had a meeting today with a group of three TLC libraries who are thinking about joining forces and forming a Koha consortium.  As part of their due diligence, they proffered up some questions which Brendan Gallagher of ByWater Solutions answered. My rendition of the Qs&As follows.

But first, the million dollar question....."Since we are all independent libraries with our own policies, which policies will we need to agree upon?"

 ANSWER:  To create a union catalog for all of the libraries, you will have to agree on the Global Policy settings.  These are described here: http://koha-community.org/documentation/3-2-manual/index.php?ch=c19#AEN1602

And here's the rest of the Questions and Answers:

1.  Is there a way to easily change the circulating location of a batch of items, like "item transfers" function in TLC's circ?  When we send items to a branch, we change the circ-ing location so the books will stay there.  We don't want to have to go into cataloging to do this.

 ANSWER:  Yes.

2.  Will our hold report show only on library's holds, or all holds in the consortium? (we probably need to have a discussion about how Koha will function and look as a consortium)

 ANSWER: You can do it either way 

3.  Can we limit branch staff to log into their branch only? 

 ANSWER:  Yes.

4.  We've looked at fast add -- is there a way to do on-the-fly records that aren't MARC?

 ANSWER:  Not really. 

5.  Has any library migrated from TLC to Koha?

 ANSWER:  Yes.

6.  Will we be able to access the LOC authority file through Z39.50?

 ANSWER: You can create a local file of LOC authorities and this can be updated but it isn't done via Z39.50.

7.  What's Bywater's redundancy/backup?

 ANSWER:  There are backups including backups of your Linux server, the Koha code and your database.  Depending on which thing you're talking about.  An image of your server is saved offsite, the code is backed up regularly and stored on tape, and your database is backed up every and stored in a couple different places for safe-keeping and quick recovery.

8.  Is it possible to put a recall on an item so a specific message comes up when a book is checked in?

 ANSWER:  If you mean a "recall" as in asking a patron to return a book that they have checked-out...no.  But if you are talking about having a note pop up that circ staff can see when an item is returned (e.g. send to mending), yes.

9.  How do you alter the status of an item (make it missing, damaged, lost) in circ?

 ANSWER: Search for the title, select it, go to the detail page, select the new status from the dropdown list.

10.  Is there any way to clear current patron from screen after you've finished with them (right now you can go to check-in, and last patron still shows on screen).

 ANSWER:  Yes, there is a "clear" button that staff can click.

11.  We need to see what the overdues report looks like.  Many of our patrons don't have e-mail; we need to know what's involved in printing overdue notices.

 ANSWER:  Notices are highly configurable for each library and they go out via email when a valid email is available for the patron.  If not, they can be formatted and batch printed using Word merge or something similar.

12.  There are a number of cataloging functions that are more cumbersome, requiring more steps, in Koha.  Withdrawing books and adding items to a title record are two.

 ANSWER:  You can batch add several items to a single bib record.  You can batch add multiple bib records.  You can batch delete several item records (and if the item is the last one connected to a bib record, the bib record is also automatically deleted).  You cannot create one file with all of these options (add this record, delete that)...each function has to be performed as its own batch function.

13.  It seems too easy to check a book in while in the patron's record when you meant to renew it. 

 ANSWER:  Agreed. For that reason, ByWater recommends removing the check-in button from the patron screen (in the staff interface).

14.  There are a lot of TLC reports that we currently run to pull the information needed for the State Library report.  It would be really nice if there's money in the grant, or some method of collaboration, so we could come up with a list of the Koha reports we would need to run to get that same info.

 ANSWER:  ByWater will be working on this  with other California libraries migrating to Koha so everyone will have what they need for the State Library.

15.  Will we be able to upload (import) to OCLC via Z39.50?  TLC does this automatically when a new record is created.

 ANSWER:  In Koha, you will need to export any records you want to upload to OCLC and then upload that file to OCLC.