In Attendance: Linda Westlake, Karen Calhoun, Philip Herold, Elaine Engst, George Kozak, Diane Hillman, Lynne Personius, Susan Currie, John Saylor, Pat Schafer, Bill Kara, Ed Weissman, Surinder Ghangas

Voyager Updates

• Cataloging is up and running. Busy making a list of technical services questions and other quirks and Endeavor has been addressing these via a mail list.
  
• Decisions records did not migrate. NOTIS will be available through the end of July and the data will be available forever. So, these could be extracted from NOTIS as MARC records and bulk loaded at any time.
  
• Circulation history will be housed in the item records which will be available soon. History about patrons such as fines and fees will not migrate.
  
• All funds that hold money have been inputted. This includes summary and allocated funds. The other funds will be input later.
  
• Order Tests - Scott Wicks
  Will be doing another test load on the 1 million record database to test Orders. Records without funds in them didn't load the last time. Might delay acquisitions a little bit in order to retest the orders. We're writing a program that inserts the word "bogus" into records that don't have funds. Mei will rerun the test load after the program is in place. The delay in acquisitions will not affect circulation.
• Circulation configuration is not quite complete. The calendar has been entered but l needs to be extended. Policy groups need to be redone because of location codes. The client patch didn't do anything in the test but this might be because configuration wasn't complete.
  
• There will be a global print queue in either the library copy center or in 107 Olin (DLIT). Lynne is going to provide more information to the steering committee about what the demands of the print queue will be and what its operation will entail.
  
• At this point there is no circulation configuration in the 1 million record database. Will try to complete this by next week for those who need it for testing.
  
• We discussed when we would change people's security settings to allow them into Voyager when we go live. Don't want to do it too far in advance and risk people trying to log in before they're supposed to. This is of particular concern if we decide to go live on Friday 6/23. Decided that we will wait to go live until Monday so that we have Sunday to prepare.
  
• OPAC - Ed Weissman
  There continue to be changes to the OPAC screens. The "databases" button has been removed. Hook to holdings from the new FirstSearch and the SilverPlatter native interfaces will be in place on Monday. The "Exit" button is now "start over." We're considering a "comments" button. WI has a "known problems" page where they list previous complaints to cut down on repetitive negative feedback. This might be a good place for mentioning things like the diacritics and the patron login issue. We could call it something a little less negative like "Frequently Asked Questions." We could direct people to this page before they make any comments. Want to add some minimum configuration guidelines to OPAC help as well as to the library web page.
  
• Considering using mag stripe readers to ease the problem of patron empowerment. This will help when patrons are in the library but not if they're accessing remotely.
  
• Accounting - Linda Westlake
  Accounting reports for payable voucher forms, bursar fines and bursar data feeds are ready. The daily invoice control and the daily payable feed reports are still in the test phase. Funds in the 1 million record test database are not complete or entirely accurate compared to our production system. Can we copy the fund structure from the production database to the test database? In general, we need a process that avoids the time-consuming task of periodically rebuilding the actual 2,000+ fund structure in the test system.
  
• The 1 million record database will have the goal of being as close to reality as possible by clearly, this will never be. People will always need to change and update it for testing. It will be used for testing queries, testing new releases and new order loads.
  
• Reporting - Karen Calhoun
  Daily operation reports (e.g., overdue notices) are ready and everyone is trained. We think most who need it have the Reporter Client loaded. It will be interesting to see whether everyone is truly prepared. Lydia is going to visit all the libraries to do a final check of the reporting client. She has been the driving force behind the reporting committee…a big thank you to Lydia! The reporting working group has made a proposal that will go to IMT and to the steering committee about the future of the group. The technical services production statistics group met for the first time. They hope to have some of the reports ready for start of the new fiscal year. The technical services production statistics data will be produced using Voyager add-on software developed by Gary Strawn called "VgerSelect." The MyLibrary group wants to use the same software package to produce current awareness reports (new accessions) for MyLibrary. If we can get accessions lists reports from this package many departments may be able to use it. Might also be helpful in tracking reserves. We are still planning to bring Alan Manifold in from Purdue to consult with us on fund accounting reports that are wanted by selectors.
  
• Steering committee has agreed that December 2000 is the best time for upgrading to Voyager 2000. The system will have to come down during the upgrade. After 2000 though, they will build in a function that allows the system to stay functional during upgrades.
  
• Endeavor is doing training for the 2000 release in Rochester but it seems to be aimed mostly at acquisitions.
  
• The LC file is ready for Mei.
  
• Library Systems - Surinder Ghangas
  We need to start using our disk space more efficiently on our servers. Surinder is looking at ways to accomplish this. Full back-ups of the voyager system have been done every night. We will keep it this way until we go live. After we go live, we will do a full backup every Friday night and other partial backups throughout the week. We will store five weeks of full backups and 35 days of partial backups.
  
• We will send out a message with the new Z3950 information so that we can distribute it to those who use it. Will also contact Endnote with this information as well. There is no easy way to redirect users to the new Z3950.