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 #6 - |
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. Next steps are to run a full synchronization to see how long it takes. Incremental can add/update; drop has not been implemented yet. EN | ||
2 | Must have at go live |
| Extracts from Alma are operational. Currently populating a crosswalk index of record identifiers to support item availability lookup. Working toward end-to-end data flow so testers can view Alma data in a local TRLN Discovery instance. | ||
3 | Must have at go live |
| Ready to submit test files to Duke AP - they aren’t available until early May for validation. Work continues on reporting and error handling JB | ||
4 | Must have at go live | Can use code from Harvard as a start | Started intial review of this integration on 4/22/24. Communicating with Harvard with a request to review their code and also reviewing acquisitions APIs. JB | ||
5 | Must have at go live |
| Patron information, loans, fees and fines information is available. Work is ongoing on viewing item lists and placing requests. Work to differentiate title versus item is complete. AEON redirects as expected. Testing and debugging continues. EN | ||
6 | Must have at go live |
| First meeting scheduled with CaiaSoft staff 5/2/2024. | ||
7 | Must have at go live | Discovery Working Group taking responsibility | Ongoing. Work will be discussed at 5-1 First Wednesday. EN | ||
8 | Must have at go live |
| Requirements are complete; waiting for developer capacity. EN | ||
9 | Must have at go live | or at least by early August | |||
10 | Must have at go live | tied to TRLN Discovery project | |||
11 | Must have by June 10 for ExLibris to load during cutover | Coding was completed for a test run in Dec. Open tasks are to fix some bugs and add a few changes based on users feedback on test data load. 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 |
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). | Met with Desktop Support to share installation instructions and create timeline for application to be pushed to staff computers. RL and RD staff working on call number parsing and label testing. KHN | |
2 |
| Must have at go live | Configuration - VMs, print daemon (desktop support not developers) | Met with Desktop Support to share installation instructions and create timeline for print daemon to be pushed to staff computers. KHN | |
3 |
| Must have at go live | Configuration LTI with DLI; exporting Courses data | Loaded FOLIO courses, reading lists. LTI communication with Canvas working. Starting onboarding subject matter experts, working on loading .pdf files of readings. KHN | |
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)