Upgrade StorageSummon/PRIMO "An error occurred saving with Primo 2018..."
We have had issues with saving to Zotero from Primo since we first converted to Primo several years ago. I have read through the other threads on this topic, and it seems that this issue was thought to be fixed as recently as last year. However, it is still happening for us. Here is a link to a record that demonstrates the error:
https://tamucc.userservices.exlibrisgroup.com/discovery/openurl?institution=01TEXAM_COR&rfr_id=info:sid/summon&rft_dat=ie=2145184410005591,language=EN&svc_dat=CTO&u.ignore_date_coverage=true&vid=01TEXAM_COR:Services&Force_direct=false
Since apparently this is fixed for some at this point, is there anything we can do to correct it for our instance of Summon?
https://tamucc.userservices.exlibrisgroup.com/discovery/openurl?institution=01TEXAM_COR&rfr_id=info:sid/summon&rft_dat=ie=2145184410005591,language=EN&svc_dat=CTO&u.ignore_date_coverage=true&vid=01TEXAM_COR:Services&Force_direct=false
Since apparently this is fixed for some at this point, is there anything we can do to correct it for our instance of Summon?
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
.urlToXmlPnxand that produces a 400 (Bad request), including when I'm trying it straight in the browser. I'd take this up with ExLibris support -- this would seem like their bug in your version of the hosted Primo, not your Summon instance.