Integration with Polaris and eContent Vendors

Libraries can implement integration between Polaris and the following eContent vendor applications:

After a library subscribes to one of these eContent applications and configures Polaris to enable the integration, patrons can search for, place holds on, and check out a vendor's eContent directly from the PAC.

For eContent integration where item records are created as part of the import process, the associated circulation processing and tracking for integrated eContent occurs in Polaris. For RBdigital integration where no item records are created in Polaris, checkouts from the PAC are logged, but not checkouts from the RBdigital application. Although Polaris logs statistics, the eContent vendor is the source of the most accurate and timely circulation data.

The eContent products cloudLibrary and Axis 360 use Polaris API (PAPI) authentication, defined in Patron initiated circulation rules. For these vendors, Polaris requires an SSL certificate for PAPI server security. OverDrive and RBdigital use SIP authentication, defined in Polaris SIP authentication rules. Since authentication takes place via SIP and not PAPI, SSL is not required.

Note: Your library can choose to configure Axis 360 to use SIP authentication instead of PAPI.

When an integrated eContent vendor’s bibliographic records are imported in Polaris, a resource entity is automatically created for each 856 tag. A resource entity is a group of fields that collectively identifies the eContent vendor, the library’s account with the vendor, and the specific electronic resource in the vendor’s repository.

The following components are required for implementing eContent integration with Polaris:

Tip:
The integrated vendor record is visible in Polaris Administration only if the library has a license for that vendor.

Important:
For OverDrive and cloudLibrary, newly-purchased eContent records are imported automatically using the import profile selected in the Vendor Account workform. Newly-purchased RBdigital titles are automatically imported as part of the overnight sync processes. Your library can copy and rename the Integrated ebook Bibs profile, but the renamed profile must be selected in the Vendor Account workform.

Your library may also implement the following optional Polaris records and settings:

  • Patron initiated circulation: Transaction branch profile - You can change the transaction branch setting from Patron’s branch (the default) to Item’s branch in the Patron Services profile to track eContent circulation transactions from the PAC separately from check outs and holds for physical items. See Set the loaning branch for eContent circulations.
  • Check-out: Require format selection when checking out integrated eContent parameter - When this parameter is set to Yes for the library organization the patron is connected to in the PAC, the patron must select the format when checking out eContent titles. See Require format for integrated eContent check outs in PAC.

Note:
By default, integrated eContent titles are not included in patron notices. Polaris administrators can change this setting on the Reminder tab of the Notification options dialog box. See Setting Up E-mail Reminder Notices.

See also: