CCS News
OCTOBER 24, 2008
FROM THE COMPUTER ROOM:
Spell Checker – the Lucien Spell Checker has been running for a few days now with iBistro and so far so good. We have had GREAT feedback about this new feature. We are currently in a three month trial period and then plan to obtain a permanent license.
iBistro – over the weekend and at the request of PAS we will be making a little change to indicate when a patron is blocked. iBistro will now inform the patron: There is an issue with your account. Please contact the library...
Pictures – we will be working on a new CCS web site soon. Do you want to update your library’s picture? If so please send a .jpeg to Frank in the computer room.
Security testing on test iBistro – we have been doing some testing of HTTPS for securing iBistro session using the test server. So if you see reference to secure sessions on this server suddenly, it is likely that it is due to our testing. This is related to the ePay integration project that we plan to do with SirsiDynix.
DID YOU KNOW?
Did you know that we'll soon be installing Symphony 3.2.1 (the latest WorkFlows upgrade) on the CCS test server and I’m looking for volunteers to help test changes in the new release? In conjunction with the installation I’ll be distributing test scripts to each CCS Technical Group and would like every library to identify at least one experienced member of each department to review the changes. The five areas to be examined are: Acquisitions, Cataloging (including Authorities and Serials), Circulation, ILL, and PAS. There will be a separate test script for each of the five components and I’m hoping all libraries will find a tester for each area. This is a major new release and the modules have many fixes and enhancements in them. Some departments may elect to divide a test script into smaller sub-segments and ask more than one person to work on a portion of the script. NOTE: Symphony 3.2.1 testing will be conducted with the Java client. If your library is still using the C client for any operations, you'll have to test them in-house to verify that they still work with this release.
The primary purpose of our testing is to verify that fixes and enhancements to the 3.2.1 release are working as they should. But I hope testers will also take time to look at their normal daily tasks during testing to ensure that frequently used functions/wizards are all working properly. Time spent testing now will benefit the entire consortium in the long run. We want to avoid unpleasant surprises when we install this release on the production server and the best way to do that is to have as many people as possible test it thoroughly beforehand. You’ll be hearing more about Symphony 3.2.1 testing as the date for the new installation draws closer, but feel free to contact me at any time if you have questions or concerns about the project. Please send me the names and email addresses of the staff members who’ll be helping with the testing as soon as you identify them, so I can begin to coordinate with them directly. – Ken Victorson
CCS MEETINGS NEXT WEEK:
None! (How did that happen in October??)
