Export Formats for the BookMetaHub

Export Formats for the BookMetaHub

Export Content via XML Files


After successful import, creation, or enhancement of your book and chapter metadata, you can freely download all content to share with other third-party content aggregators.


HowTo export content via BITS or Crossref-compatible XML on the record-level:


On all record pages (books and chapters) on the BookMetaHub you will find a →Download button. Just click the button, and select your preferred →export format. Supported in the system are BITS XMLs and Crossref XML.


BookMetaHub: Export data via our open API


We are happy to announce that the BookMetaHub now operates an OAI-PMH service for the distribution of metadata in XML.


This system is based on the OAI-PMH version 2 repository framework and implements the interface as documented here:



We support selective harvesting according to sets defined by the Publisher’s Workspaces available on BookMetaHub. To list all available sets, go to:



Please note that the from and until dates in a request capture when a record was imported to OAI database and are not referring to the publishing dates of the item.

This means a request of records with dates defined e.g. 2022-01-01 to 2022-12-31 will return all records that were created or updated within the hub throughout the year of 2022, regardless of the publication dates included in the records.


With the ListIdentifiers (ListRecords) request the set, from, and until parameters are optional.


Examples of requests:


Request a list of records from Masaryk University Press set (Workspace):



Request a list of all records imported since 2022-12-01:



Many OAI requests are too big to be retrieved in a single transaction.

If a given response contains a resumption token like this:

<resumptionToken expirationDate=”2022-12-12T12:19:04Z” completeListSize=”705″ cursor=”10″>a8f7db4c-31cf-413c-8710-e13c8d845c6f</resumptionToken>

you must make an additional request to retrieve the rest of the data.

The token should be appended to the end of the next request: