Implementing the cloudLink Feature

Libraries using the cloudLibrary eContent service can implement Bibliotheca's cloudLink feature whereby libraries in a cloudLink group can share digital collections across multiple cloudLibrary accounts. Bibliotheca's cloudLink groups are ILS-independent and can be used to connect existing cloudLibrary customers on different systems, usually based on geographic location. The Polaris integration can also support a "self-contained" cloud, where all libraries in the cloudLink group are on the same Polaris server.

To ensure that patron check-outs and requests appear under a single library when resources are being shared via cloudLink, use the Preferred Vendor Accounts policy table.

Note:
Existing cloudLibrary customers who are not using the cloudLink feature do not need to use the Preferred Vendor Accounts policy table. However, all cloudLink customers should use the policy table to provide the best patron experience.

Circulation Transactions for cloudLink Titles

When cloudLibrary titles are checked out through the PAC, Polaris uses the Item Library ID returned in the cloudLibrary API to associate the correct item record with the patron. For cloudLink libraries, one of two transaction types can be logged:

If the item belongs to a library that exists in the Polaris database, a normal check-out transaction is logged.
If the item does not belong to a library within the Polaris database, a new eContent check-out (6103) transaction is logged. This is different from a normal check-out transaction because there is no item record associated with the transaction. In addition, the following message appears: Your ebook has been successfully checked out. To provide faster access, this ebook was borrowed from a partner library. Please use your cloudLibrary reader to download or view this title.