Data Testing Guidelines

This page provides guidance to prepare your library for the final load into Alma and Primo. If you’re unsure how to proceed in the project from this point forward, walk through the lists below.

Data Testing

Gather a team of experts - find staff at your institution with expertise in each functional area.
Create user accounts for your expert staff members.
Review the Testing Migrated Data guides provided by Ex Libris. Use them as a reference when moving through step 4 below.
Visit the Data Testing Worksheets page. Read the description of the worksheet Sarina provided to your campus and have your team work through the tabs that apply to their area of expertise.
1. Find records that fit the description in each column.
2. Compare the records you find in Alma to the same records in your current ILS. Use the questions in column E (“What are you testing?”) to guide your analysis.
3. Record your results and observations in columns F, G & H.
Run through the sample Analytics reports to get a snapshot of your data. If you need a crash course in Analytics, look through the Analytics materials listed on the Videos and Reading by Functional Area: Analytics page on the ULMS project website.
Test Electronic Resources and SFX data.
1. Use the ERM Task Force Checklist. Disregard the due dates attached to the list, instead use the list as a guideline for testing your institution’s E-Resources.
2. Refer to the the Post Load Review page as an additional E-Resources testing guide.
It's important to record the problems that you see in your test load and identify a path forward for each issue. Use the Final Migration to-do List to record actions that need to be taken prior to the final migration.
Note: if you find a record and are confused by its placement and/or characteristics in Alma refer to the Migration Decision Tree for a visual guide of migration processes.

When you find a data issue ask the following questions:

Can you resolve the issue by cleaning up the data in your current ILS?
Can you resolve the issue by making a change to your Field Mapping or Migration Form for the final load? Can you resolve the issue by making a change to your final load data export?
Can you make configuration changes to achieve the desired result?
If there isn’t a method to migrate data as you expect, is there a solution to resolve this issue post-migration in Alma? Refer to the post-migration clean-up
section on the ULMS project website for a list of areas that require post-migration data massaging.

Any problems that can’t be solved using the methods above should be sent to Ex Libris by opening a Salesforce ticket. Data problems must be reported to Ex Libris via Salesforce by December 15, 2016.

Alma/Primo Configuration and Functional Testing

Functional testing should consist of performing familiar day-to-day activities to ensure the system is behaving in an expected manner. Functional testing can also help identify particularly challenging areas that may require additional training. A list of hands-on activities to aid in functional testing is currently in development (as of 8/18/16).

When you find a functionality issue ask the following questions:

Analyze relevant configuration options and ensure your selections match your intended output.
Search for documentation of step-by-step instructions on the Ex Libris knowledge center. Be creative with your search terms and ensure your search results include videos and powerpoints as they also contain useful content.

If unexpected behavior persists in Alma or Primo after making configuration changes and perusing the product documentation, open a Salesforce ticket with Ex Libris including screenshots and the exact steps taken when you encountered the problem.

Configuration options should be established for Go-Live by May 2017. However, after Go-Live these configurations can be changed.