Looks like EDS is maybe working again on their end? Although I'm still having trouble on my dev machine.
I have made sure at least basic logging of failed searches appears in the Rails logs, avail from heroku. For instance, here is an example:
Error fetching results for `articles`: {:query=>"hours", :per_page=>6}: {:exception=>#<BentoSearch::EdsEngine::EdsCommException: Could not get auth>, :http_status=>404, :http_body=>"{\"success\": false, \"errors\": [{ \"message\": \"\", \"code\": 404}]}"}
Doesn't tell you exactly what's going on, but does give you a hint that an HTTP 404 "Not Found" was encountered when interacting with EDS, trying to get 'auth', for the 'articles' search. Which in this case is at least a clue that the problem is on EDS's end.
If we have time, I can try to add more complete logging, at least for EDS, something you could actually forward to EBSCO support for instance. But for now, just the fact of the error being logged is an advance.
Looks like EDS is maybe working again on their end? Although I'm still having trouble on my dev machine.
I have made sure at least basic logging of failed searches appears in the Rails logs, avail from heroku. For instance, here is an example:
Doesn't tell you exactly what's going on, but does give you a hint that an HTTP 404 "Not Found" was encountered when interacting with EDS, trying to get 'auth', for the 'articles' search. Which in this case is at least a clue that the problem is on EDS's end.
If we have time, I can try to add more complete logging, at least for EDS, something you could actually forward to EBSCO support for instance. But for now, just the fact of the error being logged is an advance.