...
Priority # | Title | Jira Epic | Importance | Notes | Status | |||||
|---|---|---|---|---|---|---|---|---|---|---|
1 | Must have before go live |
| File retrievals are running as expected. Next steps are to run a full synchronization to see how long it takes. Incremental can add/update; drop has not been implemented yet. EN | |||||||
2 | AI-28: TRLN Discovery/POD/Summon IntegrationTO DOIntegration | Must have at go live |
| Instance of TRLN Discovery is running locally, extracts from Alma can be done. Work ongoing on putting all the pieces together 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 |
| Data mapping is complete, file can be sent to Accounts Payable. Early May, AP will review our file. Work is ongoing on reporting and Alma to AP data flow. KHN 17 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 | AI-41: Invoice Creation from Vendor MARC RecordsTO DORecords | Must have at go live | Can use code from Harvard as a start | Meeting planned Started intial review of this integration on 4/22/24. Communicating with Harvard staff involved with this integration to share helpful tipsKHN 17 a request to review their code and also reviewing acquisitions APIs. JB | ||||||
5 | Must have at go live |
| Patron information, loans, fees and fines information is available. Work is ongoing on viewing item lists and placing requests. Work to differentiate title versus item is complete. AEON redirects as expected. Testing and debugging continues. EN | |||||||
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 | |||||||
8 | Must have at go live |
| Requirements are complete; waiting for developer capacity. EN | |||||||
9 | Must have at go live | or at least by early August | ||||||||
10 | Must have at go live | tied to TRLN Discovery project | ||||||||
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. | ||||||||
1213 |
| Post go live | Would need to adjust the landing page if not at go live | |||||||
1314 | Migrate FOLIO ERM Organizations Contacts and Interfaces to Alma |
| Post go live | May not require developer resources, maybe Postman | ||||||
1415 |
| Post go live | Connection to DSC for item history | 15 |
| Post go live | Coding mostly done, working on some tweaks based on data review |
These will likely not require developers, but may require desktop support or assistance from Learning Innovation:
...