Table of Contents

Batch Mode: Sideloading and Exporting Titles in Batches

If you are working on multiple titles you can use batch mode to sideload titles or export titles in batches. This feature has been created to save time, especially if you are working on a remediation project.

To use Batch Mode for Sideloading:

To use Batch Mode for Exporting Titles:

If you realize you need to change something in a title after you added it to an export batch, you can still do this before you execute jobs. If you need to make changes to a book after you select execute jobs, you must export the project again.
If you upload a file from your computer in Batch Mode the file is added to your import list. When you import, it is then added to the queue for Batch Mode.
When you import a book in batch mode, there is no link to open the project, since the project isn't imported until the batch is processed. Instead, there is a link back to the Add a Book page.
You can use OverDrive metadata during Batch Mode. You can turn this function on in your Account Settings.

The following video is a tutorial on How to Use Batch Mode to Sideload and Export Multiple Titles:

Errors in Batch Mode

During Batch Mode, if there were any errors, the error will be listed followed by an Okay button. When this happens, do the following:

The following sections will tell you how to manage and report different types of common errors in Batch Mode.

If the you receive and error that is not covered below, please email the Production Coordinator with the error message, title, and steps that lead to the error.

Common Errors and Solutions

In this section, you will find two common errors that can be fixed on the user end, as well as what to do if you get stuck in Batch Mode. You do not need to email the Production Coordinator when you get these errors.

If the error is Cannot find record. Confirm the URL is to the book record page. do the following:

The following is a video for how to deal with the Cannot find record Error:

If the error is # MP3 versions found. Please use the direct download URL to add this book do the following:

The following is a tutorial on how to deal with the # MP3 Version found Error:

If the error is: Error: Failure, the server said: NoSuchKeyThe specified key does not exist (followed by directory and file name) do the following:

If there are any other error messages that have an Okay button that are not listed above report this issue to the Production Coordinator. Please make sure to include the title and error message.
The most recent listing of errors is available to the Developer. If you dismiss the errors and realize you missed making note, report the issue to the Production Coordinator before running another batch.

When Batch Mode Gets Stuck

If there is an error that causes Batch Mode to get stuck, or the batch pauses for more than 2 minutes, please do the following:

The following video is a tutorial on How to Restart a Failed Batch:

.

How to Report a Stuck Job: If Cancel Button Does Not Work

When there is an error in Batch Mode, or the batch pauses for more than 2 minutes, and you can not get the Cancel button to work, you can report the issue using the Report Stuck Job link after the Cancel button.

The Production Coordinator and Developer will let you know as soon as the error is fixed and when you will be able to restart your work. Please do not work in COP until you have been contacted with confirmation the error is fixed.

All issues will be worked on in order of submission. It can take 48-72 hours to fix an issue depending on when it is submitted. The Production Coordinator and the Developer will contact you once the issue is resolved.

The following video is a tutorial on Report a Stuck Job: