Sort Offline Transactions Report
The Sort Offline Transactions (Sortstand) report consolidates and sorts offline transactions that were recorded by Offline WorkFlows in multiple libraries. This report produces the standtrans.srt file, which contains all of the sorted offline transactions for the libraries. Library administrators can manually break this file into multiple files for simultaneous processing by the API server.
Run this report only with the guidance of SirsiDynix Customer Support.
This report is typically used only by library consortia and very large library systems that find the Load Offline Transactions (Loadstand) report does not process the volume of collected offline transactions efficiently enough for library needs.
The offline transactions in the output file produced by this report must be processed with the API server.
This Sort Offline Transactions report contains the following tabs:
| • | Basic Tab: Reports, |
| • | Transaction Selection Tab |
This report is a part of the Administration Group Reports.
If your consortia or library system decides to use the Sort Offline Transactions report, the basic workflow of collecting and applying offline transactions is as follows:
| 1 | Use Offline WorkFlows for Recording Offline Transactions when the SirsiDynix Symphony server is unavailable. |
| 2 | When the server becomes available again, the next step is Transferring Offline Transactions When the Server is Available to the server. |
| 3 | Use the Sort Offline Transactions report for Consolidating and Sorting the Offline Transactions from the libraries. |
| 4 | Manually divide the sorted transactions file into multiple files, and begin Processing the Offline Transactions with the API Server simultaneously. |
Recording Offline Transactions
When the SirsiDynix Symphony server is unavailable, use the Offline WorkFlows wizards to continue circulating items and registering users. As you work, transactions are written to a log file named for the library selected in the Library field of the Report Session wizard in Offline WorkFlows. This log file is created in the login\Sirsi\Workflows\LOG directory in the home directory of your login, which is typically Documents and Settings for Windows workstations. For example, if you logged into the Windows workstation at the Washington Library as CIRCMAIN, the log file is in Documents and Settings\CIRCMAIN\Sirsi\Workflows\LOG\WASHINGTON.
In SirsiDynix Symphony K12, if your system is configured to allow duplicate item IDs in different school libraries, you cannot share materials across libraries.
Transferring Offline Transactions When the Server is Available
When the server becomes available again, clear the Operate in Offline Mode check box on the Configuration window to connect the WorkFlows client to the server. When WorkFlows connects to the server, the Documents and Settings\login\Sirsi\Workflows\LOG\LibraryName file is automatically transferred to the server as Unicorn/Standalone/Library/standlog.x, where LibraryName is the name of the library at which the transactions were recorded, and x is the station number. The original LOG/LibraryName file on the workstation is removed.
For example, on workstation number 1, the CIRCMAIN\Sirsi\Workflows\LOG\WASHINGTON file will be transferred to the server as Unicorn/Standalone/WASHINGTON/standlog.1.
Consolidating and Sorting the Offline Transactions
On the SirsiDynix Symphony server, run the Sort Offline Transactions report. By default the report gathers only those transasctions that occurred during the previous seven days (however, you can modify the range in the Transaction Selection tab). Each library’s standalone.x files are combined, sorted, and written to the standtrans.srt file.
The report combines all of the standalone.x files in the Unicorn/Standalone/LibraryName directory on the server. The report then sorts the transactions by date, then by item barcode in dictionary sort order. Since the Offline WorkFlows New User Registration wizard transactions create user records and do not have item barcodes associated with them, the create user transactions are filtered to the beginning of the sorted transactions file. This ensures that when the transactions are later processed with the API server, the user record creation transactions are applied to the database before any item transactions are applied. The item transactions are grouped in chronological and dictionary sort order after the create user transactions.
The Sort Offline Transactions log will note if any older transactions were found. These transactions are appended to a file named old_transactions and saved in the /Unicorn/standalone/LibraryName/ directory. Library staff can examine this file to determine how each transaction should be handled.
Processing the Offline Transactions with the API Server
The sorted standtrans.srt file can be broken manually into multiple separate files for processing by the API server. Since API server knowledge is required for this task, you must have API server training and consult SirsiDynix Customer Support for guidance.
Related topics