How to Prepare: Introduction to Data Testing
Our Polaris test database is live, staff have access to their usernames and passwords or will be receiving their information soon, and training has begun - it's time to *leap* (see what I did there?! and yes, I can hear your groans...) into data testing! As you may have heard before, data testing is a critical part of the migration process; it's how we check that our data has been converted properly and that the Polaris settings correctly reflect your library's policies and practices.
Next week, CCS will begin working with library leads to provide directives for data testing at each library. We'll establish guidelines, deadlines, and best practices. In addition to the How To Prepares you've been used to, you'll see data testing tasks that libraries will coordinate across departments, with the goal of identifying and correcting database errors prior to go-live in April.
This week, familiarize yourself with your library's unique Polaris configuration. CCS put together spreadsheets for each library containing their customized Polaris policies. Over time, data testing assignments will look at each of the elements in these spreadsheets.
During data testing, staff will compare data in Polaris against the Symphony test database and to their library's customized Polaris policy document. Instructions on how to access the test database are available on the Migration Portal; your library's IT staff was given the login information along with staff usernames on September 19th.
Getting Started with Data Testing: Item Records
When data testing, pay attention to data that mapped directly from Symphony (such as barcodes and call numbers), data elements that are unique to Polaris (such as collection and shelf location), and policies that may have been revised during profiling ( loan periods and fine codes). Using Leap or the staff client, Check the following information for each record, referring to your library's code sheet when noted (If applicable, data elements are linked to informational pages on the migration portal):
Under the Details tab:
Shelf Location (refer to the customized policy spreadsheet)
Owning and Assigned Branch
Price (if no price listed in Symphony, refer to the customized policy spreadsheet for default prices)
If the Non-circulating option is selected
If the Display in PAC option is selected (if the item displays in the public catalog)
Under the Circulation tab:
Due Date (if applicable)
Current Borrower (if applicable)
Held For and Held At (if applicable)
Under the Controls tab:
Loan Period (refer to the customized policy spreadsheet)
Fine Code (refer to the customized policy spreadsheet)
Renewal Limit (refer to the customized policy spreadsheet)
Loanable Outside of System
Under the Blocks & Notes tab:
If ACQNOTE and STAFF notes mapped to the Non-Public Note field in an item record
If CIRCNOTE mapped to the Free-Text Block field in an item record
If PUBLIC notes mapped to the Public Note field in an item record
Under the Statistics Tab:
Information about data mapping is also available on the portal if you would like to learn about how items were mapped to collections, stat classes, material types, and more.
If you find issues when inspecting records, please email email@example.com with the following information:
What specific information is incorrect and what the correct information should be
Whether you see the same error in multiple records
The Item ID. The Item ID can be located by selecting the "i" at the top of the record; this will open the Item Record Properties.