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 |
Target Date | - data freeze / Ex-Libris-imposed-deadline for integrations - Alma rollover |
Status |
|
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
# | Title | Jira Epic | Importance | Notes | Status |
|---|---|---|---|---|---|
1 | Must have before go live |
| |||
2 | Must have at go live |
| |||
3 | Must have at go live |
| |||
4 | Must have at go live | Can use code from Harvard as a start | |||
5 | Must have at go live |
| |||
6 |
| Must have at go live |
| ||
7 | Must have at go live |
| |||
8 |
| Must have at go live |
| ||
9 |
| Must have at go live | or at least by early August | ||
10 |
| Must have at go live | soon as possible after go-live | ||
11 |
| Must have at go live | tied to TRLN Discovery project | ||
12 |
| Post go live | Would need to adjust the landing page if not at go live | ||
13 | Migrate FOLIO ERM Organizations Contacts and Interfaces to Alma |
| Post go live | May not require developer resources, maybe Postman | |
14 |
| Post go live | Connection to DSC for item history | ||
15 |
| Post go live | Coding mostly done, working on some tweaks based on data review |
These will likely not require developers, but may require desktop support or assistance from Learning Innovation:
# | Title | Jira Epic | Importance | Notes |
|---|---|---|---|---|
1 |
| Must have at go live | May not require developer time. | |
2 |
| Must have at go live | Configuration - VMs, print daemon (desktop support not developers) | |
3 |
| Must have at go live | Configuration LTI with DLI; exporting Courses data | |
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)