[Back to Part 2: Deep Dive]
| Table of Contents |
|---|
...
Complete and Submit Go Live Readiness Checklist
Introduction
...
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, you will need to complete Ex Libris’ Go Live Readiness Checklist to guide your efforts and ensure you have sufficiently tested all the relevant modules in Alma.
Due Date
Symphony Colleges: This checklist Additional guidance for completing the checklist is provided below.
Submitting the Checklist
You will need to be completed and returned provide your completed Go Live Readiness Checklist to Ex Libris on the applicable due date by April 29 [link to Basecamp] to allow time for OCLS to create new data extracts
Non-Sirsi Colleges: This checklist will need to be completed and returned to Ex Libris by May ?? (give a specific date) as there may be 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.
...
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
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
Make note of any problems with functionality that may have an impact on configuration as well as mapping/migration forms
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
Acquisitions
Resource management
Do they:
| ||||||||
Resource Management and Inventory |
| Default cataloger permission levels will allow all cataloguers the ability to test all functionalities. | ||||||
Acquisitions |
| While not all libraries are migrating acquisitions, your test environment provides a good opportunity to explore potential. | ||||||
Discovery interface (Primo VE) | Note: only complete checklist pages for Primo VE, page 6 & 7 Don’t forget to test functionality for linking and accessing patron accounts from both on and off campus. | |||||||
General | Ex Libris Training Links: |
| ||||||
Analytics |
...
[Go to https://clo-collaboration-spaces.atlassian.net/l/c/paSjtZuv ]