Differences

This shows you the differences between two versions of the page.

--- configuration:overdrive [2019/06/11 12:32] – [Indexing] demiankatz
+++ configuration:overdrive [2019/06/13 19:26] – [Troubleshooting] bpalme
@@ Line 17: / Line 17: @@
 ===== 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 [[https://developer.overdrive.com/docs/getting-started|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 an "integration" (testing) access.
+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 [[https://developer.overdrive.com/docs/getting-started|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 =====
-You will need to import your Overdrive records into Vufind, either by importing records straight from Overdrive or from your ILS using your normal import method.  If importing from your ILS, you can either import all your records or just the Overdrive records but the only caveat is that the Overdrive records have to be marked as  type "overdrive" (lowercase).  If using MARC records you need to edit the Overdrive configuration file to designate that. 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.
+You will need to import your Overdrive records 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 as  type "overdrive" (lowercase).  If using MARC records you need to edit the Overdrive configuration file to designate that. 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 importing straight from Overdrive I highly recommend using the [[https://github.com/NatLibFi/RecordManager|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.
   * [[https://github.com/vufind-org/vufind/blob/master/config/vufind/Overdrive.ini|Configuration File]]
   * [[https://github.com/vufind-org/vufind/blob/master/module/VuFind/src/VuFind/DigitalContent/OverdriveConnector.php|Overdrive Connector]]
@@ Line 31: / Line 33: @@
   * Templates
 ===== Troubleshooting =====
-  * Log Files
-  * Admin Page
+==== Admin Page ====
-  * Vufind Users list
+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.  The Overdrive components put out quite a bit of logging at the debug level.
+==== Vufind Users list ====
+As always, if you get stuck, posting to the [[https://sourceforge.net/projects/vufind/lists/vufind-general|vufind general]] users list is a good idea.
 ---- struct data ----
 ----