Migration of Automated Systems

1. The Process

1.1. Database Cleanup

1.1.1. Have an Inventory for Your Collection

1.1.2. Weed Collection/Delete Bibliographic Records

1.1.3. Evaluate Codes & Circulation

1.2. Database Analysis

1.2.1. Analyze Bibliographic & Circulation Data

1.2.2. Analyze Additional Modules

1.3. Database Completion

1.3.1. Decide How to Catalog Items Not in System

1.4. Data Migration

1.4.1. Test for Accuracy In Records/Catalog

2. Succeed Factors

2.1. Level of Understanding of Database

2.2. Vendor's Experience

2.3. Staff Development

2.4. Planning & Preparation

2.5. Involvement of User

2.6. Effective Communication With Everyone Involved

2.7. RFP Specifications Are Met

3. Rationale:

3.1. System Must Support Web Access/Internet

3.2. Cutting Edge Technology Support

3.3. Newer Modules are Supported

3.4. Need a System Other than DOS-based

3.5. Vendor Performance Needs Improvement

3.6. Flexibility & Expandability Are A Must

3.7. School Districts Are Moving To WANs

4. Recommendations

4.1. Create a Detailed Checklist of Every Functionality Currently Used

4.2. Expect Transitional Problems

4.3. Cross-Check RFP Specifications vs. Vendor's Migration Proposal

4.4. Don't Rely on Short-Term Solutions

4.5. Have Performance Audits on Site

4.6. Invest in Training