Batch Processing quickly and automatically moves transactions from one processing queue to the next. You can batch process both request and Activity transactions. You can use the standard batch processes or create your own custom batch processes. Batch processing is activated using the Process icon on the Aeon Home ribbon. There are 5 standard batch processes: Check Out, Place on Hold, Reshelve Item, Item Reshelved, and Item Delivered.
Custom batch processes display below the standard batch processes on the Process icon and follow the same processing procedure. Custom batch processes are created in the Customization Manager using the Batch Processing Form. To learn how to create custom batch processes, see Configuring Custom Batch Processing.
Batch Processing Transactions
- Click Process and select the batch processing option you'd like to perform. This opens the Batch Process tab.
- Enter the Transaction Number of the request in the Transaction Number field and hit the Return or Enter key. You can manually enter the numbers or scan the item barcodes.
- Entering the Transaction Number processes the transaction.
- Processed items appear in a grid below the Transaction Number. The Previous Status and New Status columns show that the item has moved to the next queue in the workflow.
When you have finished Batch Processing, close the form by clicking the x to the right of the Batch Process tab.
You need to know the Transaction Numbers of the requests you want to process or scan the barcode in order to use Batch Processing. Along with the Batch Processing form, You can also process requests individually using the content-sensitive menu on the request form.
Process from Clipboard
Batch processing also has an option to process a list of transaction numbers that are copied to the clipboard. Clicking the Process from Clipboard button will send all transaction numbers on the clipboard through the batch update process as described above. Transaction numbers can be separated on the clipboard by all common delimiters including but not limited to commas, semi-colons, pipes, spaces and can be preceded by text e.g. TN 1, TN 2, TN 3.
A validation process is set by default to determine if the transactions have the correct process type (for photoduplication processing) and are in an appropriate status for the batch update. Error messages will display and cancel the process at the point when the error record is detected. To override the validation process, uncheck the Prompt on Invalid Starting Status option.
Note: The override process will not override the User Not Signed In error message.
Clearing the Grid
To clear transactions from the grid, click Clear History. This clears all transactions from the grid but does not change them in any way.
Batch Processing will display error messages if you do not follow the usual workflow or attempt a process that is now allowed.
If an item is not at the appropriate status for the attempted process, a Nonstandard Process warning displays and asks if you would like to continue. The default answer is No. An example of a nonstandard process warning:
- Routing from In Item Retrieval to Item Delivered is not the standard process. Would you like to continue?
Invalid Request Type
This warning displays to inform you that you are not allowed to perform the attempted process. Examples of error messages include:
- Copy requests cannot be placed on hold.
- Loan requests cannot be routed to delivered.
User Not Signed In
This warning displays when attempting to check out an item to a user not signed into the reading room and the ItemCheckoutSecurityPrompt key is set to Yes.