CCS News
MARCH 20, 2009
FROM THE COMPUTER ROOM:
Upgrade of 3.2.1 on test server – the upgrade on the test Workflows server is complete. The upgrade of Test iBistro is complete with the caveat that some custom pages have not been moved in yet so that testing of ePay/Sirsi integration can continue.
Purge Inactive holds – we have begun the process and will continue to purge several hundred thousand inactive holds each night (about 7 million total) until the file contains only the last six months of inactive holds.
New Web Site – in the past week we have mentioned to the Technical Groups that our new web site is available for previewing. You can find it at www.ccslib.org. Tell us what you think!
STILL MORE SUBJECT HEADING CHANGES OF NOTE:
As promised, now all headings that were under “Electric engineering” and “Electric engineers” have been changed to “Electrical engineering” and “Electrical engineers”. These changes occurred last night in our database, along with some others.
The other subject heading changes include “Catalogs, College”, “Catalogs, Union”, and etc. so that they are now found in direct order. They can now be found in our database under “College catalogs” and “Union catalogs” for example.
And for those interested, all 700+ genre headings of “Adventure television programs” have been changed to “Action and adventure television programs” (or the same heading as the regular subject heading).
--Virginia
Virginia R. Seward
CCS Authorities Librarian
DID YOU KNOW?
Did you know that testing for Symphony 3.2.1 is currently underway but it’s being conducted differently than other new release tests we’ve done in the past? With 3.2.1 we are instructing libraries to NOT use their own personal workstations for testing. Instead, we recommend that the testing be done on a laptop, a little used “back room” machine, or a staffer’s machine that doesn’t normally handle daily WorkFlows activities. We’re doing this because we’ve found a backward compatibility problem with the Symphony release that makes it difficult to return to the normal production environment after testing. In the past, the testing procedure was to open WorkFlows at your individual workstation, change the IP Address on the configuration window to the one for the test server, select the Yes option when the “Want to upgrade client?” massage appeared, follow the client upgrade path, and then proceed with testing after the upgrade completed. When testing was done for the time being, the tester would simply change the IP Address on the configuration window back to the production server and say No when the “Want to upgrade client?” message appeared. But with the Symphony 3.2.1 release it’s not that easy. It appears that returning to the production environment after testing will require uninstalling and reinstalling the Java Runtime Environment software, which is not a trivial task. We’re working with Sirsi to resolve this issue, but for the time being we want to limit our Symphony testing to only machines that are NOT normally used for daily WorkFlows operations.-- Ken Victorson
CCS MEETINGS NEXT WEEK:
Tues., 3/24, 9:30, CCS: Bylaws & Policy Committee
Wed., 3/25, 10:00, NSLS: Governing Board
Wed., 3/25, 2 PM, NSLS: Sirsi eLibrary and Enterprise demo (please register with Richard Shurman!)
