I-team Meeting Notes 6-1-2006

All, here is a summary of all the decisions that we made at the I-Team meeting last week. We will be going over these at the Director’s Meeting on the 15^th. I’m also including the agenda for that meeting with this email.

There are still some hiccups with the holds system. To address these, the following decisions were made:

We will be turning off the hold list queue in i-Bistro because the queue is so dynamic it is confusing to the patrons. We would like to see if the patrons’ outcry over not seeing their place in the holds queue is greater than the out cry over why the patrons are moving down the holds queue. If it is we will turn it back on. I will let everyone know when the switch is made.

All holds for New Castle County libraries will be sent to the Division of Libraries for processing. In addition all NCC library accounts will be deleted and each library will be issued a new barcode and PIN with the default library set as the DDL. This will have to take place in stages as these accounts have items and holds against them. Once made all libraries who have a hold for a NCC library will pull it and trap it but not check it out for the library. Instead they will send it to DDL as instructed on the pull holds list.

Libraries may load bib records for items that are on order prior to receiving them so that patrons can place holds on the items. The libraries must make sure to attach their items to these records so that these holds can be filled.

All finished reports left on the server longer than two weeks will be deleted. We need to keep the finished reports list cleaner than it is. So any report older than two weeks will be deleted by the system admins (Ben, Jane or Vinny). So if you want to keep a record of your reports save them to your local PC or print them.

A little review of patron information
Del Tech students have two accounts, their public account and their student account. Only Del Tech libraries can edit the student account. The student account expires at the end of every semester, which is why they will be using their public library cards when in the public library.

Phone numbers are entered by number only, no dashes or parenthesis.

We will be turning on a duplicate record check for the whole system beginning tomorrow. This means that when a patron is registered if that patron already has an account that matches a pop up screen will alert the staff. The matching points will be License, Name, Home Phone and Street. Unfortunately we cannot chose birthdates as a matching point or we would. So for all patrons in question the Birthdate will be the ultimate check point and should be the first thing the staff look for when a duplicate is found by the system.

All libraries should merge duplicate Kent and Sussex Patron records when made known to them. Current address will dictate which account to keep. In cases where there are bills against the account to be merged those accounts will have to be left unmerged until the bills are paid or waived by the library.

The issues with receipt printers will continue until the receipt printers are replaced with newer models. That is the response from Sirsi in regards to our issue with some wizards not printing. That also seems to be the case for the libraries that are not experiencing problems with their receipt printers. All libraries are encouraged to be looking into new receipt printers.

We will be upgrading to a new version of Workflows on the server next week. Some libraries have already been moved over to the new client. The big fix for this client is the issue with holds becoming available the moment they are trapped. You will know you are running the new client because your Workflows icon will read Workflows GL3.0J instead of Workflows GL3.0. During this process staff may see a pop up when loading workflows asking them if they want to update the client. The answer for this is always NO. Make a note of that by every machine. At no time does a staff member update the client. If the staff member ignores that and chooses yes you may not be able to connect to the server. So just say no to client updates unless instructed specifically by, me, Ben, Paul, Gene or Denise.