fix Primo's proxying functionality so it can handle encoding
Propose a solution to this problem: When people try to access content from Primo to Artstor, they are being authenticated into our proxy. After initial authentication into proxy, patrons are not linked to the Artstor result; they are shown an error page (Artstor error), or a generic Artstor resource page--not the actual result. Now that they are logged into the proxy, if they try to access the same link from Primo again, they can get to the result in Artstor properly.
1
vote
Jenn Brown
shared this idea