Skip to end of banner
Go to start of banner

Part 3: Testing Functionality

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 19 Next »

[Back to Part 2: Deep Dive]

Complete and Submit Go Live Readiness Checklist

Completing the Checklist

After completing the Sample Testing Checklist, many of you have continued to test in your new environment. 

To leave no stone unturned, you 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. 

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 for Go Live Readiness Checklist

Symphony Colleges: April 29 (to allow time for new data extracts by OCLS)

Non-Symphony Colleges: May 10

NOTE: The due date on the checklist itself (May 31) is incorrect.

Additional Guidance

Approach

For most libraries, this testing will be a team effort. 

 We suggest functionality testing in the following order:

  1. User management

  2. Fulfillment

  3. Resource management

  4. Acquisitions

  5. Discovery interface (Primo VE)

  6. General

  7. 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.

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

Checklist Section

Useful Links

NOTE There is a single presentation for all Alma Workshop sessions so the starting slide numbers is provided with the recording.

The presentation file is available on the /wiki/spaces/CI/pages/438108189 page.

Tips/Hints

User management

Note: Setting broad roles for user management may help to avoid testing roadblocks.

Fulfillment

Consider the Policies, TOU & Rules set up on your configuration form. Test loans, fines, special conditions for equipment, etc.

Do they:

  • circulate for the correct loan period?

  • accrue the correct fine?

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:

NOTE Please be aware each library is responsible for training their own staff. To support this training, we are developing training material for library staff not involved in CLSP implementation (coming soon).

Analytics

[Go to Part 4 - Coming soon]

  • No labels