Skip to main content
OCLC Support

WorldCat Discovery release notes, 12 February 2025

 

Release Date: February 12, 2025

Introduction

This release of WorldCat Discovery includes the following enhancements as well as bug fixes:

  • Refine searches with additional filters for more precise results using the redesigned advanced search preview

Many of these enhancements are the direct result of your feedback.

New features and enhancements

Refine searches with additional filters for more precise results using the redesigned advanced search preview

The latest update to the redesigned advanced search preview includes new filtering options for format, content types, audience, and language

Screenshot 2025-02-03 at 9.22.24 AM.pngA key enhancement now allows users to select multiple values for format, content types, and languages simultaneously, providing greater flexibility in refining search results.

Screenshot 2025-02-03 at 2.55.49 PM.png

Screenshot 2025-02-03 at 2.56.08 PM.png

Screenshot 2025-02-03 at 2.56.20 PM.png

Additionally, four filters for searching the central index—including record type, record status, document type, and abstract indicator—offer even more precise search refinement. 

Screenshot 2025-02-04 at 4.29.36 PM.png

Note: The available filters depend on the selected databases. Some filtering options may not appear if the chosen databases do not support the corresponding indexes.


These updates apply only to the redesigned advanced search preview and do not impact the current advanced search experience. To explore the preview and get a custom link for your institution, visit the Advanced Search Preview page for Early Adopters in the Community Center
 

Important links

Product website

More product information can be found here.

Support website(s)

Support information for this product and related products can be found at:

Include Request ID with problem reports

When reporting an issue with WorldCat Discovery, it is extremely helpful to include the Request ID. The Request ID is found at the bottom of the screen on which the issue occurred. Including this information allows us to directly trace what happened on the request we are troubleshooting.

requestID.png