About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:overdrive

OverDrive Configuration

VuFind® can integrate with the OverDrive service. To set it up, see the notes/comments in Overdrive.ini.

The functionality was added by pull request #1188.

Features

  • Support for both MARC and OverDrive record formats
  • Real-time availability using AJAX
  • OverDrive Patron Eligibility Check
  • Place/Cancel Holds
  • Previews (samples)
  • Checkouts/Early Return
  • Download Content
  • Account page shows holds/checkouts
  • Support for Consortium and Advantage Accounts
  • Adding, editing, removing hold suspensions (VuFind® versions 10.0+)
  • Editing Hold email (VuFind® versions 10.0+)
  • Magazine Issue Checkouts (VuFind® versions 10.0+)

Key

In order to use the OverDrive Integration, you must have an API Key. If you don't already have one, you can request one from the OverDrive developer site. You should tell them that you are planning on using “VuFind® with OverDrive Integration”. This should allow you to get a production key instead of “integration” (i.e. testing) access.

Indexing

OverDrive records will need to be imported into VuFind®, either by importing records straight from OverDrive or from your ILS using your normal import method. In either case, the OverDrive records have to be marked in Solr as record_format “overdrive” (lowercase). If using MARC records the OverDrive configuration file needs to be edited to indicate what field the OverDrive ID is in. If not using marc import, then the id of the record in Solr should be the OverDrive ID.

Note: I've also made the assumption that the OverDrive ID for the title is in the MARC record somewhere. I'm pretty sure it always is if you get your MARC records from OD. If you add the ID into an ILS catalog record, note that an Overdrive record contains several different IDs, and the one you need is the long UUID called either “id” or “reserveId”, not the shorter “titleId”.

If importing straight from OverDrive it is highly recommended to use the Record Manager. It does not have built-in support for OverDrive records, but if you email the list, I can provide something to get you started.

Architecture

The OverDrive feature is made up of 4 main components in addition to a handful of templates. The OverDrive Connector is the main piece that handles all of the calls to the OverDrive API. The record driver is a thin layer on top of the SolrMarc record driver hierarchy and just adds a little bit of logic for non-MARC based record information. The OverDrive Controller mostly just handles requests from the “action” buttons (placing and canceling holds, checking and returning titles out) and for the user account page.

Troubleshooting

Admin Page

There is a troubleshooting page in the admin module that you can use to check whether the integration is connecting to the OverDrive API correctly.

Log Files

The basic log file is going to be the most helpful in troubleshooting. If something isn't working, there will likely be a message in there somewhere.

VuFind® Users list

As always, if you get stuck or if you want to request a new feature, posting to the vufind-general users list is a good idea.

configuration/overdrive.txt · Last modified: 2024/06/01 19:21 by demiankatz