Skip to end of banner
Go to start of banner

Part 2: Deep Dive

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

[Back to https://clo-collaboration-spaces.atlassian.net/wiki/pages/resumedraft.action?draftId=396296263 ]

Step 1: Read Testing Resource Management Data Migration to Alma

We recommend reading the Testing Resource Management Data Migration to Alma Guide before completing the remaining tabs on the checklist. It provides explanations of Alma terminology that can be helpful in understanding your data.

Step 2: Complete the Sample Testing Checklist

Please complete the remaining tabs on the Sample Testing Checklist that apply to you as per the Checklist. Use the table below for additional guidance, things to watch for and hints.

Note: As you review your data, report major problems to Basecamp immediately. Include examples and as much detailed record information as possible.

Checklist Tab

Tasks

Pay Particular Attention to:

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 the Sample 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:

  • Searching: p. 17-20

  • Check Resources - Bibs: p. 22-28

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. 

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:

  • Check Resources - Physical holdings: p. 29

  • Sirsi Serial Control and Issue Migration - p. 30

Items Tab

Open item records to ensure that barcodes, notes, etc., have migrated as expected.

On the Sample Testing Checklist:

--lines 4 & 5: do 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 records with activated Community Zone records 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).

The combination of migration and eResource activation approaches during onboarding phase may lead to duplicates in test environment. This provides an opportunity to assess records and decide which collections to activate in CZ, which collections to manage locally and 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. 
If a bib has multiple 856 links, there will be a portfolio created for each so the number of portfolios may exceed the number of bibs in the P2E file.

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:

--Lines 9 & 10 – do all expected campuses/locations have access as expected? Do you need to check the IP ranges on your forms?

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:

--lines 10, 11 and 12

Hint: See Alma for Data Review Presentation:

  • Patron Migration & Check Patron Records, p. 43-46

  • Check Fulfillment, p. 56

Hint: See Testing Fulfillment Data Migration to Alma:

  • Loans, chapter 4

  • Hold Requests, chapter 5

  • Fines & fees, chapter 6

Courses
(if migrated)

Hint: For course search and navigation tips, visit Course Reading in Testing Fulfillment Data Migration to Alma, chapter 8, p. 59.

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

[Go to Part 3 - Coming soon]

  • No labels