Allow Primo Research Assistant proxy definition to be determined by electronic collection's service
Currently, there is only one proxy definition allowed for the electronic services in Primo Research Assistant, but a one-size-fits-all approach is not sufficient for our needs. Alma allows for multiple proxy definitions to be used with electronic services, as they are configured in each electronic collection's service editor. We currently use 3 different definitions: 1) OpenAthens Redirector, 2) OpenAthens Proxy, and 3) no proxy. Please mirror this functionality in PRA so that we can create the correct links for all of our electronic services.
Blake Galbreath
shared this idea
-
Dmitriy Makuha commented
We ran into a similar configuration hurdle last semester while trying to bridge our institutional library software with external discovery APIs. The default system setup kept trying to route all research traffic through a single internal gateway, which triggered security blocks on the publisher's end due to the volume of requests. To keep our research automation working without constant script timeouts, we had to isolate our query routing by configuring dedicated endpoints from https://proxy-solutions.net/en . Having native, flexible controls to define separate routing paths for AI assistants directly within the platform would save a lot of backend troubleshooting.