Orbis2 Activity Report
Data Migration preparation and hardware selection dominated the month of October in the Orbis2 project. Implementation groups continued to work with the Voyager clients, sysadmin and workflows.
In preparation for our early November data migration test of bibliographic, holdings, authority and item records from NOTIS to Voyager, Endeavor programmed our special extract requirements. In conjunction with Endeavor staff, Kalee Sprague tested these customized routines. Special processing incorporated into this initial conversion includes:
A couple of special requirements will be tested after this initial extract. These requirements include:
Also in preparation for this first test extract and conversion, a draft mapping table was established by the Location Subgroup (http://www.library.yale.edu/orbis2/implementation/workinggroup_implementation.html). The Draft Posted at that URL are also location and loan code usage figures. Libraries are reviewing their use of loan codes and refining the location +loan code mapping tables.
Based on an exhaustive, year-long investigation that included wide consultation throughout ITS, certification testing of servers at a Sun testing center, a study of disk and tape system options and the analysis of successive new offerings of technology by Sun, David Gewirtz presented to the MMG three possible hardware configurations for the production Orbis2 environment. Davidís detailed report is available at: http://www.library.yale.edu/orbis2/public/wkgroup/mmgroup.html
The MMG authorized the purchase of a configuration that will provide substantial redundant services and disaster recovery. Our Orbis2 hardware environment will consist of a production system located at the 155 Whitney Data Center that is comprised of three servers : a primary database (ORACLE server), an application and keyword server, and a public interface web server. An almost identical configuration will be installed at the Watson Data Center as a test environment. Additionally, a fourth server will be installed at Watson to act as a development environment.
This configuration, spread-out across multiple servers and installed in separate locations, will minimize service interruptions due to system upgrades, new releases, report generation and development activities. Furthermore, it creates a disaster recovery capability. In the event of a serious problem with the environment at 155 Whitney (e.g. a fire), within approximately 24 hours, the equipment in the Watson center could be configured to run, without any degradation in performance, the production Voyager system.
Debbie McGraw is leading our effort to finalize our hardware purchase from Sun. We anticipate placing the order before the end of November. We will receive the hardware either shortly before Christmas or just after the New Year.
Implementation GroupsThe Acquisitions, Cataloging, Circulation and OPAC groups continued to work through system tables, workflow, and Voyager functionality issues. See http://www.library.yale.edu/orbis2/implementation/index.html for notes from each of the workgroups.
Return to Orbis2 Implementation Site