Data testing worksheets

Each campus has access to their own data testing worksheet, that can be used to capture and record any problems that you encounter with your migrated data. You can view a generic version of this spreadsheet here:

https://docs.google.com/spreadsheets/d/1HyzGofftmtyjAc4eiLZSyvIgRiM54gFiXBCYLQz3Cm8/edit?usp=sharing

For each example, each column is intended to capture the following information:

Unique characteristics of the record: the particular situation that this example is capturing. This can vary based on specific data elements, or any particular characteristic of a record that you might encounter in your system.
Record number in current system: record the barcode or record number of the record that matches the scenario in your current system here. This allows you to identify specific records that you want to look at in Alma. In Alma, you can compare both the specific situation that this scenario captures, as well as the other parts of the record. It's possible that the specific piece of data that you capture in this scenario migrates correctly, but a different aspect of the record does not. You will want to record anything that does not migrate correctly in this situation.
Create Lists criteria to identify matching records in your current system: This applies to Millennium/Sierra only. If there is a Create Lists query that can be used to identify records that match a particular scenario, the criteria is listed here for you to use in your current system to identify possible examples. Not all situations can be captured through Create Lists. For scenarios that can't be identified through Create Lists, you may have subject matter experts that are aware of examples that meet the criteria and can identify example records. Staff can also record new examples over time if they encounter new or unique situations that meet unusual criteria.
Alma MMS ID: record the Alma record number for the relevant record in Alma. This will ensure that you can report a specific example to Ex Libris if there are any problems that you encountered. It will also allow others to easily find the record that you looked at in Alma.
What are you testing?: This provides a general guide for what you are testing for this particular scenario.
Accept/Reject?: This column can be used to track whether the migrated data for a scenario is acceptable or unacceptable. If you encounter a problem with a particular use case, you can select "Reject" here until some type of resolution is reached regarding this problem. A resolution may take the form of: altering your Field Mapping or Migration Form, post-migration clean-up, or a resolution provided by Ex Libris. When first going through your data, this can allow you to quickly capture any problems that you encounter and you can later return to investigate them further.
If rejected, describe the steps that you took and the problem that you encountered: Record the steps that you took and the specific problem that you encountered if you did encounter a problem. This will allow you to report this problem to Ex Libris and allow others to replicate your steps to see if they also encounter this problem.
Resolution required? Place any steps that you are aware of to resolve this issue: For some problems, you may immediately know what you need to do to resolve the issue. Perhaps you forgot something on one of the migration forms, and you know you need to adjust your forms in order to address the issue. If you know what needs to happen to resolve the issue already, you can place "Accept" in the Accept/Reject column, and enter in the steps necessary to reach the resolution.

If your campus thinks of any new use cases that they want to test in Alma, you can feel free to add rows to your campus spreadsheet to record these new cases. You can also use this sheet to record any problems that you encounter that are not specifically listed on the spreadsheet. The goal of the spreadsheet is to help you track issues that you encounter and ensure that you are surveying your data in Alma thoroughly.