Essentially, a transaction script is a file; a method by which you can transfer information from a wireless (or wired) scanner or plain text document (i.e. .txt) such as those created in Notepad (Windows) or TextEdit (Macintosh) into Alexandria.

Although mainly used when performing inventory, transaction scripts aren't limited to that activity. In the event that your Workstation loses connection with the Data Station and Alexandria is not available, you can use transaction scripts to perform circulation in a plain text file and then import your script later when connections have been restored.

You can create a .txt file containing (patron or item) barcodes and circulation commands to be processed at a later date. These scripts can be used for both inventory and remote circulation. Regardless of mode, your transaction script should consist of a list of barcodes (either patron or item) that are added one barcode per line to the file; it makes no difference whether these are typed or scanned.

Transaction scripts are text files that are readable by Notepad (Windows) or TextEdit (Macintosh). When creating your transaction scripts, be sure to save as a “plain text” or “ascii text” format rather than “rich text” or any other format; Alexandria can only process plain text files as transaction scripts.

When the text file is imported, each line (separated by line break or carriage return) will give instructions to the Circulation window just as if it were being typed into the command line.

As an example, let's examine the contents of a transaction script used for remote circulation.

The period (.) and double period (..) in the first two lines will clear any circulation modes, patrons, or items that may be current in your Circulation window.

If you are performing remote circulation (as shown in the example above), the secondary redundant period (.) ensures that Alexandria is in Check In/Out (.) mode. In this mode, each item barcode processed will be checked out to the patron whose barcode precedes it.

If you are performing inventory, substitute the secondary period with an (IB) for Inventory Bookdrop mode. In this mode, any items scanned will be inventoried as well as checked in if they're currently checked out.

Whether you're creating the transaction script by manually typing the commands and barcodes or scanning them into notepad, they're all imported into Alexandria in the same manner; please review the documentation here to learn how to import transaction scripts.

Creating Transaction Scripts

There are several different reasons for creating your own transaction scripts: they can be used for inventory, creating lists of barcodes, or checking items out for a curriculum unit. Sometimes it is not possible to use Alexandria, like during a prolonged rebuild. Transaction scripts are essential if you have no connection to the network or to your Alexandria Data Station and still need to perform circulation. Transaction scripts work with many other commands and circulation modes; you can assign keywords, change patron policies or locations, or change copy policies, collections, or locations. Thankfully, creating transaction scripts is easy.

Follow these steps to create a transaction script for inventory or remote circulation.

1. Open a word processor or text editor that can save a plain text .txt file.
2. On the first line of your text document, type a period (.) and press <enter>; this tells Alexandria that the file is a transaction script.
3. On the following line, type two periods (..) and press <enter>; this tells Alexandria to clear any circulation modes, patrons, or items that may be current in the Circulation window.
4. Next, type the command that activates the appropriate circulation mode (e.g. “ . ”, “ B ”, or “ IB ”) and press <enter>.
5. Now, scan (or type) your barcodes. If you're performing inventory, scan (or type) the barcodes of your items. If you are performing remote circulation, scan (or type) the patron's barcode followed by the barcode(s) of the item(s) they are checking out.
6. If you need or want an override date, enter it before scanning barcodes. Override dates are set by typing “.{date}” such as “.12/20/2001”. Remember to clear the override date once it is no longer applicable by typing a period (.) on a new line and pressing <enter>.
7. If you do not intend to import the transaction script on the same day you created it, then be sure to provide an override date before scanning items that are returned. For example, if you're creating a transaction script with Bookdrop as the indicated circulation mode, the override date is the “returned” date that Alexandria will use to calculate any applicable fines.
8. When finished with the script, type a period (.) and press <enter>.
9. In your word processor or text editor, go to File on the main menu bar and select Save As.
10. Give the file a descriptive name and select “.txt” as the format in which to save the document.
11. When you are ready, you can import the transaction script.

Import Transaction Scripts

Command: *

Circulation script imports are now triggered by dropping an import script in the Circulation Window.

Dropping a .txt file that contains copy barcode numbers or circulation commands (for remote processing) on the Circulation window will trigger a transaction script import. Transaction scripts (also known as circulation scripts) can also be created (or edited) using word processors or simple text editors—just as long as the file can be saved as a .txt file.

Since this function is typically used for inventory scans, Alexandria defaults all transaction files to begin with the Inventory command. If you are using a transaction file for purposes other than inventory, you must have the appropriate header designated in the file. You can also drag and drop these files onto the Circulation window or use the Import command if they have the proper file header. Alexandria will recognize them as transaction files and process them accordingly.

Use these steps to import transaction script information into Alexandria from the Circulation window.

1. Drop an import script onto the Circulation window.
2. Make sure to archive (and back up, if you're Self-Hosted) your current Alexandria data.
3. The file will be added to the Operations Management queue for automatic import.
4. Once completed, your data is now imported into the Alexandria database.
5. From here, you can go to Operations Management to access the original import file, review the operation summary, or email the summary to anyone you'd like.