Configuring ILLiad as a Lending and Borrowing Partner
Reference urls: https://github.com/kurtmunson/ILLiad-NCIP
Background
In late Spring 2025, we decided to prioritize integrating Alma and ILLiad to help with workflow management and decreases in staffing.
There are three basic parts to this:
Set up ILLiad so that Duke requests that can’t be filled can be converted to resource borrowing requests and sent to ILLiad as a partner of last resort;
Set up ILLiad so that ILLiad-born OCLC borrowing requests can be sent to Alma and managed there for patrons, in a similar fashion to how patrons manage BorrowDirect and TRLNDirect requests
Convert ILLiad usernames from netid@duke.edu to netid to match the Alma primary identifier.
#3 above has to be done by OCLC and Michael Edwards is working with the OCLC concierge service to make that happen, as it must be in place in order for 1 and 2 to work as expected.
Configuration
As of June 2025, we are working on testing this with configuration on the Alma sandbox connecting to ILLiad production.
We need to have a resource sharing partner configured that would probably handle both #1 and #2 - it’s possible though that we might have two partners, one that handles #2 and then one that handles #1, depending on how we understand the behavior of it once we start testing.