Production Load Data Review

Last updated: 6/3/2020

This document provides an overview of the steps libraries should take to identify example records. Information on how to review your Alma Production/Cutover Load, and how to report any problems found in the migration of your data from Voyager to Alma will be added by early June.

Identifying Test Cases

Your library’s staff should have identified sample records throughout your Voyager database that exemplified both good data and potentially problematic data for the Test load. You should verify that your examples are still valid, so you are able to review them when instructed by CARLI staff during the Production/Cutover load. You should verify/find these examples now, before the Production/Cutover load is complete.

For the Test load, to assist you in identifying examples, CARLI staff shared a set of Data Migration Review worksheets. The worksheets identified many different record scenarios divided up by the type of data involved. Your library may not have data that meets all the criteria listed. You should have identified anything of interest to your library in the migration. For larger institutions we recommended dividing these worksheets among the functional areas that work with the data most frequently, for example you should have had your Acquisitions staff look for examples from the Acquisitions client, and your Circulation staff look for examples related to Patrons and Circulation transactions.

The following table identifies the dates when library data were extracted from Voyager for the Production/Cutover load. Please note: For Circulation and Patron related examples, you will want to wait until closer to the Circulation Freeze (June 18, 2020) to find examples.

Data Review

During Data Review it is important to view your sample in both Voyager and Alma, and verify your data has migrated to Alma.

Bibliographic Data Review (Bibs, MFHDs, Items, P2E, Acq, Reserves, Link Resolver) will take place June 17-19, 2020.

Fulfillment Data Review (Patrons, Charges, Fines & Fees) will take place June 22-23, 2020.

As you review, it will be helpful to have:

  1. Your library's final Migration Form (provided in your library's Production Load Box folder; file name: Alma Production Migration Form XXX_FINAL.xlsm)
  2. The Voyager to Alma Migration Guide. Ex Libris strongly recommends reviewing this document in advance and keeping it handy during your testing. This document defines the selections made on your migration form, and also identifies ways that data will be migrated or will not be migrated from Voyager to Alma.
  3. Your library's Data Migration Review worksheets 
  4. Ex Libris' testing scripts. As part of reviewing the migration data, you will also be testing your access to the system and determining whether records are behaving correctly. Ex Libris provides testing scripts that staff can use to check both the data and the functionality of records. These include:

Testing Fulfillment Data Migration to Alma
Testing Resource Management Data Migration to Alma
Testing Acquisitions Data Migration to Alma

  1. Production load reports and stats. As part of the migration process several reports are created and will be provided to assist you in evaluating your data. More details about these reports is available on the Alma Production/Cutover Load - Reports and Statistics page
  2. TheAlma Data Migration Review- Alma Searches page. 

Additional resources that may be helpful in your review:

Reporting Problems

Each I-Share library has established a single point of contact, the Alma/Primo VE Contact, to communicate with CARLI over the course of the project. As staff at your library work through the various examples and test scripts, they should always keep your library’s Contact in the loop. The Alma/Primo VE Contact is responsible for collecting problem reports from your library, and then communicating those problems to CARLI. 

CARLI will review reported problems and attempt to replicate what library staff found in Alma. In order to do this, having concrete details is critical, not just about the problem found, but about the data being searched, the path to that data, and the results that library staff were expecting. Library staff should also keep track of the Alma user roles in use for their accounts, as this may affect some results.

When reporting a problem to CARLI, please report as many of the following details as possible:

  • Describe the problem that you have found.
  • Include the Alma record identifier for the problem (e.g., MMSID, PO Line #) or create a Set (logical or itemized) in Alma and share the name of the problem set.
  • Include the Voyager record identifier for the original data (e.g., BIB ID, MFHD ID, Patron barcode, etc.).
  • Identify the area of Alma that you are using (e.g., Resource Management, Fulfillment).
  • Identify the location you have selected to work from in Alma.
  • Identify your user login name and user role(s), if known.
  • Describe what you expected to see instead of the problem.
  • Provide the Alma Error number and error reference id, if displayed.

Report these details to . This will establish a CARLI Support ticket that allows all CARLI staff to monitor issues and identify if identical issues are present in other databases.

  • Problems that look similar should not be assumed to have the same source issue, and should be reported separately. 
  • Problems that have already been reported once by your library do not need to be reported again, but library staff may follow-up to the original CARLI Support ticket with additional examples.

After reviewing the problem, CARLI staff will report the problem to Ex Libris via their tracking system, SalesForce, with one case filed per problem reported. The Alma/Primo VE Contact will be copied on each case and may review and respond to follow-up requests from CARLI or Ex Libris by email.

Both CARLI staff and Ex Libris staff will likely be responding to several reports at the same time. You may not receive an immediate response about your report.

Accepting your Data Loads

More information coming soon.