CCS News
FEBRUARY 6, 2009
FROM THE COMPUTER ROOM:
Disappearing cursor – a few of you have mention the case of the disappearing cursor which is a problem with the Java client and shows up when checking initems or checking the status of an item. The problem has been fixed in Symphony 3.3 and evidently it required some significant reworking of the SirsiDynix code. We have learned that in the mean time when this happens, if you unplug and plug in your barcode scanner the cursor will return. Also, you may be able to click around in the menu bar (for example, Preferences > Peripherals > Barcode Reader then cancel) to get the cursor to become active again.
Test 3.2.1 – We are in the process of loading the new release on the test server and will keep you posted on our progress. When you are testing, please let us know if you need any new features turned on.
AUTHORITIES UPDATE:
CCS sent 4194 bibliographic records to Marcive on Thursday, Jan. 29th for Overnight Authorities Processing. The records have been processed and were reloaded into our system. Of the 4194 bibliographic records, Marcive returned 1593 updated bibliographic records. Marcive also sent us 2050 new authority records. Marcive’s speedy service insures that the CCS database is kept up to date as much as possible with current headings and references. -- Virginia R. Seward
CCS Authorities Librarian
DID YOU KNOW?
Did you know that we’ll be ready to start testing the Symphony 3.2.1 release (AKA WorkFlows) early next week, but there are still several CCS libraries that do not have anyone from their staff participating in the project? It’s important to have as many people as possible try out the new release, of course, but it’s also critical that we have at least one person from each library getting hands-on experience with 3.2.1 before we start using it for normal operations. When testing indicates it’s stable and ready for primetime, Symphony will be moved into production and all of us will be using it every day. If no one on your library’s staff has even seen the new release by the time we go to production, there won't be anyone on hand who’s familiar with it and able to answer basic questions that may arise. This isn’t fair to the other CCS libraries, because the inexperienced libraries could monopolize the support staff with questions when we go into production.
The best way to gain knowledge of Symphony is to participate in the testing project. If you don’t have anyone at your library helping test the new release, please designate a knowledgeable person to spend time at least becoming familiar with Symphony. It would be best if someone from each department could spend as much time as possible with the new release, but every library should have a minimum of one skilled WorkFlows person learning about and/or testing the changes coming with Symphony 3.2.1. –- Ken Victorson
CCS MEETINGS NEXT WEEK:
Wed., 2/11, 10:00, CCS: Executive Committee
Thur., 2/12, 9:30, NSLS: ILL
