FUWG Project Name: Relaunch Lamont Lockers
Page content contributors:
Contents:
Brief description of project
The Lamont Lockers have been offline for several years (going as far back as at least March 2020) and we would like to relaunch the service. Julie and Laura have already worked with the vendors to resolve vendor-specific hardware and software issues, but we would like to:
- Complete full end-to-end testing before relaunching.
- Rename the location from Lamont Bookstop to Lamont Lockers, to align with the other locker naming conventions.
Configuration
Settings Changes
Configuration
- Change name of library to Lamont Lockers from Lamont Special Borrower Pickup
- Change name of Circ desk to Lamont Lockers
- Delay for hold shelf notification (minutes) = 30
- Edit hold shelf notification (need language)
- Confirm that existing self-check cert for Lamont lockers still works (see /wiki/spaces/LibraryTechServices/pages/59097952) self check instructions and confirm with static IP address of lockers=?
- Bibliotheca to confirm settings (or local IT); the outbound IP on the self-check unit should be selfcheck.lib.harvard.edu and the Port should be 5010
- LTS Dev Ops to confirm communication with IP and stunnel connection on selfcheck.lib
- Add back in deliver to relationships for Lamont lockers
- Activate Lamont Lockers hold shelf when ready to go live (date TBD)
Testing
Initial Testing
Initial Testing Plan/Steps
- Place requests on items for the Lamont Lockers,
- Have those items get pulled from the shelves and routed to Lamont,
- Have those items delivered to the lockers,
- Have the requester receive an available notice, and
- Have the requester successfully retrieve the request and have it be checked out to them in Alma
Testing Results
| Item Barcode and Requestor Name | Place requests on items for the Lamont Lockers
Success or Failure? Date and Notes. | Have those items get pulled from the shelves and routed to Lamont
Success or Failure? Date and Notes. | Have those items delivered to the lockers
Success or Failure? Date and Notes. | Have the requester receive an available notice
Success or Failure? Date and Notes. | Have the requester successfully retrieve the request and have it be checked out to them in Alma
Success or Failure? Date and Notes. |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Communication plan
When the service is ready to relaunch communicate via the following channels: