Why do some remote databases show a result count in WorldCat Discovery while others don't?
Symptom
- When a search includes remote databases, some databases in the remote database preview drawer show an approximate number of matches and others show no number.
- Databases without a count appear under the heading "Visit these additional databases to view content that might match your search terms" instead of "Relevant matches exist in additional databases."
- Users may also see one of these messages:
- "Unable to retrieve results. Visit database to view results"
- "See additional databases. No results found."
Applies to
- WorldCat Discovery
- Remote databases from EBSCO and ProQuest
- OCLC Service Configuration
Cause:
Remote databases aren't part of the WorldCat Discovery central index. Their metadata stays on the provider's platform. For each search, Discovery sends the query live to the provider and asks for an approximate result count. Discovery then groups each database in the preview drawer by how the provider responded:

A database with no count failed to respond. Common reasons are wrong or outdated credentials, a missing or wrong proxy URL, provider-side settings (such as EBSCO databases still set up for Z39.50 instead of the EIT Web Service), a timeout, or a search index the provider doesn't support remotely.
Resolution
- Check the remote database credentials
- Sign in to OCLC Service Configuration.
- Go to Metasearch Content > Default Databases and Licensed Content > Configure Databases to Search.
- On the Remote Databases tab, check the Username and Password for the affected database. Correct them if needed and click Save.
- If you aren't sure the credentials are correct, confirm them with the database provider.
- Check the proxy URL
On the same Remote Databases tab, make sure the proxy Base URL is present and correct.
- For EBSCO databases, check the EBSCOadmin setup
- In EBSCOadmin, make sure you are working in the main group.
- Go to Customize Services > Profile Maintenance > Add a New Profile. Enter a Profile ID, choose Web Service from the drop-down and click Submit.
- Under Customize Services, turn on each database you want to search from WorldCat Discovery.
- In OCLC Service Configuration, enter the username as [EBSCO site ID].main.[EBSCO profile ID].
- If you subscribe to any "Source" databases, the current and retrospective versions must be set up separately and turned on in both EBSCO and OCLC.
- If an expected database isn't in the EBSCO list, contact EBSCO to have it added.
Narrow down the pattern
-
- The database never shows a count, for any search: the cause is most likely configuration (credentials, proxy or EBSCOadmin). Repeat steps 1–3.
- A count is missing only for some searches: the cause is more likely a provider timeout or a search index the provider doesn't support over the remote connection. This is expected behavior. Users can click the database box to run the search on the provider's own platform.
- If the problem continues
- Ask the provider to confirm that remote access is turned on for your subscription.
- Then contact OCLC Support.
Additional information
- Search the Central Index and Remote Databases in WorldCat Discovery
- Why am I getting an error message instead of additional database recommendations when searching remote databases in WorldCat Discovery?
- EBSCO has provided instructions and a new method of accessing their remote databases from within Discovery
- FAQ: Database recommendation feature in WorldCat Discovery (PDF)
