...
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. 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 |
| Restarted load to pickup bound-with records. JB | ||
3 | Must have at go live |
| Initial user training complete. Send another round of files to Duke AP for additional validation. Last set were formatted correctly and were ingested into the SAP R/4 test system. 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 | Initial testing successful - would like to coordinate additional test runs with MADS. 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 |
| 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 |
| 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-6-2024. EN 05 | 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 | |||
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 | Developer is actively working toward generating a file by 6/7/24 so testing can be completed before the file is due to ExLibris by end of day 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 | |||
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). |
...