Between 1 am and 10 am on Thursday, November 22, the catalog will be down for planned maintenance (re-indexing of several fields).
Thanks to the ingenuity of folks on the EZproxy mailing list, a solution was found that fixes the off campus access problem we were having with the DSM-5 Library. I’ve applied that fix to the configuration file on our EZproxy server and tested that it works.
Some recent changes made by the vendor (American Psychiatric Association) on their end seem to be preventing us (and most other libraries using EZproxy) from connecting to the DSM-5 Library from off campus. On campus access remains unaffected.
I’ll update here as soon as the vendor and OCLC (the vendor for EZproxy) sort this out.
We’ve lost remote access to Factiva due to some unknown technical problem (the vendor, ProQuest, thinks it may either be an issue that our campus IT can help diagnose or that OCLC, the vendor for EZproxy, can figure out).
On campus access to Factiva is working fine, though. I’ll update this blog when we figure out a fix.
All JSTOR customers are having problems accessing content today. See the JSTOR Support account on Twitter for updates.
If someone is reporting that they can’t log in to something, it’s essential to know precisely which system they are having trouble with before you offer any advice. The best strategy is to ask the patron to describe the login screen that they can’t get past. Get the patron to give you answers to one or more of these questions:
What is the web address of the login page that you can’t get past?
If it begins with…
- https://libsearch.cuny.edu, then that person is trying to log into their library account via the library catalog (see screenshot at bottom of this post)
- https://cuny-pds-lb.hosted.exlibrisgroup.com or with https://onesearch.cuny.edu, then that person is trying to log into their library account via OneSearch (see screenshot at bottom of this post)
- http://remote.baruch.cuny.edu, then that person is trying to log into a database or some other licensed resource (see screenshot at bottom of this post)
- words that sound like some database we subscribe to, then they may be trying to access content we haven’t subscribed to or they may be off campus trying go directly to a database instead of going via our links on the library website
- http://guides.newman.baruch.cuny.edu/er, then that person is trying to log into a course page in the e-reserves system (see screenshot at bottom of this post)
Can you describe the login page? What words do you see on it?
- Some patrons won’t be able to provide you with the web address of the login page, so a good strategy to try next is to ask them to describe as much of the page as they can
- If the patron says the page mentions a “library ID #” or “barcode” then it is likely they are trying to log into their library account via the library catalog or OneSearch (see screenshots at bottom of this post)
- If the patron says the page has the “Baruch College” logo on it and asks for a “Baruch Username” and “Baruch Password,” then they are on our remote access page (see screenshot at bottom of this post)
- If the patron says the page has the course number and course name and is asking for a “course password,” then they are in the e-reserves system trying to log into a course page. (see screenshot at bottom of this post)
In another blog post, I’ll outline what advice to offer based on what system is a problem for the patron.
Screenshots of login pages
Remote Access (also known as EZproxy and the proxy server)
E-Reserves Course Page in the LibGuides System
Date and Time
Saturday, 20 January 2018, 1 pm – 7 pm.
This downtime had previously been announced for January 27-28 but was moved to January 20.
Affected Services and Resources
- All databases on the ProQuest platform
The November 2017 update of the Primo software has fixed the problem we were seeing with searches run in OneSearch by users in the Firefox browser (see this October 6 blog post for details).
Users from off campus can now connect to S&P NetAdvantage again. As I had suspected, the settings from S&P had changed with no notification from them and required me to tinker with the settings in our EZproxy server.