Discovery Tool Compatibility: ProQuest response

Following are ProQuest's responses to the Discovery Tool Compatibility questionnaire.

  1. Does this product conform with the Open Discovery Initiative recommendations set by section 3.2 of NISO RP-19-2014? ( If not, please specify which parts the product does not conform with, and why.

Response:  PQ: Section 3.2 contains the recommendations for content providers.  In this case, ProQuest as a content provider for CBCA and Newsstream.  We have responded from that perspective, with added notes regarding ProQuest as a provider of discovery services Summon and Primo.

ProQuest conforms completely with many of the recommendations of ODI.  ProQuest staff, as well as staff from Ex Libris, now a business unit of ProQuest, participated in the development of the recommendations. 

 We conform with the following recommendations:

3.2.1 Metadata Elements Provided to Discovery Services General Requirements

1. Generally conform.  ProQuest sends full text, as well as metadata to Summon, Primo and Google Scholar.  At the moment, we do not send the underlying full-text/original text to OCLC. We are in negotiations with them to change that in the future, though.

2. Generally conform, although we do not send Open Access Designation for all records – we do send all other metadata elements. Our metadata structure is not currently in a format that allows us to send this data to discovery services, but we are currently working on a project to change that.

Regarding ProQuest discovery services, note that our Summon discovery service now displays open access indicators for more than 200 million documents, with more being added.  We have actually created a Basecamp to allow interested librarians to participate in our gathering of open access content.  Notes from the Summon release in May 2017 where this feature was made available:

We now have detailed Documentation available in the Central Knowledge Center related to the Open Access features.  Here is a link to the documentation for these features:   (

This documentation not only describes how to activate the new features but also includes important information about how we have defined Open Access to-date, how the feature works, limitations related to filtering and linking, and most importantly how you can help improve these features.  The documentation also provides a link to a list of content sources which are currently flagged as Open Access in Summon.  With this release, libraries now have a choice of activating an Open Access filter (similar to a peer review or full text online filter), an Open Access indicator that displays inline with records, or both.

We currently have more than 200 million items flagged as Open Access across a variety of content types and from a variety of sources including books, journal articles, images, technical reports and other open content repositories as well as open access articles in subscription databases. 

Note that all Summon, Primo and Ex Libris documentation is openly available without user name and password at

3. Conform, except for what was mentioned in above. Core Metadata

Conform, except for what was mentioned in Enriched Content

Conform, except for what was mentioned in above.

3.2.2 Metadata Elements Provided by Content Providers to Libraries

We are happy to disclose the information about the level of participation for any of our products in discovery services to any libraries that request this information, but we do not have this information readily nor publicly available.

3.2.3 Disclosure


3.2.4 Technical Formats

As the standard suggests, efficient transmission of large files is important.  We format our data in a way that can be ingested by major discovery services, and adapt our data feed to the needs of each discovery solution.

Please note that ProQuest discovery services, Summon and Primo, both support data ingest from OAI-PMH and KBART.

  1. Does ProQuest provide the same metadata for this product equally to all discovery tools, regardless of their producer?

Response:  ProQuest would be pleased to supply the same metadata and full text to all discovery providers.  At the moment we provide both metadata and full text to Summon, Primo and Google Scholar, but only provide metadata to OCLC. Additionally, the databases that are sent to each discovery service varies per agreement with those services. Both databases are available in Summon (everything) and OCLC (metadata only), but Canadian Newsstream is not available in Primo nor Google Scholar as neither services were interested in News content when the agreements were first signed, although we can confirm that Primo is reconsidering their position on this.

  1. Please address whether the records in this product are equally discoverable by all of the discovery tools used currently by the BC post-secondary sector (EBSCO Discovery Service, Primo, Summon, WorldCat Discovery).

Response:  ProQuest does not currently have an agreement with EBSCO.  We would like very much to have such an agreement, and there have been discussions between Ebsco and ProQuest.  So far, we have not been able to reach a mutually acceptable arrangement.  So, we do not currently send our metadata to them, although they have ways to search and retrieve ProQuest content within EDS through other tools.

Within the ProQuest discovery services, we also have tools for accessing Ebsco content, even though we do not have an exchange agreement. 

  1. If they are not equally discoverable, what methods are available to enable maximum discovery of this content using each individual library’s chosen discovery infrastructure?

Response:  As mentioned above, EDS has a feature that enables libraries to search content that has not been indexed in EDS through federated search. OCLC has all the metadata and indexing and this content is readily discoverable, even if the full text cannot be searched at this stage.

Within the ProQuest discovery services, we have reached out to publishers directly to get the metadata and full text for much of the content in Ebsco aggregated databases.  The library can then set the preferences in its link resolver to point at the Ebsco databases.

Add new comment