...
Checklist Tab | Tasks | Items to watch: | Hints |
|---|---|---|---|
Bibs Tab | Choose records from your source ILS to review and compare. Column A of each Sample Testing Checklist tab contains suggestions for types of searches you might perform when checking. Use the Alma Path in corresponding Column D to perform your search. | On theSample Testing Checklist: line 4: were unique IDs preserved? 004 - 951 (SIRSI?) line 11: diacritics; identify and clean up invalid Unicode characters line 15: Volume numbers for multi-volume sets from SIRSI French in Alma – see Basecamp thread at French in Alma (basecamp.com) | Hint: A ‘Duplicate Title Analysis’ job can be run in Alma if you would like to test for duplicate bibliographic records. Hint: For additional search and navigation tips, visit Finding and Reviewing Bibliographic Records in Testing Resource Management Data Migration to Alma, chapter 2, p. 7. Hint: See Alma for Data Review Presentation:
|
Holdings Tab | Verify that collections have migrated to the right locations – this important for determining if items will circulate as expected. Look at specifics by opening holdings to inspect content. | On the Sample Testing Checklist: --line 4: counts of records expected in specific libraries/locations --line 6: holdings records that may have found their way to the ‘unassigned’ location, and need to go to specific locations at cutover. Further actions may include an update to your migration form or ILS information. Inform Ex Libris of changes. | Hint: Reflect back on your migration, mapping and configuration forms – testing at this level may indicate that changes are needed to final migration & mapping forms or the files sent for cutover (CO). Hint: For additional search and navigation tips, visit Finding and Reviewing Holdings Records in Testing Resource Management Data Migration to Alma, chapter 3, p. 15. Hint: See Alma for Data Review Presentation:
|
Items Tab | Open item records to ensure that barcodes, notes, etc., have migrated as expected. | On the Sample Testing Checklist: --line 4 - Did items in temporary locations migrate as expected? --line 5: do item locations match holdings locations? Did other item policies perform as expected? | Hint: Reflect back on your migration, mapping and configuration forms – testing may indicate that changes are needed to final migration & mapping forms or the files sent for cutover (CO). Hint: For additional search and navigation tips, visit Finding and Reviewing Item Records in Testing Resource Management Data Migration to Alma, chapter 4, p. 20. Hint: See Alma for Data Review Presentation: Check Resources - Physical Items, p. 31-34 |
P2E Tab | Review migrated eResource records. Compare migrated eResource collections with activated Community Zone collections and check for overlap as a result of the ‘let it fly’ recommendation. Libraries may want to consider this tab in conjunction with the Link Resolver Tab (below). | Line 7: check for any items that may have been missed on your P2E list. Note: The combination of migrated eResource records from ILS and eResource activation during onboarding phase may have lead to duplicates in test environment. The test environment provides an opportunity to assess records and decide which collections to activate in CZ, which collections to manage locally – and to determine whether it may be useful for some collections to be managed at the NZ level. | Hint: For each bib provided in the P2E file, a portfolio is created for each 856 link. Hint: For additional understanding of the electronic model, visit Testing Resource Management Data Migration to Alma, Electronic Portfolio Records and Electronic Collection Records, chapter 1, p. 5. For additional search and navigation tips for testing electronic data, visit Finding and Reviewing Electronic Titles chapter 2, p. 14. Hint: See Alma for Data Review Presentation: Check Resources - Electronic, p. 35-37 |
Link Resolver Tab | Refer to your link resolver form. Confirm that collections have migrated as listed. | On the Sample Testing Checklist: --Line 9 - Do all expected campuses/locations have access as expected? Do you need to check the IP ranges on your forms? --Line 10 - Does off campus access to link resolver portfolios perform as expected? | Hint: See Alma for Data Review Presentation: Check Resources - Electronic - Link Resolver, p. 38-40 |
Fulfillment Tab | If applicable, verify that loans, fines, fees and blocks migrated as expected. | If applicable, on the Sample Testing Checklist: --line 10: Patrons with active fines/fees --line 11: Patron with current loans --line 12: Patron with lost items | Hint: See Alma for Data Review Presentation:
Hint: SeeTesting Fulfillment Data Migration to Alma:
|
Courses | Check active, inactive courses and reading lists. | Hint: For course search and navigation tips, visit Course Reading in Testing Fulfillment Data Migration to Alma, chapter 8, p. 59. Note: Reading list citations in test environment will not be retained at cutover (CO). Note: as per Basecamp discussion at Course Reserves and Booking Requests courses and reading lists created during testing will not be retained at cutover if you aren’t migrating courses/reading lists. Hint: See Alma for Data Review Presentation: Check Courses, p. 47 | |
Acquisitions (if migrated) | Note: venders migrated will be retained a cutover (CO), but funds entered during your test phase may not be retained at cutover. Hint: For a key to understanding migrated acquisitions data, visit Testing Acquisitions Data Migration to Alma. Hint: See Alma for Data Review Presentation: Acquisitions, p. 48-54 |
...