...
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 | ||
2 | Must have at go live |
| Extracts from Alma are operational. Currently populating a crosswalk index of record identifiers to support item availability lookup. Working toward end-to-end data flow so testers can view Alma data in a local TRLN Discovery instance. | ||
3 | Must have at go live |
| Ready to submit test files to Duke AP - they aren’t available until early May for validation. Work continues on reporting and error handling 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 | ||
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 24 Apr | ||
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. Work will be discussed at 5-1 First Wednesday. EN 24 Apr . Tom C. provided an update at May First Wednesday ( First Wednesday 2024) EN | ||
8 | Must have at go live |
| Requirements are complete; waiting for developer capacity. EN 24 Apr | ||
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 | 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 | |||
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). |
...