...
Project Board | |
|---|---|
Start Date | Sprint zero |
Current Sprint | Sprint #6 22 Apr #10 - 03 May |
Target DateDates | - 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. |
...
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. Incremental can add/update; drop has not been implemented yet. EN 01 May Functionality to include name suffix is done. Handling dropped patrons is complete. We have one more Jira to complete. We will be good to go-live with the current implementation EN | ||
2 | Must have at go live |
Continuing to work toward running a full extract so testers can view Alma data in a local TRLN Discovery instance. Defining how to extract and store the # of items on a holding. | Worked through decisions for URL redirect to ensure that existing links to catalog records won’t break once we’re using the new Alma to TRLN data pipeline. JB 02 May Loading data to the TRLN SOLR index is underway. JB | ||
3 | Must have at go live |
| Working on error handling and setting invoices as “Paid” after export. Detail report is complete. Sent sample file to Duke AP on 5/2 and need to change some spacing in the fixed file format. Learned from AP that barcode is required for Law and Perk records only, so need to add that to error handling. JB 02 May Finalizing file names and destination server for sending files to AP in production. 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 02 May Designing solution for users to run on demand by selecting a file to ingest. JB | ||
5 | Must have at go live |
My Accounts is complete. Work is ongoing on viewing item lists and placing requests. AEON redirects as expected. DUL Interlibrary request works as expected; we’ve asked independent library colleagues to test. Working on an approach to handling records with large numbers of items to address performance. Testing and debugging continues. | EN 02 May 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. We have remaining jiras, but will be acceptable to go live with what is currently implemented. EN | ||
6 | Must have at go live | First meeting scheduled with CaiaSoft staff 5/2/2024. | 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) EN 02 | ||
8 | Must have at go live | Requirements are complete; waiting for developer capacity. EN | 02 May Successful test run on June 6th; we are prepared for migrating the final data set during fulfillment cutover. This is complete. EN | ||
9 | Must have at go live | or at least by early August | We’ve begun conversations with the bursar about transitioning to the Alma service output in XML and moving mapping into the data transfer warehouse. EN | ||
10 | Must have at go live | tied to TRLN Discovery project | Work has begun as part of TRLN Discovery work. EN 01 | ||
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 02 May Complete. Files delivered to ExLibris on 6/10/24 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 | As long as the catalog date is in the 946B, this will continue to work without development needed. Metadata Management needs to determine how to include the proper date in the 946B. - EN | ||
14 | Migrate FOLIO ERM Organizations Contacts and Interfaces to Alma | Post go live | FOLIO data was archived to a spreadsheet on 6/27/24 so it will be available to load to Alma post-go live. Development work is not yet underway.
| ||
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). |
...
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 with desktop support client. KHN 17 Apr 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. KHN 01 EN | |
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 17 Apr 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 |
...