Chris debriefed LIS members on the process to upgrade our ILS software to Symphony 3.4.1 SP2 on Jan 12-13, 2013. Chris reported that loading the upgrade on the Symphony server went well and installed without error. Since then he has not heard of any bugs or trouble in the new version.
The only trouble with the upgrade was the problems we encountered updating Workflows. Chris reported, while we knew Windows 7 users would not be able to update Workflows on their own, we were not aware that Windows XP would not have sufficient rights to perform the update. When we learned that Windows XP users could not update Workflows, Chris began to work with our Unit Computing Manager, Ed Smith, to determine the best way to deploy the Workflows client. Fortunately, Ed had been working with a new remote software distribution and installation tool from Dell called Kace. Ed recommended that Kace could be used to remotely push out and install the Workflows update with minimal intervention from IIS and/or local PC support staff. The process was tested and, when it was determined we would use Kace successfully, Ed and Chris came up with a plan to deploy the Workflows client. The plan was put in place Monday evening and starting Tuesday morning, users Workflows began to update remotely. Chris thanked everyone for their patience during this period and added that this whole experience will help IIS build better deployment strategies in the future.
One of the LIS team members reported they were seeing incorrect labels and pull-down options on their Workflows screens. For example, instead of displaying the word Status on the "Display User" screen, they were seeing user cat1 and instead of seeing "Item Barcode" in Item Search and Display's Index pull-down menu, Workflows displayed "Item ID". Chris responded that users with incorrect labels and pull-down options should contact IIS because this indicates that one of the Workflows screen files did not update properly. As a final check, Chris reiterated that everyone with Workflows should check they are running the latest version. To check the version, click the Help pull-down menu in Workflows, then click About, and verify that your version displays as 220.127.116.11.1051. If it does not, contact IIS.
Last year OCLC announced they anticipate that the OCLC control number will reach one billion after July 1, 2013. By that date, systems like our SirsiDynix ILS, which use the control number, will need to adjust to accommodate the larger number starting. SirsiDynix is already planning for the expansion of the OCLC control number and has notified their customers that a software patch will be available in Spring 2013 to accommodate this change. The software patch will be available either as 1) a one-off patch to adjust the length of the control number or 2) bundled with a service pack of updates in Service Pack 3 of Symphony 3.4.1.
When the update is released, LIS will determine whether it is advisable to load this change as a one-off patch or bundled with Service Pack 3.
Chris reported the following enhancements coming in Symphony 3.4.1 Service Pack 3:
Mary Beth reported on the plans to implement RDA in CTS and in our SirsiDynix ILS. It includes:
Some organizations, like Marcive, have already been supplying records with the new RDA tags and working on these changes now will position us appropriately for the future.
Mary Beth and Chris reported on the status of their work for the UMD merger. Mary Beth is co-chairing the Libraries UMD Integration Catalog Subgroup along with Natalie Wadley of UMD, and Chris is also a member. The Catalog Subgroup has been tasked with the bibliographic data migration from UMD's Voyager system to our SirsiDynix Symphony system. The plan is to normalize and load all data into our test system first, then review and sign off, before loading into production.
Many other groups and teams have been created to work on subsets of the data migration tasks such as 1) a mini item type task force to define the mapping of UMD libraries, locations, and item types to RULs, 2) a serials summary holdings group to determine how to map and load serials summary holdings data, 3) a patron group to determine how to map user record data, and 4) other miscellaneous groups reviewing loan periods, reserve collections and policies, notifying vendors like Coutts and agencies like Palci of the forthcoming changes.
Starting with a list of higher-level tasks drafted by Grace Agnew, Chris drafted a list of more granular tasks that will need to be accomplished in the ILS to complete the data migration. He asked LIS team member to review the list and suggest additions or changes to insure our list of tasks is as comprehensive as possible.
Given that Nancy Hendrickson will be retiring this Spring, this was Nancy's last LIS meeting. Team members thanked Nancy for her sixteen years of service on LIS. She will be greatly missed!
Gracemary - reviewing UMD serial records.
Mary Beth - busy with UMD Integration and RDA.
Judy - Working on the Douglass merger; DOCLINE/ILLIAD subgroup will meet to plan the continued update of DOCLINE for UMD materials after the merger.
Bob - Planning to begin the record changes for the Douglass merger beginning the weekend of 2/16.
Chris - working with ASC billing group to clear out pre-2001 LOST and other old bills in preparation for the annual patron purge in March; Relais client will be upgraded the week of March 4.
The next LIS meeting is tentatively scheduled for Thursday, May 9, 2013 at 1:30 pm in the TSB conference room.