Configure third-party connections

You can configure Vega to connect and communicate with the following third-party applications:

  • Axis 360
  • BorrowBox
  • cloudLibrary
  • Content Café
  • Google Books
  • Hoopla
  • OverDrive
  • PayPal Payflow or other payment system
  • Syndetics Classic
  • Syndetics Unbound
  • Econtent vendors (See Configure econtent management.)

For information on administration of third-party accounts, contact the provider.

Note: Vega uses either Google Books, Syndetics Classic, Syndetics Unbound, or Content Café to display book covers. If you enable one, Vega automatically disables the others. By default, Vega uses Google Books.

If you enable Syndetics Classic, Vega also displays author biographical information (if available) on the Person page. If you enable Syndetics Unbound, Vega displays the following:

  • Book covers
  • Author biographical information and author images on the Person page
  • Showcases that include persons and bookmarked authors on My Bookshelf

Important

You can configure econtent APIs for Axis 360, cloudLibrary, BorrowBox, Hoopla, and OverDrive to load econtent records directly into the Vega context engine instead of manually loading and cataloging the records in your ILS. For more information, see Configure econtent management.

In phase one of implementing this feature, we recommend that you use a vendor’s API to provide records directly to Vega only if you are comfortable with the following:

  • Loading the entire subscription into your Vega Discover context engine.
  • Note that the Hoopla catalog contains over 1.5 million records.

  • The level of cataloging detail provided by the vendor.

Loaded records cannot be individually updated like they can in the ILS. Some titles may not roll up with works based on vendor-provided data.

  • ILS-cataloged copies of matching title IDs from vendor subscriptions will appear instead of the API-ingested record.
  • You can use this feature to correct record metadata.
  • You don't need to delete your current ILS econtent records before you load records via the APIs, and you can take your time to remove ILS copies of econtent records.

Before you configure third-party connections for econtent vendors such as OverDrive, Hoopla, cloudLibrary, Axis 360, and BorrowBox, you must configure econtent mapping. For more information, see Configure econtent mapping.

About collection site-level payment configuration

If your library uses a single payment account across all branches or collection sites for processing patron fine payments, you should configure fine payment at the Vega Discover level. If any branches or collection sites use a separate payment account for processing patron fine payments, you can configure that fine payment account at the consortia collection site- or kiosk-level.

If there is no consortia collection site- or kiosk-level fine payment configuration, the collection sites or kiosks use the Vega Discover-level fine payment account.

Delete a third-party connection

You can delete all third-party connections except Google Books.

See also