Offline WorkFlows is the standalone mode of the WorkFlows client. Offline WorkFlows is used to run a SirsiDynix Symphony WorkFlows-style workstation without actually connecting to the SirsiDynix Symphony server.

How do I prepare the WorkFlows client to use Offline WorkFlows in the event of an emergency?

Do the following to keep the SirsiDynix Symphony WorkFlows workstation up to date so it can use Offline WorkFlows at a moment’s notice.

On the SirsiDynix Symphony server, run the Prepare GUI Offline Data report to make sure that you have the most current policies and configuration information for your library system. The report generates the files verifylist and config. You should schedule this report to run at least weekly.

On the SirsiDynix Symphony server, run the Update User Delinquency Status report, selecting to generate a list of delinquent users, to make sure that you have current user data for Offline WorkFlows. The report generates the delinq file (user status file) and the dumpdate file (date and time information). You should schedule this report to run daily.

Start the SirsiDynix Symphony WorkFlows client, and connect to the SirsiDynix Symphony server. The verifylist, config, dumpdate, and delinq files are automatically sent to the \Sirsi\Jwf\Configure directory on the workstation.

If your site uses the User Groups feature, the delinq file will include information about all users that belong to a group, regardless of their status. As a result, the file will be increased in size and it may take longer to download.

How do I start and use Offline WorkFlows?

When the SirsiDynix Symphony server is unavailable, do the following to use Offline WorkFlows to continue circulating items and registering users.

Start the SirsiDynix Symphony WorkFlows client. In the Configuration window, select the Operate in Offline Mode check box, and click OK.

Select the Offline toolbar.

Click the Offline Session Settings wizard, confirm or change the settings, and click OK to close the wizard.

Use the Offline wizards for as long as the SirsiDynix Symphony server is unavailable. As you work, transactions are written to a log file named for the library selected in the Library field 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 workstation at the Washington Library as CIRCMAIN, the log file is in \Documents and Settings\CIRCMAIN\Sirsi\Workflows\LOG\WASHINGTON.

Each time you start Offline WorkFlows to record offline transactions, the transactions will be appended to the log file. The log file will continue to record transactions until the workstation can connect to the server again.

How do I stop using Offline WorkFlows and use the WorkFlows client again?

When the SirsiDynix Symphony server becomes available again, do the following to switch from Offline WorkFlows (the offline mode of WorkFlows) to using the usual client mode of WorkFlows.

Double-click the SirsiDynix Symphony WorkFlows client icon.

In the Configuration window, clear the Operate in Offline Mode check box. Notice that all of the other options in the window become available.

Specify the server and workstation information that you normally use to connect to the server, and click OK.

How do I get the offline transactions from the workstation to the SirsiDynix Symphony server?

When the WorkFlows client connects to the server, the \Documents and Settings\login\Sirsi\Workflows\LOG\Library file is automatically transferred to the server as /Unicorn/Standalone/Library/standlog.x, where Library is the name of the library at which the transactions were recorded, and x is the station number. The original \LOG\Library 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.

How do I apply the offline transactions to the SirsiDynix Symphony database?

On the SirsiDynix Symphony server, run the Load Offline Transactions port. Each library’s standalone.x files are combined, sorted, and processed. Any transactions that could not be processed are moved to the /Unicorn/Standalone/oerrors file on the SirsiDynix Symphony server.

On the SirsiDynix Symphony server, run the Consolidate Daily Transactions report and the Statistics Log report to add the history logs to the monthly statistics logs.

What do I do if some transactions do not load on the server?

When offline transactions fail, manually review the transaction in the /Unicorn/Standalone/oerrors file on the SirsiDynix Symphony server and take whatever steps required to best account for the material that is in the possession of the user. If the user is known, you can override the block to charge the item to the user. If the user is not known, you can charge the item to MISSING.

Why can’t I see users who were added in Offline WorkFlows?

User records that were added in Offline WorkFlows are not searchable until the Add, Delete, Update report is run on the library server (see Add, Delete, Update User Report).

Is it possible to validate SirsiDynix auto-generated barcodes when using the WorkFlows Offline client?

No, it is not possible to validate SirsiDynix auto-generated barcodes in the Offline client. In order to validate a SirsiDynix auto-generated ID, the client must have access to the user or item database. Unlike other barcode formats, the routine used for SirsiDynix auto-generated IDs is not defined in a policy that can be downloaded to the Offline client.