In Attendance: Bill Kara, Elaine Engst, Philip Herold, Susan Currie, Diane Hillmann, Scott Wicks, John Saylor, Ed Weissman, Lynne Personius, Pat Schafer, George Kozak

I. Availability of Voyager Databases

The first test migration database will be removed from Library on Monday 3/27. We will ask Voyager to wait until 10AM EST to do this.

A sample database called Traindb is being created on Library 11 right now, drawing records from the first test migration database currently housed on Cornelldb. This database will be available tomorrow. It will contain 100, 000 records biased towards serials. Endeavor is attempting to bring all the configuration files over from Cornelldb as well. If the configuration files do not migrate, George Kozak will perform the migration manually. The hope is that we will be able to do all the same work with Traindb as we have been with Cornelldb.

Voyager will begin building the second test database Monday 3/27. It will be based on the back-up of NOTIS from Friday 3/24. We will be evaluating and configuring the database through April and it will be available on May 1.

On May 1 Voyager will create testdb - a database of 1 million records taken from the second test load. Testdb will be housed on Library 11 and will be the database we use for training and testing from that point forward. It is important that we have all the configurations finalized by the time this database is created.

II. Systems Administration Discussion
Goal: Recommendation to Steering Committee

Who will be responsible for SysAdmin through the implementation process?

Diane Hillmann came up with a spreadsheet that covers each portion of SysAdmin and who should be responsible for the configurations. We went over the spreadsheet and finalized the names of those responsible. Diane will make necessary changes to the spreadsheet and redistribute it. The people named in the spreadsheet will see their portion of SysAdmin through the cut-over and until we switch over to Voyager 2000. At that point, some system needs to be in place to ensure regular maintenance and standardization of the configurations and to keep a record of changes being made.

What form will the regulation of SysAdmin take after the upgrade to Voyager 2000?

Lynne suggested a committee made up of representatives from the various functional groups with turnover in membership accounted for by rotating positions. The alternative is if each functional group only took care of its own portion of SysAdmin. Here are some points that were raised:

• The committee would provide some structure for turnover. It would provide those new to SysAdmin with the larger picture and the history behind decisions previously made. It would be a good vehicle for training and documentation.
• The committee would help coordinate areas where there is overlap between units. Using the functional groups during the implementation process has made everyone aware of the limitations they impose.
  
• The committee would ensure that one or two specific people in each unit would be in charge of SysAdmin rather than entire units.
  
• Things like location codes need to be kept in check because so many things feed off of them.
  
• We need to have up to date and accurate documentation that is readily accessible to avoid confusion among users. This will be best achieved by having one person responsible for making changes and recording them in the documentation.
  
• Sign-ons to SysAdmin give access to everything so those making changes need to be aware of the boundaries in their jurisdiction.
  
• Talking about how the configurations should be is different than actually making the changes and maintaining the database.
  
• IMT will continue to work on Voyager until the upgrade to 2000. Perhaps this group could develop into the committee to coordinate SysAdmin
  
• There should be a protocol for what groups should be consulted about proposed changes.