4/10/08: Wiley has corrected the problems and access to the Wiley Interscience Journals is restored.

This message is to alert you of an interruption in the online service for Wiley InterScience.

On Wednesday, April 9, 2008, at approximately 12:00 noon U.S. Eastern Daylight Savings Time, the Wiley InterScience server facility experienced technical difficulties. The problem is being addressed and a follow-up notice will go out as soon as access is restored.

At this time, the library does not have an estimated time that the journals will be available again.

On Thursday, January 3, 2008, the library will be upgrading one of its primary data servers. This process will limit access to many of our electronic services, including the proxy authentication table used for off-campus access to our electronic resources. Beginning at midnight on January 3, access to databases and electronic journals will be limited to on-campus computers.

Due to the ongoing problems we are having between the current Web of Science interface and the Libraries’ proxy server, the Web of Science links in the database list and the library catalog are now going to the new Web of Science interface.

If you need access to the old version of Web of Science, it is available to on campus users by using the link http://portal.isiknowledge.com/portal.cgi. Off campus users can only access Web of Science through the new interface.

Journal Citation Reports (JCR) is not yet available on the new interface, so access is limited to on campus users at http://portal.isiknowledge.com/portal.cgi

Users of the EbscoHost databases (Academic Search Premier, Business Source Premier, etc.) may encounter an intermittant “Application Level Exception” error message while using a database. It has been observed to happen when a user attempts to change from one database to another, for example.

This is due to a glitch between the latest upgrade of the Ebsco interface and the proxy authentication software the library users to allow access to electronic resources for off-campus users. They are working to fix this problem. At this time, I don’t know when this will be corrected.