[Back to Part 2: Deep Dive]
| Table of Contents |
|---|
...
Complete and Submit Go Live Readiness Checklist
...
Completing the Checklist
After completing the Sample Testing Checklist has been completed, many of you have continued to test in your new environment.
To leave no stone unturned, we suggest that you use you need to complete Ex Libris’ Go Live Readiness Checklist to guide your efforts . As an upcoming ‘to-do,’ this checklist will need to be completed and returned to Ex Libris by April 29 for Sirsi Colleges , later for the others (should give a specific date) - impacts for mapping and migration forms.
...
Note: As you review your data, report major problems to Basecamp immediately. Include examples and as much detailed record information as possible.
...
and ensure you have sufficiently tested all the relevant modules in Alma.
Additional guidance for completing the checklist is provided below.
Submitting the Checklist
You will need to provide your completed Go Live Readiness Checklist to Ex Libris on the applicable due date by uploading it to the Go-Live Readiness Checklist page in Basecamp. When you upload your completed version, please rename it with your school name.
Due Dates
Symphony Colleges: April 29 (to allow time for new data extracts by OCLS)
Non-Symphony Colleges: May 10
| Status | ||||
|---|---|---|---|---|
|
Additional Guidance
Approach
For most libraries, this testing will be a team effort.
We suggest functionality testing in the following order:
User management
Fulfillment
Resource management
Acquisitions
Discovery interface (Primo VE)
General
Analytics
...
Weave in help links from:
LibGuides
Workshop sessions
Advice:
...
Additional Form Instructions
If you are not planning on using something now or in the future (e.g., acquisitions), then you may choose not to test it. In that case, please select “NA” on the checklist.
For Primo section, only complete the Discovery Interface (Primo VE) section (p. 6-7). Do not complete the Primo section (p. 8-9).
Advice
...
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
...
Make note of any problems with functionality that may have an impact on configuration as well as mapping/migration forms
Complete for submission to Ex Libris by May 31st.
...
Checklist Schedule
...
Tasks
...
Items to watch:
...
Hints
...
Bibs Tab
Choose records from your source ILS to review and compare.
...
Use the Alma Path in corresponding Column D to perform your search.
...
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, 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:
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:
--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.
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:
--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:
Patron Migration & Check Patron Records, p. 43-46
Check Fulfillment, p. 56
...
Loans, chapter 4
Hold Requests, chapter 5
Fines & fees, chapter 6
...
Courses
(if migrated)
...
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
Make sure your testing is well rounded and that you are covering all functionality that your library will be using.
| Note |
|---|
As you review your data, report major problems to Basecamp immediately. Include examples and as much detailed record information as possible. At this point, issues may be related to configuration issues, but it is recommended to consult with Ex Libris to ensure you are taking the right steps to correct them. |
Support Material: Links to Resources/Training
[Go to https://clo-collaboration-spaces.atlassian.net/l/c/paSjtZuv ]