EBSCO has provided instructions and a new method of accessing their remote databases from within Discovery
Symptom
-
EBSCO has provided new instructions and a new method of accessing their remote databases from within Discovery.
Applies to
- WMS Discovery
Symptom
Our library uses the remote database service in Discovery but noticed lately the results were lacking or erratic for some of the EBSCO databases. I contacted EBSCO for advice, and they agreed something was wrong. Although they previously recommended a Z39.50 method of connecting, they decided to change this feature into an EIT Web Service, intended to work as an integration service.
Resolution
Check EBSCO's updated configuration for EBSCO when accessing remote databases from within Discovery.
EBSCO suggested I change the links in the OCLC Config file for Metasearch Content > Default Databases > Remote Databases, to update the Username to
[your library’s EBSCO code].main.wcd-eit and the Password can remain the same.
They also suggested going into EBSCOadmin and:
-Make sure you are using the main group (in the upper right, above the color band)
-Under the Customize Services tab, click on Profile Maintenance (to the right of “choose profile”)
-Click Add a New Profile
-type in a Profile ID you will recognize
-type in a description, and in the dropdown menu, select “Web Service”
-Click submit
-Under the Customize Services tab, enable the relevant databases you will want to search via Discovery.
The Databases selected at EBSCO's list have to be activated already, and if you subscribe to any of the “Source” databases, you have to have them separated out to the current and retrospective versions, and enable each version at both EBSCO and OCLC. If you do not see your expected databases in the list, contact EBSCO to have them activate them on the list.
We are now finding the EBSCO Remote Database is working well and returning results consistently in Discovery.