...
Project Board | |
|---|---|
Start Date | Sprint zero |
Current Sprint | Sprint #8 20 May #10 - 31 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. Functionality to include name suffix is done. Incremental can add/update; drop has been developed but not yet tested. EN 29 May 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 |
Running a final full test load which is expected to complete on Wed June 5th.
| JB 29 May Loading data to the TRLN SOLR index is underway. 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 30 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 | 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 Designing solution for users to run on demand by selecting a file to ingest. JB 29 May | ||
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 29 May We have remaining jiras, but will be acceptable to go live with what is currently implemented. 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 29 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 | ||
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 29 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). |
...