1 / 21

System Migration

System Migration. IS 582 Spring 2007 Dr. Dania Bilal. Definition. Switching to a new system Types Change to a new software package Change to a new interface (DOS to GUI) Change to a new platform (Windows to Unix). Reasons for Migration.

Download Presentation

System Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. System Migration IS 582 Spring 2007 Dr. Dania Bilal

  2. Definition • Switching to a new system • Types • Change to a new software package • Change to a new interface (DOS to GUI) • Change to a new platform (Windows to Unix)

  3. Reasons for Migration • An interface is being phased out by the software vendor (e.g., DOS interface) • Existing system does not support recent communications protocols, such as TCP/IP to allow for Internet presence. • Existing system performance is unsatisfactory.

  4. Process of Migration • Assess needs • Assess weaknesses and strengths of existing system and unresolved problems • Select a new system • RFP

  5. Process of Migration • Find problems with current circulation module and data • Find problems with current bibliographic data

  6. Process of Migration • Provide vendor with sample circulation and bibliographic data. • Ask vendor how certain problems with some data will be handled in the system under consideration.

  7. Database Cleanup • Clean up circulation records • Clean up bibliographic records (i.e., MARC) • Clean up other existing records (e.g., acquisitions, serials)

  8. Database Cleanup • Inventory the collection • Weed the collection • Delete records for which you have no holdings and for which items are lost or missing.

  9. Database Analysis • Evaluate existing databases (circulation, cataloging, etc). No need for shelflist analysis. • Familiarize yourself with current practices: • MARC tags and fields, location codes, copy information, call number, holding codes, circulation periods, barcode symbology, etc.

  10. Database Analysis • Learn about the nature of each data record and the database structure of the entire system. • What is the relationship between a bibliographic record and an item record, for example?

  11. Database Analysis • If you do not know the database structure, data relationships, and current practices, you will not be able to communicate to the software vendor how certain data should be handled in the system under consideration.

  12. Data Completion • Make decisions about items that are not cataloged in the existing system or files that are not established for some items, such as authority files. • Decision: Will you wait until the new system is in place to complete these activities, or will you perform these activities in the current system?

  13. Data Completion • Make sure you stipulate vendor promises in the contract, if the vendor decides to take care of the odds and ends you have in the current system.

  14. Data Migration • Extract data from different modules and send to vendors under consideration to test in their systems at their sites. • Vendors should identify records that do not load and determine the reason for failure to load.

  15. Data Migration • Implement the new system • Back up the old system prior to switching to the new system. • Test data loads in each module available to determine how accurately they map into the new system.

  16. Data Migration • Develop a checklist of potential problem items to examine during implementation. • Load the entire database (patron records in the circulation database, MARC records in the cataloging database, etc.) once the sample data load has been implemented successfully (i.e., mapped correctly into the new system).

  17. Data Migration • Run the old and new system in tandem for a while until everything goes to your satisfaction. • Do not discontinue the support for the old system too soon, especially before completing the migration of all data from the old into the new system.

  18. Testing Data • When testing data, look for: • Long MARC records with 520 and 505 field tags • Bibliographic records for multi-volume items • Bibliographic records for multiple copy items

  19. Testing Data • Short MARC records • Long and/or complex call numbers • MARC records with attached item records • Patron records (fines, overdues, etc.)

  20. Data Migration • The accuracy of data migration depends on adequate preparation, data extraction for testing, testing data, developing a plan to map records from the old system to the new one, and testing the accuracy of data after migration.

  21. Tips for Successful Migration • See Text, p. 149.

More Related