Integrating to library tools

Library tools often come with a knowledge base provided by the sotfware vendor. For example, ProQuest’s services are backed by the 360 CORE KB. It is possible that such knowledge bases include metadata related to OpenEdition’s catalogue. Yet, you may want to manually setup your ILP to import and update its data straight from BACON.

In order to do so, the steps to follow depend on the tool you’re using. Most of the time, you should be looking for menus called Electronic Resources Management (ERM) or Holdings Management. You should be able to add a custom source for your resources, or as it is sometimes called, set up a locally-managed holdings database.

Extensive documentation on how to perform these operations is provided by ProQuest for 360 CORE, and for Primo, and by EBSCO for EBSCO Admin. If needed, you should ask your library software provider for support.

Note

As a complement, this slideshow from a conference at JABES 2016 (in French) describes a BACON-based workflow for updating electronic collections.