Overview:
With the Alma migration comes connecting the new Library Services Platform (LSP) to third-party applications in use across the libraries and Duke. This project is an overarching document for the integrations the DUL Agile team need to complete before go-live on July 10, 2024.
Project Board | |
|---|---|
Start Date | Sprint zero |
Current Sprint | Sprint #8 - |
Target Date | - data freeze / Ex-Libris-imposed-deadline for integrations - Alma Go Live |
Status | See list below for status updates |
Dependencies | Delivery of Duke’s Alma instance (1/18/2024) |
Notes | Target date is set by Ex Libris as part of our project plan. |
Goal: The individual integrations should be at least at MVP for the June 7 deadline.
Scope: If the team determines some of the requirements need to wait until post-implementation they should communicate that to the LSPSG through Karen and the product owners (Julie and Erin).
Team:
Name | Role | Responsibility |
|---|---|---|
Julie Brannon Erin Nettifee | Product Owners |
|
Derrek Croney | Scrum Lead Developer / DevOps Analyst |
|
Stewart Engart | Developer |
|
Jeff Fleming | Developer |
|
Zeke Graves | Developer |
|
Matt Harrington | Consultant |
|
LSP Steering Group | Stakeholders |
|
Quincy Garbutt | Stakeholder |
|
Karen Newbery | Project Sponsor |
|
Collaboration and Communication Strategy
DULdev Jira and Confluence for issue management and documentation.
Zoom for project meetings and to share progress with stakeholders.
The project team will share progress with stakeholders via biweekly Zoom
The team will hold two week scrum schedule.
Week 1: Monday Sprint meeting
Week 2: Backlog refinement, planning poker, sprint review for stakeholders
Requirements
Priority # | Title | Jira Epic | Importance | Notes | Status |
|---|---|---|---|---|---|
1 | Must have before go live |
| File retrievals are running as expected. We have run a full patron synchronization (70,000 records) and it took less than ten minutes, which is awesome. Functionality to include name suffix is done. Incremental can add/update; drop has been developed but not yet tested. EN | ||
2 | Must have at go live |
| Running a final full test load which is expected to complete on Wed June 5th. JB | ||
3 | Must have at go live |
| User training is scheduled with Med Center Library for 6/3/24. Feedback on last set of files sent to Duke AP was that the location of two data elements were swapped in the fixed file. Discovered this was caused by existing layout documenation being out of sync with code that’s running in production. Fixed and provided another set of test files to Duke AP for review. Still have an open question about the DKU E-resources company code and fund to set it up correctly for ingest with Duke AP. JB | ||
4 | Must have at go live | Can use code from Harvard as a start | Completed the initial invoice creation jia. More unit testing is needed, but initial testing looks like invoices are being built correctly. Additional jira is in the pipeline to set this up for users to run on demand by selecting a file to ingest. JB | ||
5 | Must have at go live |
| A volunteer external to the library has completed rigorous testing of the CRS with major patron groups and reporting results for adjustments. This identified some behavior that we will change in circulation rules as well as some issues with the location guide that we are tracking down. We’ve completed an implementation of a “read-only” mode that will be used to support the fulfillment freeze and be able to handle any Alma downtimes in the future. EN | ||
6 | Must have at go live |
| Configuration in Alma is complete. Data has been extracted from Alma and sent to CaiaSoft. CaiaSoft is actively loading the data to our CaiaSoft test instance. We’ve begun testing patron requests. | ||
7 | Must have at go live | Discovery Working Group taking responsibility | Ongoing. Tom C. provided an update at May First Wednesday ( First Wednesday 2024) | ||
8 | Must have at go live |
| Work has begun with Jack Hill and David Chandek-Stark. A demo will be conducted internally on 6-3-2024. EN | ||
9 | Must have at go live | or at least by early August | |||
10 | Must have at go live | tied to TRLN Discovery project | Work has begun as part of TRLN Discovery work. EN | ||
11 | Must have by June 10 for ExLibris to load during cutover | Waiting for developer capacity. Open tasks are to fix some bugs and add a few changes based on users feedback to the test data load from December. Created a list of test cases so that testing can occur quickly once a test file is ready. JB | |||
12 | Post go live | Users will be able to view these logs in Aleph after go-live, but we need to import the data so that’s is available in Alma. | |||
13 | Post go live | Would need to adjust the landing page if not at go live | |||
14 | Migrate FOLIO ERM Organizations Contacts and Interfaces to Alma | Post go live | |||
15 | Post go live | Connection to DSC for item history | |||
16 | Migrate 360 Notes to Alma E-Resources | not yet created | Post go live | The notes in 360 contain information to identify the owning library (Law, Med, etc). |
These will likely not require developers, but may require desktop support or assistance from Learning Innovation:
Priority # | Title | Jira Epic | Importance | Notes | Status |
|---|---|---|---|---|---|
1 |
| Must have at go live | Application SpineOMatic being tested (Ex Libris’s recommended software for spine labels). | RL and RD staff working on call number parsing and label testing with desktop support client. EN | |
2 |
| Must have at go live | Configuration - VMs, print daemon (desktop support not developers) | Daemon has been tested and works as expected. Next steps are to configure individual daemons for libraries and document configuration. OIT colleagues are working on this. EN | |
3 |
| Must have at go live | Configuration LTI with DLI; exporting Courses data | Leganto project is fully underway with separate project team and timeline for August implementation. EN | |
4 |
| Must have at go live | May not require developers - Index Data will help with testing and set-up | ||
5 | ABLE Binding Software | Shortly after go-live | Uses z39.50 to communicate with Alma |
Working Areas:
DulDev list of Alma integrations (DulDev Atlassian account required)
Ex Libris Basecamp list of Integrations (Ex Libris Basecamp access required)