...
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 but not yet tested. Incremental can add/update; drop has been developed but not been implemented yet tested. EN 08 | ||
2 | Must have at go live |
|
| ||
3 | Must have at go live |
| Unit testing is underway for error handling and setting error invoices as “Rejected” after export. Will run a fresh load of test data to send to Duke AP for validation. JB | ||
4 | Must have at go live | Can use code from Harvard as a start | User stories are in the current sprint, but haven’t started development yet while completing other user stories. JB | ||
5 | Must have at go live |
| My Accounts is complete. Work is ongoing on viewing item lists and placing requests. We’ve made significant progress in handling various display use cases (claim returned, transit, etc.) Working on an approach to handling records with large numbers of items to address performance. Testing and debugging continuesA volunteer external to the library is engaging in rigorous testing of the CRS with major patron groups and reporting results for adjustments. EN 08 | ||
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. Tom C. provided an update at May First Wednesday ( First Wednesday 2024) EN 08 | ||
8 | Must have at go live |
| Developer resources have been found; first meeting will be afternoon of May 9th. 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 | 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. 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). |
...