...
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 22 | ||
2 | Must have at go live |
|
JB | ||
3 | Must have at go live |
| Began user training with Law, Ford, and DUL users this week. Identified unexpected behavior with the prorata checkbox and publishing of invoice lines - if special charges such as shipping are listed as invoice lines AND the prorata checkbox on the invoice summary is turned on, those lines will not be included in the export to AP. Will handle through user training and a new error condition. Provided another set of test files to Duke AP for review JB | ||
4 | Must have at go live | Can use code from Harvard as a start | Making progress! Unit testing of invoice creating is underway - the app is sucessfully generating an invoice with lines. Need to change the invoice date value from current date to the invoice date provided in the vendor file. JB | ||
5 | Must have at go live |
| 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. Integration with AEON (for SCL/ARCH holdings) is complete, and integration with ILLiad (for ILR and scan and deliver) is complete. A volunteer external to the library is almost complete in has completed rigorous testing of the CRS with major patron groups and reporting results for adjustments. EN 22 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 | ||
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 22 | ||
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). |
...