System Administrator Notes - UTM Library Portalportal.psz.utm.my/.../SYMPHONY33-SystemAdministratorNotes.pdf · General 9 General Enhancements Open Source File Now Available from

SirsiDynix Symphony 3.3

System Administrator Notes

July 2009

© 2009 SirsiDynix. All rights reserved.

The processes and all the routines contained herein are the proprietary properties and trade secrets of SirsiDynix. Except as provided by license agreement, this manual shall not be duplicated, used or disclosed for any purpose or reason, in whole or in part, without the express written consent of SirsiDynix. The information in this document is subject to change without notice and should not be construed as a commitment by SirsiDynix.

SirsiDynix grants the right of copying the enclosed material solely for the internal business use of the end user if (1) this document has been obtained by purchase or by license agreement in conjunction with SirsiDynix products, and (2) this copyright statement is included with each copy. All other copying or distribution is strictly prohibited.

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in sub-paragraph (b)(3) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013.

Rights for non-DOD U.S. Government departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).

Sirsi®, WebCat®, Vizion®, WorkFlows®, Unicorn®, UnicornECOLE®, UnicornOASIS®, UnicornSTILAS®, Site Source®, DRA®, DRA Net®, Inlex®, MultiLIS®, Taos®, JurisLink™, Corinthian®, Dynix®, URSA®, Horizon™, Remote Patron Authentication™, TeleCirc™, and SirsiDynix Symphony™ are trademarks of SirsiDynix.

Other product and company names herein may be the trademarks of their respective owners. All titles, versions, trademarks, claims of compatibility, etc., of hardware and software products mentioned herein are the sole property and responsibility of the respective vendors. SirsiDynix makes no endorsement of any particular product for any purpose, nor claims responsibility for its operation and accuracy.

This document is compatible with SirsiDynix Symphony 3.3. Information in this document may also be compatible with later versions.

July 2009

iii

Table of Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Open Source File Now Available from SirsiDynix FTP Server. . . . . . . . . . . . . . . 9

WorkFlows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

WorkFlows Java Client Installation No Longer Requires Administrative Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Enhancements and Changes to Support Cataloging, Importing, and Displaying UNIMARC-formatted Bibliographic and Authority Records . . . . . . . . . . . . 14

Academic Reserves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Academic Reservations Module Added to WorkFlows Java Client . . . . . . . . . . 21

Acquisitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Automatic Tax Calculation Enhanced for Tax Included in Invoice Line Amounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Wizard and Helper Property Changes for Taxes Paid to a Vendor . . . . . . . . . . 26

Vendor Records, Vendor Wizards, Invoice Records, and Invoice Wizards Enhanced to Handle Vendors with a Tax Exempt Status . . . . . . . . . . . . . . . 28

Material Type Field and Default Property Added to Order Wizards to Specify an Acquisitions Material Type for Orderlines . . . . . . . . . . . . . . . . . 30

Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

When Busy, Server Can Be Configured to Retry Acquisitions Transactions Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Receive Orders Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Acquisitions Workslip Printing Added to Receive Orders Wizard . . . . . . . . . . . 32

Session Settings Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Maximum Number of Segments to Display in the View Pane Increased to 200 Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Added Setting to Prompt Before Cancelling On-Order Holds . . . . . . . . . . . . . . 33

Table of Contents

iv

Cataloging Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Formats Updated to Reflect Changes in the MARC 21 Cataloging Standard . . . 35

Added Automatic Printing of Labels Using Default Label Templates of Specific Library/Item Type Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Label Designer Sample Templates Are Now Delivered with the Version 3.3 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Global Call Number Modification Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

New Global Call Number Modification Wizard . . . . . . . . . . . . . . . . . . . . . . . . 44

Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

New User Name Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

New Circulation Sets Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Reorder Hold Queue Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

New Wizard for Reordering Holds in the Hold Queue . . . . . . . . . . . . . . . . . . . 55

e-Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

My Lists Feature Added for Users To Create and Maintain Permanent Lists of Titles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Tabbed Display Replaces the Review My Account Display. . . . . . . . . . . . . . . . 59

Updated Interface to the e-Library Includes Support for Local Cascading Stylesheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

User Can Bookmark Pages and Create Permalinks to Pages . . . . . . . . . . . . . . . 74

Page Titles Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

NoveList URL Updated in Environment Files . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Dates Can Display in Descriptive Format Instead of Numeric Format . . . . . . . . 78

Online User Registration Changed to Support the User Name Fields in SirsiDynix Symphony 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

SirsiDynix Enterprise Users Can Place Holds Without Having Access to the e-Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

All Content Link in Item’s Detailed View Displays Syndetic Enrichment Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Barnes & Noble Link Corrected for Buy Now Option . . . . . . . . . . . . . . . . . . . . 85

Optional Security Feature Added to Prevent Users from Accessing the My Account Pages Using a Copied URL. . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Message Displays to Show the Status of Online Bill Payments Made With AXIS Payment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Electronic Bill Payments Work Correctly in the e-Library revD Pages . . . . . . . . 88

v

Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Administration Group Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Refactor User Name Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Load Users Report Updated to Load New User Name Fields . . . . . . . . . . . . . . 92

Authority Group Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Added Ability to Sort Headings in List Authority Records Report . . . . . . . . . . . 96

Debt Collection Group Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Updates to Debt Collection Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Maintenance Group Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

New Report Added to Remove X12 Files That Do Not Have a Corresponding EDI Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Outreach Reports Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Outreach Reports Required to be Rescheduled For Outreach Route Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Oracle Report Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Extract Snapshots for Reporting Report Added to the Oracle Report Group . . 103

SirsiDynix StaffWeb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Due Date Receipts Can Print for Checkouts and Renewals . . . . . . . . . . . . . . . 105

System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

New Wizard Added For Outreach Module Configuration. . . . . . . . . . . . . . . . 107

Acquisitions Configuration Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Two New Fund Level Wizards Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Cataloging Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

New Label Template Profiles Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Circulation Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Default Price Policy — Added Ability to Control the Number of Days Auto-refunds for Lost Items Can Be Accepted. . . . . . . . . . . . . . . . . . . . . . 109

New Circulation Set Category Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Table of Contents

vi

Global Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Can Configure System to Display Only MARC21 Formats, Only UNIMARC Formats, or Both MARC21 and UNIMARC . . . . . . . . . . . . . . . . . . . . . . . . 110

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Environment Variables Added to Run Commands or Scripts for Starting and Stopping an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Introduction 7

Introduction

The SirsiDynix Symphony Administrator Notes for SirsiDynix Symphony 3.3 are a subset of the entire set of release notes for SirsiDynix Symphony 3.3. Since this version of SirsiDynix Symphony includes a large number of enhancements and corrections, the administrator notes are intended to help the system administrator identify the changes that may require additional configuration. For many software changes, supplemental information is included in this document to alert SirsiDynix Symphony administrators to tasks that might need to be performed as part of staging the new version at your site, such as the following list.

• Creating or checking new policies

• Creating or checking new WorkFlows properties

• Examining e-Library or Web2 page changes in light of any customized pages at your site

• Adjustments to user access policies

• Other administrative tasks, such as rescheduling reports to take advantage of new options

The supplemental administration information is only available in the SirsiDynix Symphony Administrator Notes. The SirsiDynix Symphony release notes contain details about all significant enhancements and corrections, including changes that do not require any administrative action. Sites that wish to restrict information related to system administration tasks may choose to distribute only the SirsiDynix Symphony release notes to non-administrative users.

When available, these notes contain an internal tracking number used by SirsiDynix to identify software changes. The number displays in parentheses after the text of the note.

8 SirsiDynix Symphony 3.3 Administrator Notes

General 9

General

Enhancements

Open Source File Now Available from SirsiDynix FTP Server

SirsiDynix Symphony utilizes several Open Source packages, and, historically, these packages have been included in the installation and upgrade programs. The installation and upgrade script files have grown considerably large over time, and so SirsiDynix determined that the opensource.tgz file (which includes the Open Source software) should be removed from future installation and upgrade programs.

With Version 3.3, the opensource.tgz file will now be available from the SirsiDynix FTP server (ftp.sirsi.com) in a new read-only account, in the /Symphony_3.3 directory.

The read-only account access information is as follows:

• user ID = opensource

• password = 0pensource (the number zero + “pensource”)

Sites can FTP to the ftp.sirsi.com and download the Open Source packages used in SirsiDynix Symphony Version 3.3, and all future releases and upgrades. New directories will be created for future SirsiDynix Symphony versions so that users will be able to download the appropriate version of the opensource.tgz file for their version of SirsiDynix Symphony. (UNI-22335)


WorkFlows Client 11

WorkFlows Client

General

Enhancements

WorkFlows Java Client Installation No Longer Requires Administrative Privileges

WorkFlows Client for Java client versions before Version 3.3 required administrative privileges on the workstation to install or upgrade the client on individual workstations. Now, the install and upgrade scripts have been modified and migrated to later versions of the InstallShield program which have the ability to execute with a wider range of privileges.

System Requirements

To install or update to the SirsiDynix Symphony 3.3 WorkFlows Java client, the system must meet the following minimum requirements.

• OS/Platform: XP, Vista, or Macintosh OS X (10.5 Update 2, Dual Core, 64 bit)

• RAM minimum: 1 GB, Suggested: 2 GB

• Processor speed minimum: Windows XP (minimum 700 MHz, rec. 1 Ghz) Windows Vista (800 MHz, 1GHz) Mac (2 Ghz)

• Disk space for WorkFlows: 100 MB free hard disk space

• Monitor resolution: 1024 x 768 or better

Because versions of the WorkFlows Client for Java previous to Version 3.3 were installed and upgraded by users with administrative privileges on the workstation, it will not be possible for a user without administrative privileges to upgrade an earlier version simply by starting the client and following upgrade instructions. For this reason, SirsiDynix recommends that the previous version of the client be un-installed, and the 3.3 version be installed by a user that does not have administrative privileges on the workstation. Once the new version of the client has been installed in this manner, non-administrative users will be able to upgrade the client to future versions simply by clicking on the client icon on the desktop and following the instructions.

SirsiDynix recognizes that it may not be practical to uninstall the previous version prior to installing the new version. If this is the case, SirsiDynix recommends that the desktop icon associated with the older version of the client be deleted from the desktop so as not to confuse staff users.


• TCP/IP networking support

• Ability to connect to a SirsiDynix Symphony 3.3 server

• Java 1.6

Note: Macintosh supports Java 1.6 only on 64 Bit, Dual Core Macintosh workstations running Leopard OSX 10.5, Update 2 or higher. For Macs that do not meet these requirements, users can run the SirsiDynix Symphony 3.2.1 WorkFlows Java client, which requires Java 1.5 rather than Java 1.6, against the SirsiDynix Symphony 3.3. server. Please refer to the client/server specifications for SirsiDynix Symphony 3.2.1 for details on Mac hardware specifications. While SirsiDynix has tested the Mac 3.2.1 WorkFlows Java Client against SirsiDynix Symphony 3.3, SirsiDynix strongly recommends that sites using Macs that upgrade to Symphony 3.3 make plans to upgrade to the 3.3 version of the Workflows Java client in order to take advantage of new capabilities and corrections and to ensure optimal support.

Additional Important Considerations

• On workstations running the WorkFlows Java client, SirsiDynix recommends setting the virtual memory association to equal twice the amount of physical memory, at minimum. Please work with the system administrator to check the virtual memory setting on each workstation running the WorkFlows Java client, and increase the memory if necessary.

• The WorkFlows Java client will not affect e-Library stations, which will require only a Web browser.

• Virus protection software should be temporarily disabled while installing the WorkFlows Java client.

Installation Steps

If the user has never used the WorkFlows Java client on the Windows workstation, or has never installed the client under a particular login username, follow this procedure.

To install the WorkFlows Java client on a Windows system

1 Log into the Windows workstation. You should log in as the user who will be installing the WorkFlows Java client. This can be the Administrator or a non-administrator.

2 The fupd_jwf.exe file from the /Unicorn/Clients directory on the server should already have been copied to your workstation as part of the upgrade process.

Locate the fupd_jwf.exe executable file on your workstation and double-click it to launch the Install Shield.

Sites with Windows Vista workstations will need to disable User Account Control before non-administrator accounts can install and update the WorkFlows Java client. The following Microsoft documentation explains the User Account Control feature in some detail: http://technet.microsoft.com/en-us/library/cc709628.aspx.

WorkFlows Client 13

3 Follow the instructions in the setup windows. Answer the questions posted by the installation program affirmatively.

4 At the end of the install, you will be prompted to connect the client to the Symphony server. The installation will not be complete until you connect the client to the server.

Type the server connection information. Allow the WorkFlows Java client to connect to the SirsiDynix Symphony server and transfer server files to the client system.

5 If you are logged on to the Windows workstation as an administrator, the WorkFlows Java client will be installed in the \Program Files\Sirsi\JWF directory on the workstation. This client will be accessible to all users on the workstation, but only the administrator will later be able to update the client to future versions.

6 If you are not logged into the Windows workstation as an administrator, then the WorkFlows Java client will be installed in C:\Documents and Settings\[name]\Sirsi\JWF. Only users logged in under this username will be able to access this client. Only these users will later be able to update this client to future versions.

7 If there are multiple non-administrator users logging into the same workstation with different user names, each user can install his or her own copy of the WorkFlows Java client. Each login user will only see the Desktop icon for his or her own copy of the client, and each login user will only be able to update his or her own copy of the client.

(UNI-22481)

Enhancements and Changes to Support Cataloging, Importing, and Displaying UNIMARC-formatted Bibliographic and Authority Records

Many enhancements were made to the SirsiDynix Symphony system for cataloging, importing, and display UNIMARC-formatted bibliographic and authority records.

These enhancements include the following:

• Added ability to configure the system to display only MARC21 formats, only UNIMARC formats, or both MARC21 and UNIMARC

• Catalog, authority, and Z39.50 formats updated with latest UNIMARC changes

• UNIMARC Authority variations added to catalog formats

• UNIMARC Punctuation variations added to catalog formats

• Bibliographic record loading reports and SmartPort support UNIMARC title control key and MARC tag hierarchy match and load options

• Authority Map wizard accommodates import of UNIMARC records

For detailed instructions on the new Version 3.3.0 WorkFlows Java client installation, see the document titled “Installing the Version 3.3.0 WorkFlows Java Client on Windows Workstations“on the SirsiDynix Client Care page.


• New delivered UNIMARC Authority Map policies

• New NSB/NSE Character helper for non-sorting begin and non-sorting end character input

• NSB/NSE non-filing characters added to catalog and authority formats

• MARC Record Editor updates

• SmartPort and Z39.50 Gateway Destination Elements Enhancements

• Validate Headings helper authorizes UNIMARC fields

See the following subsections for more information about these UNIMARC enhancements.

Sites Can Configure System to Display Only MARC21 Formats, Only UNIMARC Formats, or Both MARC21 and UNIMARC

The Display UNIMARC Formats Global Configuration policy has been changed so that sites can configure their systems to display only MARC21 formats, only UNIMARC formats, or both MARC21 and UNIMARC formats in the clients. The policy is now named “MARC Format Display.” By default, only MARC21 formats display.

Currently Delivered Catalog, Authority, and Z39.50 Formats Updated

The current UNIMARC catalog, authority, and Z39.50 formats were updated with the latest UNIMARC enhancements.

The following UNIMARC catalog formats are delivered:

• UNIMARC (Bibliographic)

• SUNIMARC (Serials)

• UNIMAP (Map)

The following UNIMARC authority formats are delivered:

• UCOLUNITTL (Collective uniform title heading)

• UCRPNAME (Corporate name heading)

• UFAMNAME (Family name heading)

• UGENRE (Form or genre heading)

• UNAMCOLTTL (Name/collective uniform title heading)

• UNAMTITL (Name/title heading)

If a site wishes to use UNIMARC formats on their system, they must be an Oracle/Unicode system.

Also, the site must have the MARC Family feature configured for the system. Contact SirsiDynix Client Care about configuring the system for MARC families.

During the Version 3.3 upgrade process, the site will need to run an additional conversion script to add the new UNIMARC formats and supporting features.

WorkFlows Client 15

• UPERNAME (Personal name heading

• UPLACE (Place access)

• UPORASSUN (Bib.NacPortugal assunto)

• URAMEAU (Sujet Rameau)

• USUBJ (Topical subject heading

• UTERNAME (Territorial/geographic name heading)

• UTRDMARK (Trademark heading)

• UUNITITL (Uniform title heading)

The following UNIMARC Z39.50 formats are delivered:

• ZUNIMARC (Z39.50 bibliographic)

• ZUNIAUTH (Z39.50 authority)

For more information about the UNIMARC formats, go to the IFLANET Concise UNIMARC Classification Format Web page (http://www.ifla.org/VI/3/p1996-1/concise.htm).

UNIMARC Authority Variations Added to Catalog Formats

Default authority variations have been added to the catalog formats. For a table of the bibliographic fields under authority control, see the “Delivered Formats for Bibliographic Fields Under Authority Control — UNIMARC” topic in the WorkFlows Java client online Help.

UNIMARC Punctuation Variations Added to Catalog Formats

The Punctuations tab now displays for entries in UNIMARC catalog and authority formats, and default punctuation variations have been added to the catalog formats.

Bibliographic Record Loading Reports and SmartPort Wizard Now Support UNIMARC Title Control Key and MARC Tag Hierarchy Match and Load Options

Data fields in the UNIMARC bibliographic format do not always include the same data as the equivalent MARC21 tags. Previously, the bibliographic load programs did not allow the appropriate options for loading UNIMARC bibliographic records. Now, these programs have been updated, and the title control key options and MARC tag hierarchy options in the reports and wizard have also been updated to display the UNIMARC tag selections. The following reports and wizard have been updated.

• Load Bibliographic Records

• Load Bibs for Selection

• Load Bibs with Order Information

• SmartPort wizard


New Title Control Key Rules Gadget Options In the bibliographic load reports and in the SmartPort wizard properties, users can now select the following UNIMARC title control key options.

• ISBN (U 010)

• ISSN (U 011)

New Match MARC Tag Hierarchy Gadget Options In the bibliographic load reports and in the SmartPort wizard properties, users can now select the following UNIMARC tag hierarchy options.

• National Bibliographic Number (U 020)

• ISBN (U 010)

• ISSN (U 011)

• Government Publication Number (U 022)

• International Standard Music Number (U 013)

• International Standard Recording Code (U 016)

• International Standard Report Number (U 015)

• Publisher Number (U 071)

Authority Map Wizard Enhanced to Accommodate Import of UNIMARC Authority Records

To support importing UNIMARC authority records into a SirsiDynix Symphony system, the Authority Map wizard has been enhanced with the following new attributes.

• MARC Family — The MARC Family policy allows the user to choose the type of MARC21 or UNIMARC encoding that applies to a specific set of authority records. Select a MARC Family policy from the drop-down list. (This selection will only appear for sites configured to use MARC Family.)

• Source of Subject (previously 8/11 source) — Identifies the source of the subject heading.

– For MARC21 records, if the content of the 008 fixed field position 11 affects the authority format that should be assigned, this attribute should be the single character code in the record’s 008 field in byte (position) 11 which identifies the source (according to the MARC 21 Authority Format Manual). Type the single character code value.

– For UNIMARC records, the source of subject heading is defined in the 152 field, subfield b. The value of |b is a string instead of a single character code. Type the source code value, up to 25 characters.

The U before the number designates a UNIMARC tag.

WorkFlows Client 17

New Delivered UNIMARC Authority Map Policies

The following UNIMARC Authority Map policies are now delivered:

• Personal Name (UPERSNAME) — 200

• Topical Subject (UTOPSUBJ) — 250

• Sujet Rameau (URAMEAU) — 250

• Corporate or meeting name (UCORP) — 210

• Territorial/Geographical name (UTERRNAME) — 215

• Trademark (UTRADEMK) — 216

• Uniform title (UTITLE) — 230

• Collecive uniform title (UCOLLTITL) — 235

• Name/title (UNAMETITL) — 240

• Name/collective uniform title (UNAMCOLUNI) — 245

• Place access (UPLACEACC) — 260

• Form/genre term (UGENREFORM) — 280

• Family name (UFAMILY) — 220

• Assunto de Biblioteca Nacional de Portugal (BNPORTUGAL) — 250

New Add NSB/NSE Characters Helper for Non-sorting Begin and Non-Sorting End Character Input

The new Add NSB/NSE Characters helper was created for adding and viewing the NSB (Non-sorting begin) and NSE (non-sorting end) characters in WorkFlows Java client cataloging and authority wizards. Because these characters are only used in UNIMARC formats, the helper is only available on SirsiDynix Symphony Unicode/Oracle systems. The NSB/NSE are non-printable characters and will not display in full record displays or cataloging and authority wizard View panes.

The Add NSB/NSE Characters helper is available in the following wizards:

• Add Title

• Modify Title

• Duplicate Title

• Add Authority

• Modify Authority

• Duplicate Authority

A new property, Add NSB/NSE Characters, was added to the Helpers tab in the wizards’ properties. When the user selects this property, and if the format of a record is a UNIMARC format, the helper will display in these wizards.


Added NSB/NSE Non-filing Characters to UNIMARC Catalog and Authority Format Entries Keyword, Browse, and Authority Variations for the Leading Article Value

Because the UNIMARC formats use the NSB/NSE (Non-sorting begin/non-sorting end) characters for non-filing purposes, the NSB/NSE selection will appear on the Keyword, Browse, and Authority tabs for catalog and authority format entries as a Leading Article value selection.

In UNIMARC catalog formats, the INDICATOR1 and INDICATOR2 values are no longer available for selection on these entry tabs as they are not used for non-filing purposes.

MARC Record Editor Updates

The MARC Record Editor in cataloging and authority wizards has been updated to handle cataloging UNIMARC records.

• The Record Editor allows input and edit of coded fields for cataloging and authority records.

• The Record Editor help includes updated tooltips and more for UNIMARC records. Users can modify these tooltips using the MARC Record Editor Help wizard.

SmartPort and Z39.50 Gateway Destination Element Enhancements

The following changes were made to the Z39.50 gateway destination element configurations for SmartPort import of UNIMARC-formatted records.

• Query Character Set — This attribute appears on the Destination tab for the Gateway element type Z3950 Search. The attribute specifies the type of character encoding used in the query sent to this Z39.50 destination. For example, the Library of Congress Z39.50 server expects search query strings to be sent using UTF8 character encoding, so this attribute should be set to UNICODE for the LC destination. Possible values include UNICODE, MARC8, ANSI, CCCII, BIG5, GBK, and UNIMARC. The MARC8 value is the default value.

• Record Character Set — This attribute appears on the Destination tab for the Gateway element type Z3950 Search. The attribute specifies the type of character encoding used in the records of this Z39.50 destination. For example, Chinese sites may use CCCII records, which are also MARC records, but use a different character encoding for Chinese characters. When records are imported into SirsiDynix Symphony from these sites, a different table for conversion is required to convert CCCII records to Unicode records, so this attribute should be set to CCCII. The WorkFlows client will know which character encoding is used by the Z39.50 site based on the value in this field. Possible values include UNICODE, MARC8, ANSI, CCCII, BIG5, GBK, and UNIMARC. The MARC8 value is the default value.

WorkFlows Client 19

Validate Headings Helper Authorizes UNIMARC Fields

The Validate Headings helper has been enhanced with the ability to authorize UNIMARC fields. However, since the Propose Authority function of this helper is MARC21 based, the Propose option is not available (the Propose button does not display) if the bibliographic record type is UNIMARC. The Propose Authority option is still available for MARC21-formatted records.

SirsiDynix Symphony System Administrator Notes

The SirsiDynix Symphony System Administrator must consider the following when deciding to use UNIMARC formats.

• If a site wishes to use UNIMARC formats on their system, they must be an Oracle/Unicode system.

• The site must have the MARC Family feature configured for the system. Contact SirsiDynix Client Care about configuring the system for MARC families.

• In the Global Configuration wizard, sites will need to set the MARC Format Display to display only UNIMARC formats or display both UNIMARC formats and MARC formats. By default, this policy is set to display only MARC formats.

• During the Version 3.3 upgrade process, the site will need to run an additional conversion script to add the new UNIMARC formats and supporting cataloging and authority features.

(UNI-14598, UNI-16253, UNI-16254, UNI-16255, UNI-17218, UNI-17825, UNI-18087, UNI-18774, UNI-18786, UNI-18814, UNI-19424, UNI-19440, UNI-20135, UNI-20520, UNI-21522, UNI-20661)


Academic Reserves 21

Academic Reserves

General

Enhancements

Academic Reservations Module Added to WorkFlows Java Client

With Version 3.3, the Academic Reservations module has been added to the WorkFlows Java client. Academic Reservations allow users to make advance reservations on Reserve materials to guarantee that the materials will be available at the Reserve Desk at the requested time.

Unlike placing a hold, which requests library materials for use as soon as they become available, making a reservation on a reserve title requests a copy of the title for a specific date and time and for a specific period of time. Other patrons may use the reserve materials until the reservation time period; at that time, the item must be returned to the Reserve Desk so it can be checked out to the patron who made the reservation. SirsiDynix Symphony tracks and schedules reservations for the entire reservation cycle, from the staff preparation of reserve materials, to the actual use of the item, and to the return of reserve materials.

The Academic Reservations module includes the following features.

• Reservation profiles can be created to determine how reservations may be made on reserve items.

• Reservations can be restricted by item type and by user profile.

• Reservations may be placed by the minute. Starting and ending dates and times must be specified for each reservation.

• Reservations can be configured to be unavailable for certain times even though the Reserve Desk is open.

Academic Reservations Wizards

The academic reservations wizards appear on the Reserves toolbar in the Reservations Information and Maintenance wizard group. The following wizards are used to create, display, modify, and remove reservation information.

• Create Reservations — This wizard guides the user through the process of creating a reservation. A reservation is a means of ensuring the reserve material will be available for a specific date and time in the future. Users can search reserve titles using catalog searches and instructor information and course information searches.

• Display Title Reservations — This wizard displays reservation record(s) for a title. Users can search title reservations using catalog searches, instructor information and course information searches, and job ID search. Once title reservations are identified, the Calendar Options provide the ability to limit the reservations display to a given date range.


• Display User Reservations — This wizard displays reservation record(s) for a specified patron.

• Modify Reservations — This wizard makes changes to the reservation record information. Users can search title reservations using catalog searches, user ID, instructor information and course information searches, and job ID search. Once title reservations are identified, the Calendar Options provide the ability to limit the reservations display to a given date range. Users can modify reservation start and end dates, fixed time slots (if used), the pickup library, and reservation extended information (if used).

• Remove Title Reservations — This wizard removes the reservation record(s) for a title. Users can search title reservations using catalog searches, instructor information and course information searches, and job ID search. Once title reservations are identified, the Calendar Options provide the ability to limit the reservations display to a given date range. Users have the option of removing individual reservations records or all reservations records at once.

• Remove User Reservations — This wizard removes one or more reservations made by the specified patron. Once patron reservations are identified, the Calendar Options provide the ability to limit the reservations display to a given date range. Users have the option of removing individual reservations records or all reservations records at once.

Additionally, if a user is linked to any reservation records, the Display User wizard in the Circulation wizard group will display a list of a user’s reservations on the Reservations tab.

Academic Reservations Policies

The following policies need to be configured when using Academic Reservations.

• Item Type — For every type of reserved item that can have reservations placed against it, the item's Reservation Profile must be defined in the Item Type policy.

• Reservations Profile — This new policy was added to the WorkFlows Java client. The Reservations Profile policy defines the optional fixed time periods for which reservations can be made, minimum loan periods, expiration time periods, how far in advance reservations can be made on the items, and how much time to allow before the start of a reservation when a loan period must be shortened due to an upcoming reservation.

• Reserve Desk — The Reservations section of the Reserve Desk policy defines when reservations are unavailable. Users can define the default Reserve Desk in the Reserves Session Settings wizard.

• User Profile — The User Profile policy contains the following three reservation related attributes: Reservation Limit, Eligible for Reservation, and Consecutive Reservation Allowed.

• Bill Reason — If users who make reservations are to be billed for the reservation service using the Bill a User wizard, a new Bill Reason policy may need to be created.

For more information about how to use these wizards, see the WorkFlows Java client online Help.

Academic Reserves 23

• Circulation Map — Before a user can make a reservation on an item, there must be a Circulation Map policy that permits charging of that item type by that user's profile and library.

• Circulation Rule — The Circulation Rule policy determines whether the combination of library, user profile, and item type is “chargeable.” If it is “chargeable,” the first test of whether a reservation can be accepted for an item has been passed.

• Library —The Library policy contains a Dates Closed attribute, which impacts Reserve Desks. When making a reservation on a reserved item, the system checks the dates closed of the owning library. If the requested reservation falls within any of the dates listed, the item is said to be “Unavailable for reservations,” and the reservation is not allowed.

Academic Reservations Reports

The following Academic Reservations reports are included in the Reserve report group.

• Count Reservations (Reservationcnt) — Counts reservation records

• List of Reservations (Rsvationlist) — Lists reservation records

• Remove Reservations (Remreservation) — Removes reservation records in batch


The Academic Reservations wizards are configured for the admin and sirsi user access policies only. Administrators will need to review the functionality of these wizards and determine whether or not other to give access to other users.

(UNI-7221, UNI-16794, UNI-16958, UNI-17363, UNI-17364, UNI-17366, UNI-17585, UNI-17747, UNI-17587, UNI-18141, UNI-18339, UNI-18341)

For more information about configuring the Academic Reservations module, see “Getting Started in Academic Reservations” in the WorkFlows Java client online Help.

When Academic Reservations is configured on the library’s system, the Global Configuration policy, Display Booking Profile in Reserves Wizards, is not available. Additionally, the Booking Profile policy values will not display in reserve control records.


Acquisitions 25

Acquisitions

General

Enhancements

Automatic Tax Calculation Enhanced for Tax Included in Invoice Line Amounts

Some vendors send invoices in which the line item amounts include tax. If SirsiDynix Symphony is set up to automatically calculate tax invoice lines, the user should modify the vendor’s vendor record and select the Tax Included in Invoice Line Amounts check box. When the user creates an invoice using the Add Invoice wizard or Add Invoice for Order helper, the invoice inherits the setting of the Tax Included in Invoice Line Amounts check box in the vendor record. As the user adds invoice lines to the invoice, the user is prompted to enter the invoice line amount that includes tax in the Amount Including Tax field. The Amount Including Tax field specifies the vendor final price including tax. SirsiDynix Symphony will do the following when automatically calculating taxes on the invoice line.

• If the tax handling for all of the taxes (Tax1, Tax2, and Tax3) on the invoice line is set to Exempt or Zero Rated, SirsiDynix Symphony does not add any tax invoice lines. The Amount Including Tax field (vendor final price including tax) and the Amount field (vendor final price) will contain the same value.

• If the tax handling for any of the taxes (Tax1, Tax2, or Tax3) is set to Standard or Rebate, SirsiDynix Symphony takes the value in the Amount Including Tax field and determines how much of the amount is the vendor final price and how much is tax and/or a tax rebate. SirsiDynix Symphony then creates Tax/Fund, Tax/Adjust, Rebate/Fund, or Rebate/Adjust invoice lines with the proper tax and tax rebate amounts according to the settings in the Acquisitions Session Settings wizard and policies.

When X12 invoice information is loaded using the Book X12 Invoices (Bookinvoicex12) report and the Serials X12 Invoices (Serinvoicex12) report, tax invoice lines are not created automatically in the loaded invoices if the vendor includes tax in the invoice line amounts. The following message displays in the report log.

Tax lines cannot be loaded for a tax included vendor.

The user must edit the loaded invoices and manually add tax and tax rebate invoice lines and adjust the Amount and Amount Including Tax fields in the invoice lines.



Some vendors send invoices in which the line item amounts include tax. If SirsiDynix Symphony is set up to automatically calculate tax invoice lines, edit the vendor’s vendor record to select the Tax Included in Invoice Line Amounts check box. As the user adds invoice lines to the invoice, the user is prompted to enter the invoice line amount that includes tax in the Amount Including Tax field. SirsiDynix Symphony automatically calculate taxes on the invoice line according to the tax handling settings for Tax1, Tax 2, and/or Tax 3 on the invoice line.

If the library wants to use the Tax Included feature, the system administrator must go to the Global Configuration wizard, select the Acquisitions tab, and set the Tax Included in Invoice Line Amount setting to Use Tax Included in Invoice Amount. By default, Do Not Use Tax Included in Invoice Line Amount is selected so the Tax Included in Invoice Line Amount feature is disabled in Acquisitions.

(UNI-20219) (UNI-20006) (UNI-20080) (UNI-21539)

Wizard and Helper Property Changes for Taxes Paid to a Vendor

The Vendor wizards have been enhanced with new fields to specify whether taxes are paid to a vendor for ordered materials, whether the vendor has a tax exempt status, and whether tax is to be included in item amounts on invoice lines. The tax settings are stored in the vendor record, and are inherited by the invoice.

Tax Field Defaults Added to the Add Vendor Wizard Properties

The Add Vendor wizard properties now include default settings for certain tax-related fields. The following fields have been added to the Defaults tab of the Add Vendor wizard properties.

• Tax Paid to Vendor – Specifies whether taxes on ordered materials are paid directly to the vendor by default. Select this check box if taxes are to be paid to the vendor. Clear this check box if taxes are to be paid to a government agency.

• Tax Exempt Vendor – Specifies whether the vendor has a tax exempt status. If a vendor has a tax exempt status, materials ordered from the vendor are not subject to taxes. Select this check box if materials ordered from this vendor are not subject to taxes. Clear this check box if materials ordered from the vendor are subject to taxes.

• Tax Included in Invoice Line Amount – Specifies if taxes on ordered materials are included in the amount on invoice lines. Select this check box to include taxes in the invoice line amounts by default. Clear this check box to not include taxes in the invoice line amounts by default.

Acquisitions 27

Vendor Information Tab Includes Tax Fields

The Vendor Information tab that displays in various Acquisitions wizards has been enhanced to include fields to indicate if taxes are paid to a vendor.

• Tax Paid to Vendor – Specifies whether taxes on ordered materials are paid directly to the vendor.

• Tax Exempt Vendor – Specifies whether the vendor has a tax exempt status. If a vendor has a tax exempt status, materials ordered from the vendor are not subject to taxes.

• Tax Included in Invoice Line Amount – Specifies if taxes on ordered materials are included in the amount on invoice lines.

The tax fields on the Vendor Information tab can be modified in the following wizards.

• Add Vendor

• Duplicate Vendor

• Modify Vendor

The tax fields display on the Vendor Information tab in the following wizards, and cannot be modified.

• Add Vendor Cycle

• Delete Vendor

• Display Vendor (All Cycles)

• Display Vendor (Specific Cycle)

Tax Paid to Vendor Property Removed from the Add Invoice Wizard and Add Invoice for Order Helper

Previously, the default value used for the Tax Paid to Vendor flag when creating an invoice was set in properties for the Add Invoice wizard and the Add Invoice for Order helper. The Tax Paid to Vendor setting used when creating an invoice is now taken from the Tax Paid to Vendor field in the vendor record. The Tax Paid to Vendor property has been removed from the default properties for the Add Invoice wizard and the Add Invoice for Order helper.


The Vendor wizards have been enhanced with new fields to specify whether taxes are paid to a vendor for ordered materials, whether the vendor has a tax exempt status, and whether tax is to be included in item amounts on invoice lines. The tax settings are stored in the vendor record, and are inherited by the invoice.

Previously, the default value used for the Tax Paid to Vendor flag when creating an invoice was set in properties for the Add Invoice wizard and the Add Invoice for Order helper. The Tax Paid to Vendor setting used when creating an invoice is now taken from the Tax Paid to Vendor field in the vendor record. The Tax Paid to Vendor property has been removed from the default properties for the Add Invoice wizard and the Add Invoice for Order helper.


The Add Vendor wizard properties now include default settings for certain tax-related fields. The following fields have been added to the Defaults tab of the Add Vendor wizard properties.

• Tax Paid to Vendor – Specifies whether taxes on ordered materials are paid directly to the vendor by default.

• Tax Exempt Vendor – Specifies whether the vendor has a tax exempt status. Materials ordered from a tax exempt vendor are not subject to taxes.

• Tax Included in Invoice Line Amount – Specifies if taxes on ordered materials are included in the amount on invoice lines.

SirsiDynix Symphony administrators should evaluate the Add Vendor wizard properties and determine the appropriate default settings to use.

(UNI-18267,UNI-18279)

Vendor Records, Vendor Wizards, Invoice Records, and Invoice Wizards Enhanced to Handle Vendors with a Tax Exempt Status

Vendor records and invoice records have been enhanced to include the Tax Exempt Vendor setting to specify whether the vendor has a tax exempt status. If a vendor has a tax exempt status, materials ordered from the vendor are not subject to taxes. When an invoice is created, the Tax Exempt Vendor field on the Invoice tab of the invoice inherits the value of the Tax Exempt Vendor setting in the vendor record. If the vendor has a tax exempt status, no tax or tax rebate lines will be added to the invoice, and tax or tax rebate invoice lines cannot be added manually to the invoice with the Add Invoiceline tool or Add Invoice Lines wizard.

Enhanced Wizards

The Tax Exempt Vendor field display on the Vendor Information tab in the following Vendor wizards.

• Add Vendor

• Add Vendor Cycle

• Display Vendor (All Cycles)

• Display Vendor (Specific Cycle)

• Duplicate Vendor

• Modify Vendor

The Tax Exempt Vendor field displays on the Invoice tab in the following Invoice wizards.

• Add Invoice

• Add Invoice Lines

• Delete Invoice

• Display Invoice

• Modify Invoice

Acquisitions 29

• Pay Invoice

• Reverse Payment of Invoice

• Unlock Invoice

Effects of Changing a Vendor’s Tax Exemption Status

If a vendor’s tax exemption status changes, users can edit the setting of the Tax Exempt Vendor field using the Modify Vendor wizard and the Modify Invoice wizard. SirsiDynix Symphony adjusts invoices as follows.

• If the Tax Exempt Vendor setting is changed in the vendor record, existing invoices are not affected.

• If the Tax Exempt Vendor setting is changed in the invoice from Y (yes) to N (no), and the Invoice Tax feature is configured to calculate taxes automatically, tax and tax rebate invoice lines will be automatically added to the invoice.

• If the Tax Exempt Vendor setting is changed in the invoice from N (no) to Y (yes), and the invoice contains tax and (if applicable) tax rebate lines, all tax and tax rebate lines are removed from the invoice. The invoice totals are recalculated, and funds originally specified in the tax and tax rebate lines are adjusted. The user will be prompted to confirm the removal of the tax and tax rebate lines before the invoice is modified.

Message Warns of Vendor Tax Exemption Conflicts

If the Tax Exempt Vendor check box is selected in the Vendor Information tab when a vendor record is created or modified, or in the Invoice tab when the invoice is created or modified, the following message displays if the Tax Paid to Vendor check box and/or the Tax Included in Invoice Line Amounts check box is also selected, and the user tries to save the vendor record or the invoice.

The vendor tax exemption conflicts with other vendor tax fields.

If the Tax Exempt Vendor check box is selected in the vendor record or in the invoice, the Tax Paid to Vendor check box and the Tax Included in Invoice Line Amounts check box must be cleared because they do not apply to a vendor who supplies ordered materials that are exempt from taxes.

If the Tax Exempt Vendor check box is cleared (meaning the materials ordered from the vendor are subject to taxes) in the vendor record or in the invoice, then the Tax Paid to Vendor check box and/or the Tax Included in Invoice Line Amounts check box can be selected.


Vendor records and invoice records have been enhanced to include the Tax Exempt Vendor setting to specify whether the vendor has a tax exempt status. If a vendor has a tax exempt status, materials ordered from the vendor are not subject to taxes. When an invoice for a tax exempt vendor is created, no tax lines will be added to the invoice, and tax invoice lines cannot be added manually to the invoice with the Add Invoiceline tool or Add Invoice Lines wizards.


If the library wants to use the Tax Exempt Vendor feature, the system administrator must go to the Global Configuration wizard, select the Acquisitions tab, and set the Vendor Tax Exemptions setting to Use Vendor Tax Exemptions. By default, Do Not Use Vendor Tax Exemptions is selected so the Tax Exempt Vendor feature is disabled in Acquisitions.

(UNI-18256) (UNI-19721) (UNI-20079) (UNI-21539)

Material Type Field and Default Property Added to Order Wizards to Specify an Acquisitions Material Type for Orderlines

The Order Information and Maintenance wizards have been enhanced with the Material Type field, which has been added to the Orderline tab in the wizards. The Material Type field is optional, and allows the user to select an acquisitions material type to be associated with the orderline. Specifying an acquisitions material type is useful when running reports and selecting orders or orderlines by an item’s material characteristics.

The available selections in the Material Type list are defined with the Acquisitions Material Type wizard on the Configuration toolbar.

In the following wizards, the Material Type field displays under Orderline Information on the Orderline wizard tab.

• Add Basic Order

• Add Dated Order

• Add Recurring Order

• Add Orderlines

• Duplicate Order

• Modify Order

In the following wizards, the Material Type field displays under Bibliographic Info on the Orderline wizard tab.

• Display Order

• Delete Order

Certain Order Information and Maintenance wizards have been enhanced with the Material Type default wizard property. The property is on the Defaults tab, and is blank by default. Users can set the default acquisitions material type by selecting an Acquisitions Material Type policy name from the Material Type list. The following wizards have the Material Type property.

• Add Basic Order

• Add Dated Order


• Add Orderlines

Acquisitions 31


Certain Order Information and Maintenance wizards have been enhanced with the Material Type default wizard property. The Material Type field is optional, and allows the user to select an acquisitions material type to be associated with the orderline. The property is on the Defaults tab, and is blank by default. System administrators should evaluate the new wizard property and determine the appropriate default setting, if any.

Use the Acquisitions Material Type wizard on the Configuration toolbar to define the policy selections that will display in the Material Type wizard property list and in the Material Type field in the Order Information and Maintenance wizards.

The following wizards have been enhanced with the Material Type property.

• Add Basic Order

• Add Dated Order


• Add Orderlines

(UNI-18283)

Corrections

When Busy, Server Can Be Configured to Retry Acquisitions Transactions Automatically

The SirsiDynix Symphony server can now be configured to retry transactions when receiving the ‘records in use’ message in the following wizards.

• Receive orders

• Add ordered items to catalog

• Editing orders

• Add invoice line

• Pay invoice

The ‘records in use’ message occurs when there are a large number of orders associated with a relatively small number of vendors.

SirsiDynix Symphony System Administrator Note

If you are getting these ‘records in use’ messages with the listed wizards, please contact SirsiDynix Client Care to configure the ability to retry transactions.

(UNI-22937, UNI-21707)


Receive Orders Wizard

Enhancements

Acquisitions Workslip Printing Added to Receive Orders Wizard

The Receive Orders wizard can now print acquisitions workslips when one or more orderlines are received. The Workslip Printing options in the Receive Orders wizard properties determine when an acquisitions workslip should print. The workslip options are as follows.

• Do Not Print Workslips – Does not print a workslip when orderlines are received. This option is selected by default.

• Print a Workslip When Receiving Orderlines with Holds and/or Extended Information – Prints a workslip when any selected orderline being received either has one or more active holds or any level or range, and/or the orderline contains extended information to print on the workslip.

• Always Print a Workslip When an Orderline is Received – Prints a workslip when Receive Orderline is selected to receive a single orderline, or when Receive Selected Orderlines is selected in the receiving tree.

SirsiDynix System System Administrator Notes

The Receive Orders wizard can now print acquisitions workslips when one or more orderlines are received. The Workslip Printing options in the Receive Orders wizard properties determine when an acquisitions workslip should print. SirsiDynix Symphony administrators should evaluate the Workslip Printing options and determine which option is appropriate for the library. (UNI-17256)

Session Settings Wizard

Enhancements

Maximum Number of Segments to Display in the View Pane Increased to 200 Segments

In the Session Setting Wizard for Acquisitions and Selections Lists, the Number of Segments to Trigger Display of Single Selected Segment in Viewer Pane property had a maximum value of 100 to limit the number of segments that can display simultaneously in the view pane of the Segments interface. The maximum value has been changed to 200 to display all segments for orderlines with as many as 199 segments.

While the maximum value has been changed, the delivered property default value remains at 100.

Acquisitions 33


To experiment with the new limit of how many segments can display in the viewer pane at one time, go to the Acquisitions Session Settings wizard, and increase the value in Number of Segments to Trigger Display of Single Selected Segment in Viewer Pane field.

(UNI-22081)

Added Setting to Prompt Before Cancelling On-Order Holds

The Session Settings wizard has been enhanced with the Prompt for Confirmation Before Cancelling On-Order Holds property.

Previously, if SirsiDynix Symphony was configured to allow holds to be placed on ordered items, and the global property to automatically cancel on-order holds when orders for materials on hold are changed or removed was selected, the on-order holds were made inactive without warning the user. With the Prompt for Confirmation Before Cancelling On-Order Holds property, the following message prompt displays if an orderline with holds is removed or modified such that the holds are about to be cancelled automatically.

On-order holds will be cancelled. Proceed?

If the user selects OK to confirm the hold cancellation, the orderline is removed or modified, and the on-order holds are cancelled. If the user selects Cancel, the orderline is not removed or modified, and the on-order holds are not cancelled.

(UNI-16919)


The Session Settings wizard has been enhanced with the Prompt for Confirmation Before Cancelling On-Order Holds property.

Previously, if SirsiDynix Symphony was configured to allow holds to be placed on ordered items, and the Automatically Cancel On-Order Holds When Order For Material On Hold is Changed/Removed global property was selected, the on-order holds were made inactive without warning. With the Prompt for Confirmation Before Cancelling On-Order Holds property, the following message prompt displays if an orderline with holds is removed or modified so that the holds are about to be cancelled automatically.

On-order holds will be cancelled. Proceed?

If the user selects OK to confirm the hold cancellation, the orderline is removed or modified, and the on-order holds are cancelled. If the user selects Cancel, the orderline is not removed or modified, and the on-order holds are not cancelled.


By default, the Prompt for Confirmation Before Cancelling On-Order Holds property is selected.

(UNI-16919)

The Prompt for Confirmation Before Cancelling On-order Holds property displays in the Acquisitions Session Settings only if SirsiDynix Symphony is configured to allow holds to be placed on materials on order, and if the Automatically Cancel On-Order Holds When Order For Material On Hold is Changed/Removed global property is selected in the Global Configuration wizard.

Cataloging Wizards 35

Cataloging Wizards

General

Enhancements

Formats Updated to Reflect Changes in the MARC 21 Cataloging Standard

The SirsiDynix Symphony formats were updated to reflect changes in the MARC 21 cataloging standard. These changes include updates to the bibliographic, authority, holdings, and community information formats.

Bibliographic Format Changes

The following changes were made to the SirsiDynix Symphony bibliographic formats for the changes to the MARC 21 formats for bibliographic data.

• In the 007 field (Videorecording), character position 04 (Videorecording Format) now includes a new code, s, for Blu-ray Disc.

• In the 008 field (Books), character position 24 (Nature of Contents), and in the 006 field (Books), character position 07 (Nature of Contents), the following new codes have been added.

Only new installations will receive the entire set of format changes in the SirsiDynix Symphony installation.

For existing sites, the SirsiDynix Symphony 3.3 upgrade will update only the fixed fields (006, 007, and 008 fields) in the formats. For all of the remaining format changes, existing sites will need to modify their bibliographic, authority, holding, and community information formats to match the changes to the MARC 21 cataloging standard.

If existing sites had customized field labels and values in the fixed fields, system administrators should review the formats and fix the customization, if necessary, after the upgrade to SirsiDynix Symphony 3.3 is complete.

For more information about the MARC 21 catalog standard changes, go to the MARC 21 information page in the Library of Congress web site at http://www.loc.gov/marc.

Code LC Description

2 Offprints

5 Calendars

6 Comics/Graphic Novels


• In the 008 field (Continuing Resources), character position 24 (Nature of Entire Work), and in the 006 field (Continuing Resources), character position 07 (Nature of Entire Work), the following new codes have been added.

• In the 008 field (Continuing Resources), character positions 25 through 27 (Nature of Contents), and in the 006 field (Continuing Resources), character positions 08 through 10 (Nature of Contents), the following new codes have been added.

• In the 008 field (Books), character position 33 (Literary Form), the code c (Comic Strips) is obsolete.

• In the 008 field (Continuing Resources), character positions 24 through 27, the code h (Handbooks) is obsolete.

• The 017 field (Copyright or Legal Deposit Number) now includes the new subfield z, Canceled/Invalid Copyright or Legal Deposit Number.

• The 041 field (Language Code) has a new first indicator (Translation Indication) of a blank space, for No Information Provided.

• The 082 field (Dewey Decimal Classification Number) has two new subfields.

• The 083 field has been added for Additional Dewey Decimal Classification Number. The first indicator (Type of Edition) has the following indicators.

The second indicator (Undefined) has a blank space, for Undefined.

Code LC Description

2 Offprint

5 Calendars


Code LC Description

2 Offprint

5 Calendars


Code LC Description

m Standard or Optional Designation

The following codes are used: a (Standard) and b (Optional).

q Assigning Agency

Code

LC Description

0 Full Edition

1 Abridged Edition


The 083 field has the following subfields.

• The 085 field has been added for Synthesized Classification Number Components. The first indicator (Undefined) has a blank space, for Undefined.



Code LC Description

a Classification Number

c Classification Number--Ending Number of Span



q Assigning Agency

y Table Sequence Number for Internal Subarrangement or Add Table

z Table Identification

2 Edition Number

6 Linkage

8 Field Link and Sequence Number

Code LC Description

a Number Where Instructions are Found -Single Number or Beginning Number of Span

b Base Number

c Classification Number -Ending Number of Span

f Facet Designator

r Root Number

s Digits Added From Classification Number in Schedule or External Table

t Digits Added From Internal Subarrangement or Add Table

u Number Being Analyzed

v Number in Internal Subarrangement or Add Table Where Instructions are Found

w Table Identification - Internal Subarrangement or Add Table

y Table Sequence Number for Internal Subarrangement or Add Table

z Table Identification

6 Linkage



• The 440 field (Series Statement/Added Entry-Title) is now obsolete. The field remains in the SirsiDynix Symphony catalog formats until OCLC makes a final decision on how these fields should be converted. The catalog format tooltips will now say “Obsolete” for this field.

• In the 490 field (Series Statement), the first indicator (Series Tracing Policy) now has the following indicators.


The 490 field has a new subfield, 3, for Materials Specified.

• The 502 field (Dissertation Note) has the following new subfields.

• The 534 field (Original Version Note) has the new subfield, o, for Other Resource Identifier.

• The 542 field has been added for Information Relating to Copyright Status. The first indicator (Privacy) has the following indicators.



Code LC Description

0 Series Not Traced

1 Series Traced (series traced in 8XX field)

Code LC Description

b Degree Type

c Name of Granting Institution

d Year Degree Granted

g Miscellaneous Information

o Dissertation Identifier

Code LC Description

<blank space> No Information Provided

0 Private

1 Not Private

Code LC Description

a Personal Creator

b Personal Creator Death Date

c Corporate Creator

d Copyright Holder

e Copyright Holder Contact Information


• In the 800 field (Series Added Entry - Personal Name), the 810 field (Series Added Entry - Corporate Name), the 811 field (Series Added Entry - Meeting Name), and the 830 field (Series Added Entry - Uniform Title), the following subfields have been added.

• The 882 field has been added for Replacement Record Information. The first indicator (Undefined) has a blank space, for Undefined.



f Copyright Statement

g Copyright Date

h Copyright Renewal Date

i Publication Date

j Creation Date

k Publisher

l Copyright Status

m Publication Status

n Note

o Research Date

q Supplying Agency

r Jurisdiction of Copyright Assessment

s Source of Information

Code LC Description

x International Standard Serial Number

3 Materials Specified

Code LC Description

a Replacement Title

i Explanatory Text

w Replacement Bibliographic Record Control Number

6 Linkage



Authority Format Changes

The following change was made to the SirsiDynix Symphony authority formats for the change to the MARC 21 formats for authority data.

The 083 field (Dewey Decimal Classification Number) has a new subfield, y, for Table Sequence Number for Internal Subarrangement or Add Table.

Holdings Format Changes

The following changes were made to the SirsiDynix Symphony holdings formats for the changes to the MARC 21 formats for holdings data.

• In the 007 field (Videorecording), character position 04 now includes a new code, s, for Blu-ray Disc.

• The 017 field has been added for Copyright or Legal Deposit Number. The first indicator (Undefined) has a blank space, for Undefined.

The second indicator (Display Constant Controller) has the following indicators.


Code LC Description

<blank space> Copyright or Legal Deposit Number

8 No Display Constant Generated

Code LC Description

a Copyright or legal deposit number

b Assigning agency

d Date

i Display text

z Canceled/invalid copyright or legal deposit number

2 Source

6 Linkage

8 Field link and sequence number


Community Information Format Changes

The following changes were made to the SirsiDynix Symphony community information formats for the changes to the MARC 21 formats for community information.

• The 041 field (Language Code) has a new first indicator (Translation Indication) of a blank space, No Information Provided.

• The 082 field (Dewey Decimal Classification Number) has two new subfields.

• The 440 field (Series Title) is now obsolete. The field remains in the SirsiDynix Symphony catalog formats until OCLC makes a final decision on how these fields should be converted. The catalog format tooltips will now say “Obsolete” for this field.

(UNI-20047, UNI-22140)


The SirsiDynix Symphony formats have been updated to reflect changes in the MARC 21 cataloging standard. These changes include updates to the bibliographic, authority, holdings, and community information formats.

Code LC Description



q Assigning Agency

Only new installations will receive the entire set of format changes in the SirsiDynix Symphony installation.

For existing sites, the SirsiDynix Symphony 3.3 upgrade will update only the fixed fields (006, 007, and 008 fields) in the formats. For all of the remaining format changes, existing sites will need to modify their bibliographic, authority, holding, and community information formats to match the changes to the MARC 21 cataloging standard. See “FAQs: Working with Formats” in the WorkFlows Java client online Help for information about modifying formats.

If existing sites had customized field labels and values in the fixed fields, system administrators should review the formats and fix the customization, if necessary, after the upgrade to SirsiDynix Symphony 3.3 is complete.

For more information about the MARC 21 catalog standard changes, go to the MARC 21 information page in the Library of Congress web site at http://www.loc.gov/marc.


To add new entries to a format policy, the administrator must first check the Entry ID policy list within a format to see if the entry is available. If not, the administrator will need to create a new Entry ID policy. This new entry ID should now be added to the format. To create an Entry ID Policy, use the Entry ID policy helper. See the Entry ID policy helper topic in the WorkFlows Java client online Help.

To add an entry ID to a format, see the “Entries Tab for the Format Policy” topic in the WorkFlows Java client online Help. This topic describes the fields required when adding an entry to a format policy. For each entry ID, sub-tabs such as Basic, Display, and Punctuation display fields to be completed based on the purpose of the format. After adding an entry to a format, the administrator must halt and run the workstation server for format changes to appear.

Following sections of this system administrator note describe the exact changes that the SirsiDynix Symphony 3.3 upgrade will make to fixed fields in the bibliographic formats and holdings formats.

Changes to Fixed Fields in the Bibliographic Format

For existing sites, the SirsiDynix Symphony 3.3 upgrade will make the following changes to the 006, 007, and 008 fixed fields in bibliographic formats.

• In the 007 field (Videorecording), character position 04 (Videorecording Format) now includes a new code, s, for Blu-ray Disc.

• In the 008 field (Books), character position 24 (Nature of Contents), and in the 006 field (Books), character position 07 (Nature of Contents), the following new codes have been added.

• In the 008 field (Continuing Resources), character position 24 (Nature of Entire Work), and in the 006 field (Continuing Resources), character position 07 (Nature of Entire Work), the following new codes have been added.

Code LC Description

2 Offprints

5 Calendars


Code LC Description

2 Offprint

5 Calendars



• In the 008 field (Continuing Resources), character positions 25 through 27 (Nature of Contents), and in the 006 field (Continuing Resources), character positions 08 through 10 (Nature of Contents), the following new codes have been added.

• In the 008 field (Books), character position 33 (Literary Form), the code c (Comic Strips) is obsolete.

• In the 008 field (Continuing Resources), character positions 24 through 27, the code h (Handbooks) is obsolete.

Changes to Fixed Fields in the Holdings Format

For existing sites, the SirsiDynix Symphony 3.3 upgrade will make the following change to the 007 fixed field in bibliographic formats.

In the 007 field (Videorecording), character position 04 now includes a new code, s, for Blu-ray Disc.

(UNI-20047, UNI-22140)

Added Automatic Printing of Labels Using Default Label Templates of Specific Library/Item Type Combinations

Cataloging wizards can now be configured to automatically print a book or spine label using a label template specifically defined for a library/item type combination. For example, when the cataloger searches for a title and adds a new item for the MAIN item library with an item type of BOOK, the cataloging wizards can be configured to automatically print a book or spine label and use a label template specifically defined for MAIN/BOOK. If no label template profile is found for the particular library/item type combination, the label will not be printed, and the cataloging wizard will display a message.

A new behavior property was added to the Add Item, Add Title, Call Number and Item Maintenance, and Duplicate Title wizards. If the Print Labels for New Items behavior is selected, the Use Label Template Profiles behavior becomes available. If selected, the wizard will use the label template assigned for this library/item type combination found in the Label Template Profiles Map policies. This property applies to both the Automatically and Print Preview options.

The cataloging label templates for specific library/item type combinations are defined using the new Label Template Profiles Map wizard on Configuration toolbar under Cataloging Configuration. For more information about this wizard, see the release note in the System Configuration section.

Code LC Description

2 Offprint

5 Calendars




The new Use Label Template Profiles behavior property is delivered for the Add Item, Add Title, Call Number and Item Maintenance, and Duplicate Title wizards with the Version 3.3 upgrade. The SirsiDynix Symphony Administrator should review this new Label Template Profile feature and determine whether or not the behavior property should be configured for these wizards and which users should have access to this feature. The Administrator must first define label template profiles using the new Label Template Profiles Map wizard on the Configuration toolbar under Cataloging Configuration.

(UNI-15609)

Label Designer Sample Templates Are Now Delivered with the Version 3.3 Upgrade

Previously, only new installations of SirsiDynix Symphony received the Label Designer sample templates when their systems were configured. Now, the following Label Designer templates are delivered with the Version 3.3 upgrade:

• SirsiDynixSampleBibTemplate - bibliographic template

• SirsiDynixSampleItemBarcode - barcode template

• SirsiDynixSamplePatronLibCard - user template

• SirsiDynixSamplePatronMailLbl - user template


The Label Designer templates will be copied to the /Unicorn/Config/LabelDesigner on upgrade. Should the system already have one of these templates, they will not be overwritten or updated during the upgrade. (UNI-16210)

Global Call Number Modification Wizard

Enhancements

New Global Call Number Modification Wizard

The new Global Call Number Modification wizard allows the cataloger to update one or more call number records for a title at the same time using either interactive or report mode. The same modifications can be made to more than one call number of a title more efficiently using this wizard.

For more information about how this wizard modifies call numbers, prefixes, and call number analytics, see the “FAQs: Modifying Call Numbers Using the Global Call Number Modification Wizard” and the “Global Call Number Modification Wizard” topics in the WorkFlows Java client online Help.


How the New Wizard Works

With the Global Call Number Modification wizard, the cataloger can update some or all call numbers of a title. The wizard contains properties that allow the cataloger to set default values for fields that can be modified, set the default update modes, prompt for library when selecting call numbers, control whether or not call number analytics can be modified, and prompt for confirmation before modifying call numbers.

In the Global Call Number Modification wizard, after the cataloger searches a title to modify, the Modify Call Number and Modify Call Number Prefix options display. The cataloger can select only one option.

• Modify Call Number — If selected, the cataloger can type the new base call number and new call number analytic, or leave these fields blank to leave the base call number and/or analytic unchanged. The cataloger can also delete the analytic. The cataloger is able to select a new class scheme or shadow status, or he can select Will Not Be Modified to leave the class scheme and/or shadow status unchanged.

• Modify Call Number Prefix — If selected, the Prefix box will display, with three options for modification: Add, Replace, and Delete. The call number prefix is defined as all characters preceding the first space in the base call number. For example, in the call number Fic SMITH, the characters Fic will be selected as the prefix. But, it also means that in the call number PZ3.F456, the characters PZ3 will be selected as the prefix since there is a space following the 3. If no space is found in the base call number, the call number will not be modified. For example, the call number PZ3.F456 would not be modified. Leading spaces in a call number are ignored when selecting the prefix.

When the cataloger selects a title to modify, the Call Number tree for the title will display in the wizard View pane. The cataloger can select the check boxes next to the call numbers to be modified or select the main title mode so that all check boxes are selected. (Check boxes can be cleared by selecting them again.)

Under Update Options in the top pane, the cataloger can click Interactive if these changes should be made in interactive mode or click Report to make changes in report mode (a batch report will be submitted). If the cataloger selects Report, he can elect to first run the report in Test mode.

After clicking Modify, the cataloger will see the following.

• If Interactive mode was selected, the call numbers will be modified, and a new window will open displaying the results of modifications in a table format. Call numbers that cannot be changed will display “Failed” in the Status column and the failure reason will display in the Reason column. Highlighting a call number in the table will also display details of how the call number was modified in the View pane below the table. If not satisfied with these changes, the cataloger has the option to reset the call number values and modify the call numbers again.

Note: The Reset next step button does not un-do the changes made to the call numbers; it simply returns the cataloger to the modify screen so that additional changes can be made without having to search for the same title and set of call numbers again.


• If more than 100 call numbers are selected to modify using the Interactive mode, the wizard will display a message that, depending on system performance, it may be best to submit these changes in Report mode.

• If Report mode was selected with the Test option, the call numbers will not actually be updated. The cataloger can review the test results using the Review Call Number Modification helper. If running the Report mode without the Test option selected, the modifications will be submitted as a batch report, and the databases will be updated. The cataloger can review the results of this report using the Review Call Number Modification Report helper.

Review Call Number Modification Report Helper

The Review Call Number Modification Report helper allows the cataloger to view the results of call number modifications when using the Global Call Number Modification wizard in Report mode. The cataloger can also use this helper to review the test results when using the Test option of the Report mode.

With this helper, the cataloger can display the list of reports run by the Global Call Number Modification wizard. The cataloger can view, print, email, or remove any of the listed reports. Before viewing the report, the cataloger can select formatting options. The report name will be Edit Call Number: followed by the title of the record modified, for example Edit Call Number: Gone with the wind. The reports will display a list of call numbers modified, the modifications selected, the status of the call number, and reason (if the call number was not modified).


The Global Call Number Modification wizard is delivered for the sirsi and admin logins with the Version 3.3 upgrade. Administrators will need to review the features of this new wizard and add the wizard to the User Access Lists for other users who should have access. Since this is a very powerful wizard that makes global changes to the database, administrators should carefully consider who should have access to this wizard. (UNI-15143, UNI-15811, UNI-15812, UNI-15813, UNI-16218, UNI-16231, UNI-16216, UNI-16228, UNI-16224, UNI-16507, UNI-16773, UNI-16580)

If the resulting call number is too long (more than 40 characters), the call number will not be modified and reported as not modified.

Users can only edit call numbers for libraries in their Call Number Maintenance library group.

Circulation 47

Circulation

General

Enhancements

New User Name Fields

In Version 3.3, the user name has been expanded to include the following new fields:

• First name (maximum 20 characters)

• Preferred name (maximum 20 characters)

• Middle name (maximum 20 characters)

• Last Name (maximum 60 characters)

• Suffix (maximum 10 characters)

User Search and the User Search helper have been modified to search on the data in any of these name fields (except for Suffix). Wizards, tabs, and helpers have been modified to display the new fields, and user load reports and programs have also been updated.

When sites upgrade to Version 3.3, these new user fields will be added to the user records. The User Name field will be renamed “Last Name,” and the previous user name data will populate this new Last Name field. After the Version 3.3 upgrade, sites will need to run the new Refactor User Name report which will convert the user name data in the Last Name field and populate the new First Name, Middle Name, and Suffix fields. (The Preferred Name field will not be populated because it is a brand new field for SirsiDynix Symphony.)

Since the existing User Name field is converted to the Last Name field in Version 3.3, the user name will still display correctly in the WorkFlows C client or any older client that does not have the new fields First Name, Middle Name, and Suffix. If the user record only has information in the Last Name field (for example, the name has not been refactored or pieces moved to the new name fields) then the User Name field can be edited with the WorkFlows C client or older client. However, once the name in the user record has been refactored or the pieces moved to the new fields, library staff will no longer be able to edit the name for that particular user record in the WorkFlows C client (or any other client that does not contain the new name fields).


New Report for Converting User Name Field in Existing User Records

Using the Refactor User Name report, sites can populate the user records in the SirsiDynix Symphony user database that contain no data in the First Name, Middle Name, and Suffix fields.

The Refactor User Name report will create two finished reports.

• Refactor User Name (default report title) — This report will list the user records that are selected for User Name field reformatting. The report output will contain the original user’s name and ID and an example of how the name will be converted to the First Name, Middle Name, Last Name, and Suffix fields.

• Refactor User Name (unknown name formats) — This report will list all the selected user records that have an unrecognized user name format. Library staff can use this report to manually adjust user records that the report cannot reformat. The report output will contain the user’s name and ID.

When the report is run in the Update Database Records mode, the original user name will be saved in the Extended Information field of the user record.

This report can be run in test mode, where the user databases are not updated, but the report will list the user records selected for update and an example of how the user name will be updated.

New User Name Display Configuration Option

The SirsiDynix Symphony system can now be configured to display the user name in the WorkFlows and e-Library clients in one of two ways:

• Last Name, Suffix, First Name, Middle, Title (default setting)

• Title, First Name, Middle Name, Last Name, Suffix

If the specific name fields are not populated, these fields will not display. If the Use Preferred Name option is selected in the user record, the user’s preferred name will display instead of the first name.

For example, by default, the user name display setting is Last Name, Suffix, First Name, Middle, Title. A user name appears in the clients as follows:

Blankenship, Jr., Jess Allen (Mr.)

If the user name display configuration option is set to Title, First Name, Middle Name, Last Name, Suffix, the user name will appear in the clients as follows:

The Refactor User Name report will only update user records that do not contain data in any of the First Name, Middle Name, and Suffix fields.

For more information see the Reports section of this document and the WorkFlows Java client online Help.

Contact SirsiDynix Client Care to change the user name display default.

Circulation 49

Mr. Jess Allen Blankenship Jr.

Changes to the WorkFlows Wizards

The following changes have been made to the WorkFlows Java client wizard and helper displays.

• In the user wizards and helpers (Copy User, Modify User, and Register New User) the Basic Info tab displays the new name fields. Additionally, there is a Use Preferred Name field, where library staff can indicate whether or not the user’s preferred name is used (instead of first name) for display in the SirsiDynix Symphony clients and reports.

• In the Offline Register New User wizard, the Basic Info tab displays the new name fields. Additionally, there is a Use Preferred Name field, where library staff can indicate whether or not the user’s preferred name is used (instead of first name) for display in the SirsiDynix Symphony clients and reports.

• All WorkFlows wizards and wizard glossaries that display the user’s name (including Offline WorkFlows wizards) display the new name fields in the order specified in the server configuration.

• In the Copy User wizard and helper, only data in the Last Name field will be copied to the new user record.

• The user name in circulation lists (such as checkout lists, holds lists, and bills lists) will always display as last name, suffix, first name, middle, title.

Changes to the e-Library

The e-Library displays the new user name fields in the order specified in the server configuration. e-Library screens that allow for user registration have been updated with the new user name fields. The user name in circulation lists (such as checkout lists, holds lists, and bills lists) that display in the e-Library will always display as last name, suffix, first name (or preferred name), middle, title. Whether or not the preferred name displays rather than the user’s first name is indicated in the user record.

Changes to the Load Users Report

The Load Users report has been modified to accept the new user record load format which includes the new name fields.

The User Name field is the name field used by pre-Version 3.3 systems. Sites that have user record input files created before the Version 3.3 upgrade can load these files using the updated Load Users report. If the input file contains name data in the User Name field, the data will be loaded into the Last Name field in Version 3.3. If the user record input file has information in the User Name field and also in the Last Name field, the information in the Last Name field will be loaded into the user record.

The user name in circulation lists (such as checkout lists, holds lists, and bills lists) that display in the WorkFlows client will always display as last name, suffix, first name, middle, title.


Changes to Notice Reports

Notices will print user names according to the Use Preferred Name selection in the user record.


When sites upgrade to Version 3.3, these new user fields will be added to the user records. The User Name field will be renamed “Last Name,” and the previous user name data will populate this new Last Name field. After the Version 3.3 upgrade, sites will need to run the new Refactor User Name report which will convert the user name data in the Last Name field and populate the new First Name, Middle Name, and Suffix fields.

Sites that have user record input files created before the Version 3.3 upgrade can still load these files using the Version 3.3 Load Users report. If the input file contains name data in the User Name field, the data will be loaded into the Last Name field. If the user record input file has information in the User Name field and also in the Last Name field, the information in the Last Name field will be loaded into the user record.

Administrators should contact SirsiDynix Client Care if they wish to change the default user name display setting Last Name, Suffix, First Name, Middle, Title to Title, First Name, Middle Name, Last Name, Suffix.

(UNI-16674, UNI-16775, UNI-17260, UNI-17666, UNI-17678, UNI-17679, UNI-17700, UNI-17824, UNI-18727, UNI-18971)

Since the existing User Name field is converted to the Last Name field in Version 3.3, the user name will still display correctly in the WorkFlows C client or any older client that does not have the new fields First Name, Middle Name, and Suffix. If the user record only has information in the Last Name field (for example, the name has not been refactored or pieces moved to the First Name, Middle Name, and Suffix fields) then the User Name field can be edited with the WorkFlows C client or older client. However, once the name in the user record has been refactored or the pieces moved to the new fields, library staff will no longer be able to edit the name for that particular user record in the WorkFlows C client (or any other client that does not contain the new name fields).

Circulation 51

New Circulation Sets Feature

The new Circulation Sets feature allows users to group individual items together to circulate as one set of items.

New Circulation Sets Wizards

The Circulation Sets feature includes new wizards for creating, displaying, maintaining, and removing circulation sets.

The Circulation Sets feature includes the following wizards. These wizards are found in the Maintain Sets group on the Circulation toolbar.

• Add Circulation Sets — This wizard is used to create a circulation set.

• Display Circulation Sets — This wizard is used to display a list of all items contained in a circulation set. If you type a set ID, all the items belonging to the set display.

• Modify Circulation Sets — This wizard is used to change the makeup of a circulation set.

• Remove Circulation Sets — This wizard is used to remove a circulation set.

Circulation Sets Designations

Users can identify the circulation sets as parental or non-parental.

• Parental — A parental circulation set has a separate bibliographic and item record designated as the parent item. When items circulate as part of a parent circulation set, the items are circulated using the same loan period and circulation rule as the parent item.

• Non-parental — A non-parental circulation set does not have a separate bibliographic and item record designated as the parent item. The intent of the non-parental circulation set is to provide a vehicle for bulk processing within the Circulation module. Each item in a non-parental circulation set will circulate using its own circulation rule.

Creating and Maintaining Circulation Sets

When creating and maintaining circulation sets, users need to keep in mind the following:

• Users must group together at least two Item IDs to make a set. As items are added to the set, the Total Parts in Set counter will update with the number of items in the set.

• For each type of circulation set there is a set ID. For parent type circulation sets, the ID of the parent item is the set ID; for non-parental type circulation sets, the set ID is the ID assigned to the set.

Sites interested in using the Circulation Sets functionality should contact SirsiDynix Client Care to configure this feature on their systems.


• When creating circulation sets, if the user selects the Circulate as Set option, items within the set cannot circulate individually; they can only circulate as part of the set. If the Circulate as Set option is not selected, then items within the set can individually circulate.

• An item cannot belong to more than one circulation set. When a set is created or an item is added to a set, the system will check to see if the item already belongs to a set, and if so, prevent the item from being added to the new set.

New Circulation Set Category Wizard

A new policy wizard, the Circulation Set Category wizard, allows users to define categories for the circulation sets. This new policy wizard appears in the Circulation Configuration wizard group. The primary purpose of the Circulation Set Category policy is to establish controlled vocabulary that describes a group's characteristics for reporting purposes.

Searching Circulation Sets

The Item Search and Display wizard, the Item Search in the circulation wizards, and Item Search helper now include the Set ID search option. This search option is available only if the system is configured to use the Circulation Sets feature. When the user selects the Set ID index, Browse and Exact are the only available search options (Keyword is unavailable and appears in grey). The Browse search is selected by default. This search retrieves a list of circulation set names, descriptions, and set types. When the user selects a set name in the search list, the Description tab will display more information about the circulation set, and the Items in Set tab will display a list of the items included in the circulation set.

Circulation Sets and the Circulation Wizards

Circulation sets can be checked out, checked in, renewed, transited, and more using the standard circulation and offline circulation wizards.

• Checkout — Users can check out circulation sets using the Checkout wizard. When a parent type circulation set is checked out, the system checks out the parent item and each of the child items using the circulation map for the parent item (the parent will not circulate on its own). When a non-parent type circulation set is checked out, the system checks out the items associated with the set using the individual items’ circulation rule.

The control record can indicate whether or not items within a set can be checked out individually. If not, the wizard displays a message indicating that the item can only circulate as part of a circulation set and includes the set ID in the message.

When the user scans the item ID of circulation set item that can circulate individually, the Checkout wizard will display a message indicating that the item is part of a circulation set. The user can select to continue with the individual item check out or cancel the check out.

Floating items cannot be included in circulation sets. Items should always belong to the library that owns the set. When creating a circulation set, take care not to select floating items.

Circulation 53

The Checkout wizard has a new behavior property, Checkout All Items Associated with a Set, which allows the user to checkout all items at once, or prompts the user to select items for checkout.

• Renew Item — Users can renew circulation sets using the Renew Item wizard and the renew item function of the Checkout wizard. If a set ID is scanned, the wizard displays the list of items in the set. The user can renew all items or selected items from the list. If a parental type circulation set is renewed, then all items in the set are renewed using the circulation rule of the parent item. If a non-parental circulation set is renewed then all items in the set are renewed using the items’ individual circulation rules.

• Renew User — Users can select the items in the set from the list of checkouts that display in the Renew User wizard.

• Check In/Discharge, Checkin Bookdrop Items, and Fine Free Checkin — Users can check in circulation sets using the Check In /Discharge, Checkin Bookdrop Items, and Fine Free Checkin wizards. These wizards contain a new Behavior property, Discharge All Items Associated With Set, which allows users to discharge the circulation set by scanning the set ID. The user can select to discharge all items in a circulation set with one discharge action or discharge each item separately. Items checked in as a set or part of a set will transit to the circulation set’s owning library set in the circulation set control record, and each item associated with the set and checked in will display in the check in list.

• Check Item Status — Users can check the status of a circulation set using the Check Item Status wizard. When a set ID is scanned, the wizard displays the circulation set status and a list of items that belong to the set with the items’ individual status information.

• Inventory Item — Users can inventory circulation sets using the Inventory Item wizard. When a set ID is scanned, the wizard displays the list of items in the set along with item status information. In this list, the user can select which items in the set are to be inventoried. The wizard will update the inventory counter and the last activity date for these items.

• Receive In Transit Items — Users can receive circulation sets in transit using the Receive In Transit Items wizard by typing or scanning the set ID on the Receive Set tab. This tab will display all received circulation set items.

• Mark Item Missing — Users can mark circulation sets missing using the Mark Item Missing wizard. When a set ID is scanned in the wizard, the wizard displays the list of items in set. In this list, the user can select which items in the set are missing. The wizard will update each selected item’s current location to MISSING.

• Mark Item Lost — Users can mark circulation sets lost using the Mark Item Lost wizard. When a set ID is scanned in the wizard, the wizard displays the list of items in set. In this list, the user can select which items in the set are lost. The wizard will prompt to create a lost bill for each item and update each selected item’s current location to LOST_CLAIM.

• Mark Item Used — Users can mark circulation sets as used using the Mark Item Used wizard. When a set ID is scanned, the wizard displays the list of items in the set along with items status information. In this list, the user can select which items in the set are to be marked for inhouse use. The wizard will update the in use counter and the last activity date for these items.


• Place Hold — Users can place holds on circulation sets using the Place Hold wizard as long as the system is configured to use Demand Management and Blanket Holds. If the system is not configured for these features, and the wishes to place holds on circulation sets, the site should contact SirsiDynix Client Care. In the Place Hold wizard, when the user scans a set ID, the wizard displays a list of items in the circulation set. The user can select items in the set to be placed on hold. When a hold is placed for a circulation set, the system places a blanket level hold. The blanket hold will contain copy level holds for each item in the set. This is to ensure that only items included in the set are pulled to fill the hold. The normal rules for copy level holds will apply; that is, the hold range is not applied to copy level holds.

• Trap Holds — Users can trap holds for circulation sets using the Trap Holds wizard. When a set ID is scanned, the wizard checks for outstanding holds for the set. If there is a hold for the set, the wizard displays a list of items in the set. By default, only available items within the set (not checked out, lost, missing, or intransit) and on hold for the same patron are selected. The user can trap individual set items or select all items to fill the hold.

• Offline — When the user checks out or renews a circulation set in the Offline wizards, he will need to scan each item in the set, and each item will circulate using it’s own circulation rule regardless of the set type. The Load Standalone Transactions report has been modified to load circulation set checkout transactions as individual item checkouts.

Circulation Sets and Collection Exchange

Collection Exchange libraries that want to use Circulation Sets need to be aware that there is a limitation when using this feature. When Circulation Sets is configured, an item can be a member of only one set. In Collection Exchange, an item can belong to both a simple set (“parental” in Circulation Sets) and a boxed set. This is no longer the case once Circulation Sets is configured.

Also, extra configuration steps are required to implement Circulation Sets on systems using Collection Exchange. Sites should contact SirsiDynix Client Care if they wish to use Circulation Sets on systems that also use Collection Exchange.


SirsiDynix Symphony administrators interested in using the Circulation Sets functionality should contact SirsiDynix Client Care to configure this feature on their systems. The new Circulation Sets wizards are delivered for the sirsi and admin logins only. Administrators should review the Circulation Sets wizard functions and determine which user logins should also have access these wizards.

The new Behavior properties for the Checkout wizard, Discharge/Checkin wizard, Check In Bookdrop Items wizard, and Fine Free Discharge/Checkin wizard should be reviewed and set appropriately for the various user logins.

Also, if the site wants to be able to place holds on circulation sets, Demand Management and Blanket Holds must also be configured on the system. Contact SirsiDynix Client Care to configure Demand Management and Blanket Holds.

Circulation 55

Extra configuration steps are required to implement Circulation Sets on systems using Collection Exchange. Sites should contact SirsiDynix Client Care if they wish to use Circulation Sets on systems that also use Collection Exchange.

(UNI-1025, UNI-1075, UNI-1279, UNI-1280, UNI-19253, UNI-19252, UNI-19257, UNI-19259, UNI-19425, UNI-19527, UNI-19454, UNI-19608, UNI-19621, UNI-19630, UNI-19697, UNI-19707, UNI-19708, UNI-19712, UNI-19724, UNI-19935, UNI-19976, UNI-20129)

Reorder Hold Queue Wizard

Enhancements

New Wizard for Reordering Holds in the Hold Queue

The new Reorder Hold Queue wizard allows the user to re-order the hold queue for a title and move a hold or group of holds up or down in the queue. Only unavailable/active holds (including suspended unavailable/active holds) can be reordered by this wizard.

After the user identifies a title for hold queue reordering, the wizard displays a table of the unavailable/active holds for the title. (By default, title level holds display.) For each hold in the queue, the table lists the hold priority, position, patron information, status, when placed, pickup information, and more. The user can click the User ID and Status glossaries to see more information about the patrons/holds. A glossary at the top of the wizard window displays more information about the title.

To reorder a hold or group of holds, the user highlights the hold line(s) by clicking the line (and dragging the cursor down to select multiple lines), right clicks, and in the shortcut menu, selects Cut. The selected line(s) appears in italics.

The user then highlights the hold line where she wants to insert the hold(s), right-clicks, and selects Insert Before or Insert After in the shortcut menu. The hold(s) are inserted before or after the selected hold line.

When a hold queue that has not been re-ordered displays, the holds will display in the order by date placed. Once the list is reordered, the position value is updated and holds display in the new order.

SirsiDynix System System Administrator Notes

The new Reorder Hold Queue wizard is delivered for the sirsi and admin logins only. The administrator will need to evaluate the functions of this wizard and add the wizard to the access lists of the users who should have access to this wizard.(UNI-17223)

The order of the holds in this list only indicates the order in which holds will be considered to be filled. How the holds are filled after reordering depends on Demand Management policies, hold ranks, and hold priorities.


e-Library 57

e-Library

Enhancements

My Lists Feature Added for Users To Create and Maintain Permanent Lists of Titles

The e-Library has been enhanced with the My Lists feature, which gives users the ability to create one or more lists of selected items. Unlike the Kept record list, which is a temporary list of selected titles that is deleted when the user ends the e-Library session, the lists created with the My Lists feature are saved on the e-Library server for the user to access in future e-Library sessions. Users can create any number of My Lists lists and maintain any number of titles on each list.

In addition to using the My Lists enhancements, libraries also now have the ability to turn the Kept list feature on or off to allow or disallow users from making temporary lists of selected titles. By default, the Kept list feature is enabled to maintain continuity with previous versions of the e-Library.

With the My Lists feature, users can do the following.

• Create lists, modify lists, rename lists, and remove lists they no longer want. A user’s My Lists list remains on the e-Library server until the user removes the list, or until the list is removed automatically after a certain time period of list inactivity.

• Select which list is active.

• Add titles to or remove titles from the active list.

• Send a selected list by email to the specified email address.

• Click a link for a title in the list to view record details and place a hold on a title.

• Sort list contents by title, author, or call number.

• Limit the list contents by a particular library.

• Specify whether brief, full, or all entries display for each title in the selected list.

Users must be logged in to use the My Lists feature. The My Lists lists that a user creates and maintains cannot be shared or accessed by any other user.

Libraries may choose to use both the My Lists feature and the Kept list feature, only the My Lists feature, or only the Kept list feature. Contact the SirsiDynix Symphony administrator to configure the e-Library environment variables as needed.

The My Lists feature and the ability to turn the Kept list feature on or off are available only in Revision D of the e-Library.



The e-Library has been enhanced with the My Lists feature, which gives users the ability to create one or more lists of selected items. Unlike the Kept record list, which is a temporary list of selected titles that is deleted when the user ends the e-Library session, the lists created with the My Lists feature are saved on the e-Library server for the user to access in future e-Library sessions. Users can create any number of My Lists lists and maintain any number of titles on each list. A user’s My Lists list remains on the e-Library server until the user removes the list, or until the list is removed automatically after a certain time period of list inactivity.

In addition to using the My Lists enhancements, libraries also now have the ability to turn the Kept list feature on or off to allow or disallow users from making temporary lists of selected titles. By default, the Kept list feature is enabled to maintain continuity with previous versions.

Libraries may choose to use both the My Lists feature and the Kept list feature, only the My Lists feature, or only the Kept list feature. The following environment variables have been added to control the use of the My Lists feature and the Kept list feature.

• USE_KEPT_LIST controls the use of the temporary Kept list. If this environment variable is set to 0, the Kept list feature is turned off, the Keep button does not display next to each title in the search results list, and the user cannot save titles to a temporary Kept list. If this environment variable is set to 1, the Keep button displays next to each title in the search results list, and a user save titles to a temporary Kept list. By default, the USE_KEPT_LIST environment variable is set to 1 to maintain continuity with previous revisions of the e-Library.

• USE_MYKEPT_LIST controls the use of the My Lists list. If this environment variable is set to 0, the My List feature is turned off, the +My List button does not display next to each title in the search results list, and the user cannot create any My Lists lists. If this environment variable is set to 1, the +My List button displays next to each title in the search results list, and a user can create and add titles to a permanent, selected My Lists list. By default, the USE_MYKEPT_LIST environment variable is set to 0.

By default, the environment variables are delivered in the following files.

• Unicorn/Webcat/Config/k12.env

• Unicorn/Webcat/Config/ilink.env

• Unicorn/Webcat/Config/ibistro.env

The environment variables should be copied from the k12.env, ilink.env, or ibistro.env file to the system.env file (for system-wide use) or to the envnxxx.env file (for use in the specific environment defined by policy number xxx).

(UNI-18527)(UNI-19294) (UNI-19295)

The My Lists feature and the ability to turn the Kept list feature on or off are available only in Revision D of the e-Library.

e-Library 59

Tabbed Display Replaces the Review My Account Display

The Review My Account display in the e-Library has been redesigned to include tabs so the user can more quickly access the desired information. SirsiDynix Symphony administrators can configure environment variables to control what information and features are available on certain tabs.

By default, the e-Library is delivered with the new Review My Account display turned off so the e-Library interface appears as in previous versions. The SirsiDynix Symphony administrators can configure environment variables so the e-Library will use the new Review My Account tabbed display.

The tabs that may display when the user moves to the Review My Account display are described in following sections.

Account Summary Tab

The Account Summary tab displays information about the user’s current library transactions. Depending on the information that is configured to display, this tab may show the amount of unpaid bills, the number of current checkouts, the number of overdue items, and other information.

This tab may also display certain alert messages, such as the user’s status or the user group status, and the expiration of the user’s library privileges, if they are configured to display.

The tab can be configured to display a list of cancelled holds for the user, and to allow the user to place a new hold on an item for which a hold had been cancelled.

Checkouts Tab

The Checkouts tab shows a list of the user’s checkouts and allows users to renew items. By default, the tab is configured to display only current checkouts. If the user does not currently have any charged items, this tab will not display.

System administrators can change the tab to display both active and inactive checkouts (including items assumed to be lost).

This tab can be configured to display a second Select All check box at the end of a list of a user’s checkouts if the number of checkouts equals or exceeds a specified number. The Select All check box at the end of the list allows users to select all items in the list without having to return to the beginning of the checkouts list first and then selecting the Select All check box at the beginning of the list.

Holds Tab

The Holds tab shows a list of holds that the user has placed, and whether the holds are available or unavailable. Depending on how this tab is implemented by the library, users can cancel holds, edit holds, suspend holds, or activate holds on this tab. By default, the tab is set to display on active holds.

System administrators can change the tab to display both active and inactive holds.


The tab can be configured to allow users to cancel available holds, or to prevent users from cancelling holds that are already available.

The tab can be configured to display the total number of holds for the titles that the user has requested.

The tab can be configured to display an “in transit” message for a hold if the requested item is in transit to the pickup library.

This tab can be configured to display a second Select All check box at the end of the holds list if the number of holds equals or exceeds a specified number. The Select All check box at the end of the list allows users to select all items in the list without having to return to the beginning of the holds list first and then selecting the Select All check box at the beginning of the list.

Requests Tab

The Requests tab shows a list of requests the user has made of the library. Users can view the details of and response to a particular request, or cancel a request on the tab.

The tab can be configured to display or not display. If the user has not made any requests, this tab will not display even if the tab is configured to display.

Bills Tab

The Bills tab shows a list of unpaid bills that have been assessed to the user’s account. Bill information includes the reason for the bill, the amount of the bill, and the date the bill was added to the account. For bills associated with items, the title and author also display. Fines for items that are still checked out will not display on the Bills tab until the items are returned. If the user does not have any unpaid bills, the Bills tab will not display.

The tab can be configured to display bill payment button(s) if the library allows bills to be paid using an online bill payment service.

Suspensions Tab

The Suspensions tab displays a list of suspensions for the user, if the library uses suspensions. If the library does not use suspensions, or if the user does not have any suspensions, this tab will not display.

Bookings Tab

The Bookings tab displays a list of booked items for the user, if the library allows users to book items for a period of time. The booking start date and time, the booking end date and time, and the item pickup library display for each booked item. As applicable, the title and author display for booked items. If the user has not booked any materials, the Bookings tab will not display.

e-Library 61

Reservations Tab

The Reservations tab displays a list of reservations the user has made on reserved material. For each reservation, the reservation start date and time and the reservation end date and time display. Users can cancel reservations on the tab. If the user has not made any reservations, of the library does not use reservations, this tab will not display.

Additional Customizing Available for the My Account Tabs

SirsiDynix Symphony administrators can set various environment variables to customize the item displays in the My Account tabs.

• Users may be able to view the catalog record for an item in lists on the My Account tabs by selecting a Details link for the item.

• The item type can display for each item in an item list on the My Account tabs.

• Users can sort long lists, such as the list of charges, by due date, author, title or title/author, times renewed, unpaid bill amounts, and availability. The user can sort these lists in ascending or descending order by clicking the column headers. Underlined column header text indicates that the column can be sorted. Up and down arrows indicate the direction of the sort, either ascending or descending. This feature makes it easier for users to find specific titles that have available holds, or items due on a specific date, and more. For example, a user could sort the charges list by due date and then the renew items by selecting the corresponding check boxes and clicking Renew Selected Items.


The Review My Account display in the e-Library has been redesigned to include tabs so the user can more quickly access the desired information. Environment variables were added to allow or disallow the following features in the My Account tabs and lists.

• Users may view the catalog record for an item in lists on the My Account tabs.

• The item type may display for each item in an item list on the My Account tabs.

• Users may cancel available holds they have placed.

• The list of the user’s charges can display only active charges, or both active and inactive charges (including items assumed to be lost).

• The list of the user’s holds can display only active holds, or both active and inactive holds.

• Users can place a new hold on an item for which a previous hold was cancelled.

• A second Select All check box can display at the end of a checkouts list and/or a holds list when the list contains a number of items equal to or greater than the specified number.

• A list of cancelled holds may display.

• Users may see the total number of holds for the titles that they requested.

• Users may see an “in transit” message if the requested item is in transit to the pickup library.


• The user’s status and/or group status can display on the Account Summary tab.

• A message that the user’s library privilege expired or will expire soon may display on the Account Summary tab.

• The Requests tab can be configured to display or remain hidden.

• Users can sort long lists, such as the list of charges, by due date, author, title or title/author, times renewed, unpaid bill amounts, and availability. The user can sort these lists in ascending or descending order by clicking the column headers. Underlined column header text indicates that the column can be sorted. Up and down arrows indicate the direction of the sort, either ascending or descending. This feature makes it easier for users to find specific titles that have available holds, or items due on a specific date, and more. For example, a user could sort the charges list by due date and then the renew items by selecting the corresponding check boxes and clicking Renew Selected Items.

By default, the e-Library is delivered with the new Review My Account display is turned off so the e-Library interface appears as in previous versions. To turn on the new Review My Account display in the e-Library, copy the PAGES_SET and IMG_OTHER environment variables from one of the following files to the system.env file, as applicable.




In the system.env file, modify the PAGES_SET environment variable as follows to use the RevD page set.

PAGES_SET|Elib_revD|

Then, modify the IMG_OTHER environment variable as follows to specify the RevD graphics files that are to be used.

IMG_OTHER|MiscD|

To restore the system to a previous interface (such as to the Elib_revC files, to the Elib_revB files, or to the k12 files), open the system.env file, and modify the PAGES_SET environment variable to specify the interface files that are to be used.

For example, to use the Elib_revC interface files, set the PAGES_SET environment variable as follows in the system.env file.

PAGES_SET|Elib_revC|

Then, modify the IMG_OTHER environment variable to specify the graphics files that are to be used. The graphics files for previous interfaces differed depending on whether the iLink or iBistro interface was used for the e-Library.

• If the iLink interface was used, modify the IMG_OTHER environment variable as follows.

IMG_OTHER|Miscil|

• If the iBistro interface was used, modify the IMG_OTHER environment variable as follows.

e-Library 63

IMG_OTHER|Miscib|

Following sections describe the environment variables that SirsiDynix Symphony administrators can configure to control what information and features are available on certain tabs in the tabbed Review My Account display. The environment variables are defined in the following files.



ALLOW_AVAIL_CANCEL The ALLOW_AVAIL_CANCEL environment variable either allows users to cancel holds that are already available for pickup, or prevents users from cancelling available holds. If this variable is set to 1, the Cancel Hold button displays on the Holds tab for the user to cancel selected holds. If the variable is set to 0, users cannot cancel available holds. By default, the ALLOW_AVAIL_CANCEL environment variable is set to 1.

CHARGES_TO_DISPLAY The CHARGES_TO_DISPLAY environment variable determines what type of charges to display. If this environment variable is set to X, only active charges display (which were the only type of charges displayed in previous versions of the e-Library). If this environment variable is set to A, all types of charges display. Setting the environment variable to A will cause the e-Library to display both active charges and inactive charges (including items that are assumed to be lost). By default, this environment variable is set to X.

HOLDS_TO_DISPLAY The HOLDS_TO_DISPLAY environment variable determines what type of holds to display. If this environment variable is set to Y, only active holds display (which were the only type of holds displayed in previous versions of the e-Library). If this environment variable is set to A, the e-Library will display both active and inactive holds. By default, this environment variable is set to Y.

PLACE_HOLD_ON_EXPIRED The PLACE_HOLD_ON_EXPIREDenvironment variable either allows users to place holds on items for which aprevious hold has expired, or prevents users from placing holds on items thathave expired holds. If this variable is set to 1, the Place Hold button displays onthe Account Summary tab next to the items on which the user’s holds haveexpired. If this variable is set to 0, users cannot place holds from the AccountSummary tab on items for which their holds have expired. By default, thePLACE_HOLD_ON_EXPIRED environment variable is set to 1.


SHOW_ALL_SELECTOR The SHOW_ALL_SELECTOR environment variable specifies the number of items that must be in a list before a second Select All check box displays at the end of the list. The second Select All check box provides a way for the user to quickly select all items in a list without having to move back to the beginning of the list first. On the Checkouts tab, a Select All check box can be configured to display at the end of a user’s checkouts list. On the Holds tab, a second Select All check box can be configured to display at the end of user’s list of holds.

By default, the SHOW_ALL_SELECTOR environment variable is set to 20 so the second Select All check box will display at the end of a list that contains 20 or more items.

SHOW_EXPIRED_HOLDS The SHOW_EXPIRED_HOLDS environment variable either displays the user's expired holds with inactive reasons of Expired or Expired on Shelf on the Account Summary tab, or does not display expired holds for the user. If this environment variable is set to 1, any holds that have expired display on the Account Summary tab. If this environment variable is set to 0, expired holds do not display in the Account Summary tab for the user. By default, this environment variable is set to 1.

SHOW_ALERTS_ON_SUMMARY The SHOW_ALERTS_ON_SUMMARY environment variable either displays alert messages on the Account Summary tab, or does not display alert messages on the Account Summary tab. If this environment variable is set to 1, alert messages display according to the settings of the SHOW_GROUP_STATUS, SHOW_USER_EXPIRY, and SHOW_USER_STATUS environment variables. If this environment variable is set to 0, no alert messages will display on the Account Summary tab for the user. By default, the SHOW_ALERTS_ON_SUMMARY environment variable is set to 1.

SHOW_REQUESTS_ON_ACCOUNT The SHOW_REQUESTS_ON_ACCOUNT environment variable either displays the Requests tab, or hides the Requests tab. If this environment variable is set to 1, the Request tab displays. If this environment variable is set to 0, the Requests tab will not display. By default, this environment variable is set to 1.

Available holds selected with the Select All check box can be cancelled only if the ALLOW_AVAIL_CANCEL environment variable is set to 1.

Setting this environment variable to 1 will have no effect unless the SHOW_GROUP_STATUS, SHOW_USER_EXPIRY, or SHOW_USER_STATUS environment variable is set to display one or more particular alert messages.

The Requests tab will not display even if the SHOW_REQUESTS_ON_ACCOUNT environment variable is set to 1 if the user does not have any requests.

e-Library 65

SHOW_GROUP_STATUS The SHOW_GROUP_STATUS environment variable either displays the status of the user group to which the user belongs on the Account Summary tab, or does not display the user’s group status. If this environment variable is set to 1, and the SHOW_ALERTS_ON_SUMMARY environment variable is also set to 1, the status of the user group will display on the Account Summary tab. If the SHOW_GROUP_STATUS environment variable is set to 0, the status of the user group will not display. By default, the SHOW_GROUP_STATUS environment variable is set to 1.

SHOW_USER_EXPIRY The SHOW_USER_EXPIRY environment variable either displays a message on the Account Summary tab that the user’s library privileges have expired or are about to expire, or does not display any messages about the user’s library privileges. If this environment variable is set to 1, the SHOW_ALERTS_ON_SUMMARY environment variable is also set to 1, and the user’s privileges have expired, a message about the user’s expired privileges will display on the Account Summary tab. If the user’s library privileges will expire within the next 30 days, a message stating that the user’s library privileges are about to expire will display on the Account Summary tab. If the SHOW_USER_EXPIRY environment variable is set to 0, messages about the user’s library privileges will not display. By default, the SHOW_USER_EXPIRY environment variable is set to 1.

SHOW_USER_STATUS The SHOW_USER_STATUS environment variable either displays the user’s current status on the Account Summary tab, or does not display the user’s status. If this environment variable is set to 1, and the SHOW_ALERTS_ON_SUMMARY environment variable is also set to 1, the user’s current status will display on the Account Summary tab. If the SHOW_USER_STATUS environment variable is set to 0, the user’s current status will not display. By default, the SHOW_USER_STATUS environment variable is set to 1.

USE_FULLDETAIL_LINKS The USE_FULLDETAIL_LINKS environment variable either displays the Details link for users to view catalog records from the My Account lists, or does not display the Details link. If this environment variable is set to 1, the Details link displays next to items listed in the My Account tabs. Clicking the Details link will display the catalog record for the item. If this environment variable is set to 0, the Details link will not display in the My Account lists. By default, this variable is set to 0.

Both the SHOW_ALERTS_ON_SUMMARY environment variable and the SHOW_GROUP_STATUS environment variable must be set to 1 for the user status to display on the Account Summary tab.

Both the SHOW_ALERTS_ON_SUMMARY environment variable and the SHOW_USER_EXPIRY environment variable must be set to 1 for the messages about the user’s library privileges to display on the Account Summary tab.

Both the SHOW_ALERTS_ON_SUMMARY environment variable and the SHOW_USER_STATUS environment variable must be set to 1 for the user’s current status to display on the Account Summary tab.


USE_ITEMTYPE The USE_ITEMTYPE environment variable controls whether the item type will display for each item in item lists in My Account tabs. If this environment variable is set to 1, the item type will display for each item, just below the Title or Title/Author information. If this environment variable is set to 0, the item type will not display. By default, this environment variable is set to 0.

USEHOLDINTRANSIT The USEHOLDINTRANSIT environment variable controls whether the intransit status message displays in the holds lists in the My Account tabs. If this environment variable is set to 1, the intransit message displays as applicable for holds on the Holds tab. If this environment variable is set to 0, the intransit status message does not display for any holds on the Holds tab. By default, this environment variable is set to 0.

USEHOLDQUEUEPOSTOTAL The USEHOLDQUEUEPOSTOTAL environment variable controls whether the user will see the total number of holds for items in the holds list in the My Account tabs. If this environment variable is set to 1, a message similar to the following displays for each hold listed on the Holds tab.

Your position in the holds queue: 23 of 49

If this environment variable is set to 0, the total number of holds does not display in the holds message, and the message displays similar to the following.

Your position in the holds queue: 23

By default, this environment variable is set to 0.

USE_SORT_LISTS The USE_SORT_LISTS environment variable and its associated variable control the following.

• Whether users can sort My Account lists

• The default sorting value

• Which lists in the My Account tabs that can be sorted

SirsiDynix Symphony Administrators can control whether users can have the ability to sort My Account lists by defining the setting of the USE_SORT_LISTS environment variable. If this environment variable is set to 1, users can sort the My Accounts list. If the environment variable is set to 0, the My Account lists cannot be sorted. By default, this environment variable is set to 0.

Item Type values do not display for items listed on the Reservations tab.

To use the USEHOLDQUEUEPOSTOTAL variable, the USEHOLDQUEUEPOS variable must be set to 1. Additionally, the USEHOLDQUEUEPOSTOTAL variable is only valid with Demand Management when using system level holds with no prioritization.

e-Library 67

Administrators can also control the default sort value for the My Account lists with the following associated environment variables. (The text below is excerpted from the Unicorn/Webcat/Config/ilink.env file or Unicorn/Webcat/Config/ibistro.env file.) The default value for each variable is shown.

# Default table sorting

# The xxx_SORT_COLUMN is the id from the header cell definition in

# 25.pg or renew_review.h

# The xxx_SORT_TYPE tells the sort how to compare the data

# The values should be a - alphanumeric, d - date , m - money, n - numeric

# The xxx_SORT_COLUMN_NUMBER are for the tables with irregular headings

# it specifies the column in the data portion of the table to sort

CHARGE_SORT_COLUMN|t1sc1|

CHARGE_SORT_TYPE|a|

CHARGE_RENEW_SORT_COLUMN|t1asc1|

CHARGE_RENEW_SORT_TYPE|a|

SUSPENSIONS_SORT_COLUMN|t2sc1|

SUSPENSIONS_SORT_TYPE|a|

HOLD_SORT_COLUMN|t3sc1|

HOLD_SORT_TYPE|a|

BILL_SORT_COLUMN|t4sc1|

BILL_SORT_TYPE|a|

BOOKING_SORT_COLUMN|t5sc1|

BOOKING_SORT_COLUMN_NUMBER|0|

BOOKING_SORT_TYPE|a|

RESERVATION_SORT_COLUMN|t6sc1|

RESERVATION_SORT_COLUMN_NUMBER|1|

RESERVATION_SORT_TYPE|a|

# If there are words are punctuation that should not be included in the

# alphanumeric sort comparison then add them to the following variable

# in system.env

# ex: DONT_SORT_ON_THESE|\\bthe\\b,\\ba\\b,\\ban\\b,\\",.|

DONT_SORT_ON_THESE|\\bthe\\b,\\ba\\b,\\ban\\b,\\",\\t,\\n|


The administrator can control the sort of these fields:

• Charges/renewals (CHARGE_SORT_* and CHARGE_RENEW_SORT_*)

• Suspensions (SUSPENSIONS_SORT_*

• Holds (HOLD_SORT_*)

• Bills (BILL_SORT_*)

• Bookings (BOOKING_SORT_*)

• Reservations (RESERVATION_SORT_*)

The first variable for each field sort is xxx_SORT_COLUMN, which is the ID from the header cell definition in 25.pg or renew_review.h.

The second variable for each field sort is xxx_SORT_TYPE, which tells the sort how to compare the data. Accepted values are:

• a for alphanumeric

• d for date

• m for money

• n for numeric

The third variable, xxx_SORT_COLUMN_NUMBER, is for tables with irregular headings. It specifies the column in the data portion of the table to sort.

If punctuation should be ignored in the sort, the administrator can add another variable, DONT_SORT_ON_THESE. The following regular expressions can be added or removed.

• The \\b represents a blank .

• The \\" represents a quote.

• The \\t represents a tab (it is recommended that this expression not be removed, as it will affect the sort).

• The \\n represents a newline (it is recommended that this expression not be removed, as it will affect the sort).

(UNI-15101, UNI-16161, UNI-14604, UNI-14605, UNI-14607, UNI-14582, UNI-15000)

e-Library 69

Updated Interface to the e-Library Includes Support for Local Cascading Stylesheets

The e-Library interface design has been changed to include the following enhancements.

• New look and feel using Standard CSS and JavaScript files instead of inline JavaScript. The new e-Library interface is consistent with the SirsiDynix Enterprise interface because of shared cascading stylesheets. The new e-Library interface can be used across various library types, instead of the iLink interface being used in academic sites and the iBistro interface being used by all other sites.

• Support for the use of local cascading stylesheets, so the e-Library look and feel can be customized for specific libraries or logins.

• Faster response time, since many graphics have been eliminated and color changes are now configured with stylesheets and not in the page files. For example, virtually all of the buttons are now just text.

Libraries can now implement their own custom styles on a system-wide basis, or by library or even specific logins. For example, the library can use certain colors, font sizes, or images for the entire library system, for only Main Library users, or only for STAFF users.

SirsiDynix Symphony administrators can define system-wide styles by modifying the delivered Unicorn/Webcat/Config/Css/custom.css file, or they can define locally-used styles by configuring an environment variable and creating a cascading style sheet file (*.css) in the Unicorn/Webcat/Config/Css directory.

By default, the e-Library is delivered with the new look and feel turned off so the e-Library interface appears as in previous versions. The SirsiDynix Symphony administrators can configure environment variables so the e-Library will use the new interface design.



The e-Library interface design has been changed to include a new look and feel, using Standard CSS and JavaScript files instead of inline JavaScript. In addition, the e-Library now supports the use of local cascading stylesheets, so the look and feel can be customized for specific libraries and logins. If the library wants to customize the e-Library interface beyond changing styles and colors, the system administrator can create custom pages. The delivered e-Library has a new e-Library logo and a new setting for specifying how library information displays in the interface.

Evaluating the New e-Library Interface The Unicorn/Webcatcommon/Pages_deliv/Elib_revD directory contains files for the e-Library with its new interface design. By default, the e-Library is delivered with the new interface design turned off so the e-Library interface appears as in previous versions. Sites that have designed their own custom e-Library pages will need to examine the new interface and determine whether their customizations are still necessary or desired.

Enabling the New e-Library Interface To turn on the display of the new e-Library look and feel, copy the PAGES_SET and IMG_OTHER environment variables from one of the following files to the system.env file, as applicable.






Then, modify the IMG_OTHER environment variable as follows to specify the RevD graphics files that are to be used.

IMG_OTHER|MiscD|

To restore the system to a previous interface (such as to the Elib_revC files, to the Elib_revB files, or to the k12 files, open the system.env file, and modify the PAGES_SET environment variable to specify the interface files that are to be used.

For example, to use the Elib_revC interface files, set the PAGES_SET environment variable as follows in the system.env file.

PAGES_SET|Elib_revC|

In K12 libraries that want to use the new e-Library interface, the system administrator must do some additional configuration tasks so the K12 Gateway will function correctly. See Additional Configuration Required for the K12 Gateway on page 72 for information.

Modifications to the delivered custom.css file and the creation of locally-used cascading stylesheet files and custom pages are the sole responsibility of the site. SirsiDynix Client Care does not provide assistance in creating or customizing cascading stylesheets and pages.

e-Library 71

Then, modify the IMG_OTHER environment variable to specify the graphics files that are to be used. The graphics files for previous interfaces differed depending on whether the iLink or iBistro interface was used for the e-Library.

• If the iLink interface was used, modify the IMG_OTHER environment variable as follows.

IMG_OTHER|Miscil|

• If the iBistro interface was used, modify the IMG_OTHER environment variable as follows.

IMG_OTHER|Miscib|

Defining System-Wide Styles SirsiDynix Symphony administrators can define system-wide styles to be used with the new e-Library interface design by modifying the delivered Unicorn/Webcat/Config/Css/custom.css file. Modifying the custom.css stylesheet file is like editing the system.env file; any changes made to the custom.css file are applied to files in /Pages_deliv/Elib_revD directory, which contains the files for the new e-Library interface. All logins using the new e-Library interface will see the styles that are defined in the custom.css file. The custom.css file and any custom JavaScript files are copied to the system’s web root when the setup_webcat script is run.

Defining Local Styles Style changes can now be made for any individual environment by creating a stylesheet file (*.css) in the in the Unicorn/Webcat/Config/Css directory, and then specifying the stylesheet file name in the new CUSTOMCSS environment variable in the individual environment’s environment file (envnxxx.env). The xxx in the environment file name is the policy number of the specific environment. The local *.css file and any custom JavaScript files are copied to the system’s web root when the setup_webcat script is run. When the user logs into the individual environment, the stylesheet file specified with the CUSTOMCSS environment variable is used when displaying e-Library pages instead of the custom.css file in the Unicorn/Webcat/Config/Css directory.

For example, the Main Library wants its logins to have e-Library footers that have a pale yellow background, and no background image. The system administrator defines the following footer customization in the Main.css file, and saves the file to the Unicorn/Webcat/Config/Css directory.

.footer_container {

background-image: none;

background-color:#FFFFCC;

}

To continue the current example, the policy number of the MAIN environment policy is 7. In the Main Library’s environment file, envn7.env, the system administrator specifies the Main.css file in the CUSTOMCSS environment variable as follows.

CUSTOMCSS|Main.css|


When a Main Library login is used to access the e-Library, the styles defined in the Main.css stylesheet file are used in the e-Library display.

Creating Custom Pages If the library wants to customize the e-Library interface files beyond changing styles and colors, create and save custom pages to the Unicorn/Webcat/Pages_custom/Elib_revD directory.

New e-Library Logo Files The new e-Library interface includes a new e-Library logo for the titlebar. The LIBLOGO environment variable is set as follows to display the smallest of the delivered e-Library logos (LIB300.gif).

LIBLOGO|LIB300|

The LIBLOGO environment variable is set in the following files.



Change to the Display of Library Information Previously, library information could be made to display only on Quick Search pages in the e-Library interface. The following changes have been made to the USE_TITLEBAR_LIBINFO environment variable to control where the library information displays.

• If the USE_TITLEBAR_LIBINFO environment variable is set to 1, the library information displays on every e-Library page that the user accesses. This setting is the delivered default.

• If the USE_TITLEBAR_LIBINFO environment variable is set to 0, the library information displays only when the user selects Quick Search to view the Quick Search pages.

Libraries may choose to hide the library information completely by setting the IBISTRO_LIBINFO_CONFIG environment variable 0, to display the library information only on the starting page by setting the IBISTRO_LIBINFO_CONFIG environment variable to 1, or to create custom pages to contain the library information.

The USE_TITLEBAR_LIBINFO environment variable and IBISTRO_LIBINFO_CONFIG environment variable are set in the following files.



Additional Configuration Required for the K12 Gateway In K12 sites that want to use the new e-Library look and feel, the system administrator must do some additional configuration in the appropriate environment file and in the WorkFlows Java client for the K12 Gateway to function correctly.

e-Library 73

Copy the following environment variables from the Unicorn/Webcat/Config/k12.env environment file to the Unicorn/Webcat/Config/system.env environment file, or to the individual environment’s environment file, envnxxx.env (where xxx is the policy number of the specific environment).

• PAGES_SET

• RB_IMG_*

• ENTERPRISE_PAGE_MODEL



In the system.env file, modify the RB_IMG_* environment variables to specify the graphics files that are to be used for the images in the Gateway Root Bar (folder tabs). For example, the RB_IMG_POWER_SEARCH environment variable for the Power Search images may be set to RBPOWER.

The following list shows the Root Bar environment variables that may be configured.

• RB_IMG_COOL_SITES

• RB_IMG_FAVORITES

• RB_IMG_MY_STUFF

• RB_IMG_POWER_SEARCH

• RB_IMG_QUICK_SEARCH

• RB_IMG_READING_PROG

• RB_IMG_RESERVES

• RB_IMG_VISUAL_SEARCH

In the system.env file, set the ENTERPRISE_PAGE_MODEL environment variable to 0 so the e-Library pages have the proper page header when the e-Library connects to libraries that use SirsiDynix Enterprise.

In the WorkFlows Java client, change the K12GATE gateway configuration as follows.

• Change the CALL_NUMBER element in the K12GATE gateway to Available.

• Change the HAVE_U_READ group in the K12GATE gateway to Available.

• Change the COOL_SITES group in the K12GATE gateway to Available.

• Change the COOL_SITES group's elements beginning with DIV_ in the K12GATE gateway to Not Available.

• Change the remaining elements of COOL_SITES in the K12GATE gateway to Display Check List : NO and Display Sentences : YES.


• Change the ROOT group of the K12GATE gateway to Display Check List : NO and Display Sentences : YES.

• Change the MY_STUFF group of the K12GATE gateway from "Display Check List : NO " and " Display Sentences : YES.

(UNI-16742) (UNI-17541)

User Can Bookmark Pages and Create Permalinks to Pages

The e-Library has been enhanced with the ability to bookmark library catalog pages, and to create permanent links (permalinks) to library catalog pages that can be used in a Web log (blog) or on a Web page. With the bookmarks or permalinks, users can click a bookmark or a link to return to particular search hits page or other library Web pages of interest to them.

System administrators can configure the e-Library to display options for bookmarking the current page or catalog page, and/or to create permalinks for the current page or catalog page. The bookmarks and permalinks feature is supported for the Internet Explorer, Firefox, and Safari browsers.


The e-Library has been enhanced with environment variables that are used to display options for bookmarking the current page or catalog page, and/or to create permanent links (permalinks) for the current page or catalog page. The bookmarks and permalinks feature is supported for the Internet Explorer, Firefox, and Safari browsers.

Users cannot create bookmarks or permalinks by copying the URL of a browser window because the browser URL contains a unique ID for the e-Library session. If the user ends the e-Library session and later tries to use the copied URL, a message displays that the e-Library session has ended, and the user is returned to the catalog search page or e-Library home page.

The bookmarks and permalinks feature is available only in the new e-Library interface design, which is contained in files in the Unicorn/Webcatcommon/Pages_deliv/Elib_revD directory. This feature is not available for previous versions of the e-Library (iBistro and iLink).

The bookmarks and permalinks feature is available only in the new e-Library interface design, which is contained in files in the Unicorn/Webcatcommon/Pages_deliv/Elib_revD directory. This feature is not available for previous versions of the e-Library (iBistro and iLink).

e-Library 75

Using Bookmarks

The following environment variables have been added to the e-Library environment files, ibistro.env and ilink.env, for the use of bookmarks.

• The USE_BOOKMARKS environment variable determines whether the library allows the use of the bookmark feature in the e-Library. If this environment variable is set to 0, no option displays to bookmark e-Library pages. If this environment variable is set to 1, an option displays for users to bookmark the current e-Library page. By default, this environment variable is set to 0.

• The BOOKMARK_THIS_PAGE environment variable specifies the text that is to display on the bookmark option, such as Bookmark This Page. By default, the environment variable is set to $<bookmark_this_page> so the bookmark option text can be localized.

Using Permalinks

The following environment variables have been added to the e-Library environment files for the use of permalinks.

• The USE_PERMALINKS environment variable determines whether the library allows the use of the permalinks feature in the e-Library. If this environment variable is set to 0, no option displays to create a permalink for the e-Library page. If this environment variable is set to 1, an option displays for users to create a permalink for the current e-Library page. By default, this environment variable is set to 0.

• The PERMALINK environment variable specifies the text that is to display on the permalink option, such as Permalink to This Page By default, the environment variable is set to $<permalink> so the permalink option text can be localized.

• The TO_LINK environment variable specifies the instructional text that is to display in the permalink window. The text should explain to the user how to copy and paste the permalink so it can be used in mail messages, blogs, a Web page, and so on. By default, the environment variable is set to $<to_link> so the text can be localized.

The USE_BOOKMARKS environment variable must be set to 1 for the BOOKMARK_THIS_PAGE environment variable setting to have any effect.

The USE_PERMALINKS environment variable must be set to 1 for the PERMALINK and the TO_LINK environment variable settings to have any effect.


Specifying Shared IDs in Multilibrary Systems or Consortia

In a multilibrary system or a library consortia, the LINK_OPAC_USER environment variable can be used to specify different shared IDs for libraries in the system. Since each library can have a different gateway and page set, each library that wants to use bookmarks and permalinks can define the LINK_OPAC_USER environment variable in its individual environment file, envnxxx.env. (The xxx in the environment file name is the policy number of the specific environment.) When the user logs into the individual environment, the user ID specified with the LINK_OPAC_USER environment variable is used when creating bookmarks and permalinks. By default, the LINK_OPAC_USER environment variable is set to the WEBSERVER user ID.

The following e-Library files have been modified for the bookmarks and permalinks enhancement.



(UNI-15856)

Page Titles Display

Previously, all e-Library page titles displayed in the browser window titlebar as either e-Library OPAC iBistro or e-Library OPAC iLink. As a result, users could be confused as to which e-Library page displayed, was bookmarked, or was used for a permanent link (permalink).

The e-Library has been enhanced to display page titles in the browser window titlebar. Contact the e-Library administrator to customize the page titles.


The e-Library has been enhanced to display page titles in the browser window titlebar. For each e-Library page that comes from a gateway, the gateway element heading displays as the page title. If the gateway element heading does not exist or is empty, the gateway element description is used as the page title. If the gateway element heading and gateway element do not exist or are empty, the $<label> variable for the page is read from the labels file.

The following list describes specific cases of how page titles are determined.

• For any group page display, the title comes from the gateway element heading, the gateway element description, or the label Gateway Element : ELEMENT_NAME. For example, the gateway element name can be HAVE_U_READ or RESERVE_DESK.

• For any catalog search page, the title comes from the gateway element heading, the gateway element description, or the $<search_catalog> label.

• For the call number browse page, the title comes from the gateway element heading, the gateway element description, or the $<call_number_browse> label.

• For the Reserve Desk page, the title comes from the gateway element heading, the gateway element description, or the $<RESERVE_DESK_DESC> label.

e-Library 77

• For the holds list page, the title comes from the gateway element heading, the gateway element description, or the $<REQGROUP_DESC> label.

• For the Z39.50 search, the title comes from the gateway element heading, the gateway element description, or the $<z3950_search:c> label.

• For the library information list, the title comes from the gateway element heading, the gateway element description, or the $<LIB_INFO_HEAD> label.

In the case of an individual request page, the title comes from the request policy description if it exists and is not blank. If the policy description does not exist, the title defaults to the $<place_request> label.

The following files were changed by this enhancement.



• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/state_title.h

(UNI-15857)

NoveList URL Updated in Environment Files

EBSCO Publishing changed the URL for NoveList, a reader advisory service. The environment files in the e-Library have been updated so the variables that apply to NoveList contain the correct settings.


EBSCO Publishing changed the URL for NoveList, a reader advisory service. The environment files in the e-Library have been updated so the variables that apply to NoveList contain the correct settings.

The following environment file excerpt shows the updated variables. Modify the variables as needed for the library.

NOVELIST_URL_START|http://search.ebscohost.com/Login.aspx?|

# EBSCO designated URL

# NoveList access information (different for every library)

NOVELIST_CUSTID|xxxxxxx|

# EBSCO assigned customer account ID #

NOVELIST_AUTHTYPE|&authtype=ip,uid|

# EBSCO designated authtype #

# EBSCO designated string

NOVELIST_URL_END|&site=novelist-live&direct=true&scope=site&bquery=IB+|

The following files were changed for the NoveList update.




(UNI-17612)


Dates Can Display in Descriptive Format Instead of Numeric Format

The e-Library has been enhanced so dates that display in the e-Library can be displayed in a descriptive date format instead of in a numeric-only format. For example, if a user accesses the My Account pages and views the items she has checked out, the due dates display as Jan 1, 2009 instead of 01/01/2009.

If English is the selected local language, three-letter abbreviations are used for the descriptive month name (Jan, Feb, Mar, Apr, and so on). For other languages, the customary month name abbreviations specific to each language are used for the descriptive month names.

If the descriptive date format is used, any e-Library displays that are sorted by date are sorted in the correct calendar order.

If the system administrator configures the e-Library to display dates in a descriptive format, the dates display as follows.

• If the system date format is mm/dd/yyyy, the descriptive date format is Month Day, Year (for example, Jan 1, 2009).

• If the system date format is dd/mm/yyyy, the descriptive date format is Day Month Year (for example, 1 Jan 2009).

• If the system date format is yyyy/mm/dd, the descriptive date format is Year Month Day (for example, 2009 Jan 1).


The e-Library has been enhanced with the DISPLAY_MONTH_AS_ALPHA environment variable. This environment variable can be set so dates that display in the e-Library can be displayed in a descriptive date format instead of in a numeric-only format. For example, if a user accesses the My Account pages and views the items she has checked out, the due dates display as Jan 1, 2009 instead of 01/01/2009.

• If the DISPLAY_MONTH_AS_ALPHA environment variable is set to 0, the dates display in the e-Library in numeric-only format. This value is the delivered default.

• If the DISPLAY_MONTH_AS_ALPHA environment variable is set to 1, the dates display in descriptive format.

This enhancement does not apply to systems that use the Hijri date format. Dates will continue to display in the Hijri date format even if the e-Library is configured to display a descriptive date format.

e-Library 79

The descriptive format that is used depends on the system date format, as follows.

• If the system date format is mm/dd/yyyy, the descriptive date format is Month Day, Year (for example, Jan 1, 2009).

• If the system date format is dd/mm/yyyy, the descriptive date format is Day Month Year (for example, 1 Jan 2009).

• If the system date format is yyyy/mm/dd, the descriptive date format is Year Month Day (for example, 2009 Jan 1).

If English is the selected local language, three-letter abbreviations are used for the descriptive month name (Jan, Feb, Mar, Apr, and so on). For other languages, the customary month name abbreviations specific to each language are used for the descriptive month names.

If the descriptive date format is used, any e-Library displays that are sorted by date are sorted in the correct calendar order.

The following files were changed for the descriptive date enhancement.




(UNI-18304)

Online User Registration Changed to Support the User Name Fields in SirsiDynix Symphony 3.3

Previously, when a user registered online using Online User Registration, the first, middle, and last name entries were combined and sent to the SirsiDynix Symphony server has a single name. In SirsiDynix Symphony 3.3, the user name has been expanded to include the new fields First Name, Preferred Name, Middle Name, Last Name, and Suffix. Online User Registration has been changed to simply send the first, middle, and last name entries to the SirsiDynix Symphony server as they are entered in the online registration form.


Previously, when a user registered online using Online User Registration, the first, middle, and last name entries were combined as specified in the NAME_ORDER variable in the Online User Registration configuration file (oureg.cfg) and sent to the SirsiDynix Symphony server has a single name. In SirsiDynix Symphony 3.3, the user name has been expanded to include the new fields First Name, Preferred Name, Middle Name, Last Name, and Suffix. Online User Registration has been

This enhancement does not apply to systems that use the Hijri date format. Dates will continue to display in the Hijri date format even if the e-Library is configured to display a descriptive date format.


changed to simply send the first, middle, and last name entries to the SirsiDynix Symphony server as they are entered in the online registration form. Therefore, the NAME_ORDER variable is no longer used to determine how the form entries are to be combined to form the user name.

(UNI-17920)

SirsiDynix Enterprise Users Can Place Holds Without Having Access to the e-Library

Patrons using SirsiDynix Enterprise 2.0 now have a more streamlined process to place holds on items owned by library systems that use the e-Library with SirsiDynix Symphony. The patron using SirsiDynix Enterprise would begin to place a hold from the selected item’s Details screen in SirsiDynix Enterprise. The patron would see the item details for the selected item in the e-Library, and then had to click Place Hold to display the Place Hold page. While the e-Library’s item details view was displayed, the patron could have access to the e-Library and all of its functions.

The e-Library has been enhanced with a new environment variable that can be used to simplify the hold placement process for patrons using SirsiDynix Enterprise to place holds. The variable can be set so that when the patron begins to place a hold, the Place Hold screen displays in a separate window. The Place Hold window prompts the patron only for information required to place the hold, and does not contain any navigation aids that would enable the patron to access additional e-Library functions. When the patron finishes placing the hold, the Place Hold window closes, and the patron is returned to SirsiDynix Enterprise.

By default, patrons using SirsiDynix Enterprise to place holds on materials owned by libraries that use the e-Library will first see the e-Library’s item details view for the selected item; then, when the patrons click Place Hold, they will move to the Place Hold page that contains navigation to access other features of the e-Library. Contact the SirsiDynix Symphony administrator to set the environment variable such that the SirsiDynix Enterprise patrons will use the separate Place Hold window to place holds and not have access to other functions of the e-Library.

The NAME_ORDER variable is still required in the oureg.cfg file because it is still used to determine whether the name entered on the registration form is a duplicate of a record already in the user database.

If any blocks occur and prevent the placement of the hold , an error message displays (such as User is BLOCKED). When the patron clicks OK to dismiss the message, the patron returns to the Place Hold window.

e-Library 81


Patrons using SirsiDynix Enterprise 2.0 can now place holds on items owned by library systems that use the e-Library with SirsiDynix Symphony by using a simplified Place Hold screen. The simplified Place Hold screen only prompts SirsiDynix Enterprise users for information required to place the hold, and returns the users to SirsiDynix Enterprise so these users cannot access other functions of the e-Library.

By default, patrons using SirsiDynix Enterprise to place holds on materials owned by libraries that use the e-Library will first see the e-Library’s item details view for the selected item; then, when the patrons click Place Hold, they will move to the Place Hold page that contains navigation to access other features of the e-Library. If the library wants SirsiDynix Enterprise patrons to place holds using a separate Place Hold window that will not allow them to access other functions of the e-Library, the SirsiDynix Symphony administrator must do the following.

• Modify the setting of the ENTERPRISE_PAGE_MODEL environment variable to display the Place Hold screen in a separate window for patrons using SirsiDynix Enterprise to place holds.

• Create the ENTERPRISE Environment policy in SirsiDynix Symphony.

• Create the ENTERPRISE User Profile policy in SirsiDynix Symphony.

Each task is described in following sections.

The following e-Library files have been changed for this enhancement.



• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/71.pg



• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/top.h

• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/showavail.h

• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/showavail.cmd

Modifying the ENTERPRISE_PAGE_MODEL Environment Variable Setting

The ENTERPRISE_PAGE_MODEL environment variable determines whether SirsiDynix Enterprise patrons will see a Place Hold screen in a separate window and be prompted only for information needed to place holds.

• If ENTERPRISE_PAGE_MODEL is set to 0, SirsiDynix Enterprise patrons will first see the e-Library’s item details view for the selected item; then, when the patrons click Place Hold, they will move to the Place Hold page that contains navigation to access other features of the e-Library. This is the delivered default.

• If ENTERPRISE_PAGE_MODEL is set to 1, the Place Hold screen displays in a separate window so the SirsiDynix Enterprise patrons can only place holds and return to SirsiDynix Enterprise.


By default, the environment variable is delivered in the following files.



The environment variable should be copied from the ilink.env or ibistro.env file to the system.env file (for system-wide use) or to the envnxxx.env file (for use in the specific environment defined by policy number xxx).

Creating the ENTERPRISE Environment Policy

The ENTERPRISE Environment policy must be defined for use by the ENTERPRISE User Profile policy. Both policies must be defined if the ENTERPRISE_PAGE_MODEL environment variable is set to 1.

The ENTERPRISE Environment policy should be named ENTERPRISE, and should use the gateway database used by the e-Library. The following example shows a possible configuration of the required fields in the ENTERPRISE Environment policy.

Name = ENTERPRISE Description = Enterprise User Gateway Database = IBISTRO

Creating the ENTERPRISE User Profile Policy

The ENTERPRISE User Profile policy should be named ENTERPRISE, should use the user access used by the e-Library, and should use the ENTERPRISE Environment. Both policies must be defined if the ENTERPRISE_PAGE_MODEL environment variable is set to 1. The following example shows a possible configuration of the required fields in the ENTERPRISE User Profile policy.

Name = ENTERPRISE Description = Enterprise user User Access = WEBSERVER Environment = ENTERPRISE

(UNI-18562)

All Content Link in Item’s Detailed View Displays Syndetic Enrichment Content

The e-Library’s detailed view of individual bibliographic records often contains content such as book cover art, summaries, and reviews for the selected item. For libraries that want to offer additional enrichment content from Syndetic Solutions (a Bowker company), the e-Library has been enhanced with the option to include an All Content link in an item’s detailed view display. When a user clicks the All Content link, all of the Syndetic enrichment content available for that item will display for a user to review. Depending on how the e-Library is configured, the additional enrichment content may display in a separate window or within the detailed item view.

e-Library 83

Syndetic’s enriched content may include the following:

• Cover images

• Summaries/Annotations

• Reviews

• Tables of contents

• Fiction/Biography profiles

• Author notes

• First chapters or excerpts

• Awards

• Fiction search (Find Similar Titles)

• Series information (fiction only)

• Music/Video summaries

If the detailed item view contains A Look Inside tab, the All Content link is the last link at the end of the tab.

If the detailed item view does not contain A Look Inside tab, the All Content link is the last link at the end of the Item Information tab.

To purchase access to Syndetic’s enrichment content, contact the library’s SirsiDynix Sales representative. Contact the library’s SirsiDynix Symphony administrator to configure the e-Library to display the All Content link in the detailed item view display.


The e-Library’s detailed view of individual bibliographic records often contains content such as book cover art, summaries, and reviews for the selected item. For libraries that want to offer additional enrichment content from Syndetic Solutions (a Bowker company), the e-Library has been enhanced with environment variables to include an All Content link in an item’s detailed view display.

The All Content link can display in UNIMARC records and MARC21 records.

If Syndetic enrichment content is not available for a selected item, the All Content link does not display in the item’s detailed view.

Only Revision D of the e-Library supports Syndetic enrichment content.

The All Content link can display in UNIMARC records and MARC21 records.

If Syndetic enrichment content is not available for a selected item, the All Content link does not display in the item’s detailed view.

Only Revision D of the e-Library supports Syndetic enrichment content.


The following environment variables have been added to support user access to Syndetic enrichment content. All three variables must be configured for users to have access to the enrichment content.

• USE_SYNDETIC_ENHANCED_CONTENT determines whether Syndetic enrichment content will be made available to e-Library users.

• SYNDETICS_BASE_URL specifies the basic URL to which values will be appended to access the content on Syndetic’s secure servers when the user clicks the All Content link in the e-Library.

• SYNDETICS_CLIENT_CODE specifies the Syndetic value that identifies the user or library ID that is used to access the Syndetic enrichment content.

Each environment variable is described in detail in following sections. By default, the environment variables are delivered in the following files.




The environment variables should be copied from the k12.env, ilink.env, or ibistro.env file to the system.env file (for system-wide use) or to the envnxxx.env file (for use in the specific environment defined by policy number xxx).

USE_SYNDETIC_ENHANCED_CONTENT The USE_SYNDETIC_ENHANCED_CONTENT environment variable controls whether the All Content link displays in a detailed item view.

• If USE_SYNDETIC_ENHANCED_CONTENT is set to 0, the All Content link does not display in the detailed item view, and users will not have access to the Syndetic enrichment content. This value is the delivered default.

• If USE_SYNDETIC_ENHANCED_CONTENT is set to 1, the All Content link displays in the detailed item view.

SYNDETICS_BASE_URL The SYNDETICS_BASE_URL environment variable specifies the basic URL that is to be used when accessing the enrichment content on Syndetic’s servers. The delivered default URL is http://syndetics.com/index.aspx?.

When a user clicks the All Content link in a detailed item view, the following information is appended to the basic URL to compose the URL that accesses enrichment content specific to the item on Syndetic’s servers.

• The ISBN number of the selected item

• The filename of the data element being requested

• The client code that Syndetic Solutions assigned to the library

• The code for the desired display type or format

Contact Syndetic Solutions for more information on the URL request that is constructed to access specific enrichment content on Syndetic’s servers.

e-Library 85

SYNDETICS_CLIENT_CODE The SYNDETICS_CLIENT_CODE environment variable specifies the Syndetic value that identifies the user or library ID that is used to access the enrichment content on Syndetic’s servers. Syndetic Solutions assigns a client code to control access to the content to which the library subscribes. SirsiDynix Sales will supply the client code to the library when the Syndetic enriched content is purchased. After the enriched content access is given, contact SirsiDynix Client Care with any questions about the client code and the SYNDETICS_CLIENT_CODE environment variable.

(UNI-14374)

Corrections

Barnes & Noble Link Corrected for Buy Now Option

If the library had defined a “Buy Now” button that users could click to purchase items from Barnes & Noble, the following message displayed in the browser window if the user selected the button while viewing a catalog record, a reserve item, or an item on a Best Seller list.

HTTP 400: Bad Request

This has been corrected so that the item is located for possible purchase on the Barnes & Noble Web site. (UNI-16640)


If a “Buy Now” button was configured to display when a user viewed a catalog record, a reserve item, or an item on a Best Seller list, the following message displayed in the browser window if the button was configured to search the Barnes & Noble site to find the selected item.

HTTP 400: Bad Request

The BUYNOW_URL_PT1 environment variable definition was modified as follows for the “Buy Now” search to find the correct item on the Barnes & Noble Web site. The ISBN of the selected item is used in the Web site search.

BUYNOW_URL_PT1|http://search.barnesandnoble.com/booksearch/isb-nInquiry.asp?ISBN=| # Barnes & Noble

The BUYNOW_URL_PT1 environment variable is defined in the Unicorn/Webcat/Config/ibistro.env file and the Unicorn/Webcat/Config/ilink.env file.

Since SirsiDynix no longer has a purchase partnership with Barnes & Noble, the following environment variable definition has been removed.

<SIRSI_Data Environ="BUYNOW_URL_PT3">')"

The BUYNOW_URL_PT3 environment variable definition has been removed from the following delivered e-Library files.




In the Unicorn/Webcatcommon/Pages_deliv/Elib_revB, Unicorn/Webcatcommon/Pages_deliv/Elib_revC, and Unicorn/Webcatcommon/Pages_deliv/Elib_revD directories, the BUYNOW_URL_PT3 environment variable definition has been removed from the following delivered files: 81.pg, recreadlist2.cmd, rsvviewtop.h, viewtop.h, and viewtop2.h. (UNI-16640)

Optional Security Feature Added to Prevent Users from Accessing the My Account Pages Using a Copied URL

Previously, if an e-Library user logged in with a user ID and password, then shared the complete URL of a particular e-Library page with another person, the e-Library user’s personal information could be seen accidentally by the other person if the person accessed the URL while the e-Library session was still open.

For example, an e-Library user mistakenly thought the way to share a bookmark to bibliographic record page was to copy the page’s full URL and send it to a friend using Instant Messenger. The friend pasted the copied complete URL into a browser window. Since the user’s e-Library session was still open, the friend was able to access the user’s particular e-Library session. The friend could then navigate to other e-Library pages, including the user’s personal information in the My Account pages.

A variable has been added to the e-Library configuration so the system administrator can enable a security feature that uses a cookie file. If the security feature is turned on, a cookie file named session_security is created and placed on the user’s workstation when the user starts an e-Library session. The cookie file contains the session code for the user’s e-Library session. As the user uses the e-Library and moves from page to page, the session code in the browser URL is compared to the one in the cookie file. If the session codes match, the user can access the e-Library pages as usual. If the session codes do not match, the following message displays in the user’s browser window.

Session timed out

The following message is also logged into the e-Library error file.

Session/cookie mismatch; unauthorized URL denied

If an e-Library user gives a URL to another user, and the second user tries to access the e-Library with the URL, the second user will see the Session timed out message since that user’s workstation does not have a cookie file with a session code that matches the session code in the copied URL.

The e-Library that will be available for use with the SirsiDynix Symphony 3.3 release will include enhancements to enable users to bookmark e-Library pages and share permanent links (permalinks) to e-Library pages. With these enhancements, users can share e-Library page URLs without mistakenly giving access to their My Account personal pages while their e-Library sessions are still open.

e-Library 87


The COOKIE_SECURITY variable has been added to the Unicorn/Webcat/Config/webconfig file to enable a security feature that uses a cookie file. The security feature is designed to prevent a user from copying an e-Library URL that contains session information and navigating to another user’s personal information in the My Account pages while the user’s e-Library session is still open.

• If the COOKIE_SECURITY variable is set to 0 or is not defined, the cookie security feature is turned off. By default, COOKIE_SECURITY is set to 0.

• If the COOKIE_SECURITY variable is set to 1, a cookie file named session_security is created on the user’s workstation when the user starts an e-Library session. The session_security file contains the session code for the user’s e-Library session. As the user uses the e-Library and moves from page to page, the session code in the browser URL is compared to the one in the session_security file. If the session codes match, the user can access the e-Library pages as usual. If the session codes do not match, the following message displays in the user’s browser window.

Session timed out

The following message is also logged into the web_error file.

Session/cookie mismatch; unauthorized URL denied

If an e-Library user gives a URL that contains a session code to another user, and the second user tries to access the e-Library with the URL, the second user will see the Session timed out message since that user’s workstation does not have a session_security file with a session code that matches the session code in the copied URL..

(UNI-17728)

If the USE_FULL_HTTP_ADDRESS variable in the ibistro.env file or the ilink.env file is set to 0 so the e-Library uses relative URLs instead of absolute URLs, setting the COOKIE_SECURITY variable in the webconfig file to 1 will prevent all users from being able to log into the e-Library. When the e-Library uses relative URLs, the Apache server automatically redirects the URL during the login process, but the session_security cookie file is not created on the user’s workstation. Since the cookie file is not present, the session code information cannot be confirmed, and the Session timed out message will display. Therefore, if the COOKIE_SECURITY variable in the webconfig file is set to 1, the USE_FULL_HTTP_ADDRESS variable must be set to 1 in the ibistro.env file or the ilink.env file to use absolute URLs in the e-Library.

The e-Library that will be available for use with the SirsiDynix Symphony 3.3 release will include enhancements to enable users to bookmark e-Library pages and share permanent links (permalinks) to e-Library pages. With these enhancements, users can share e-Library page URLs without mistakenly giving access to their My Account personal pages while their e-Library sessions are still open.


Message Displays to Show the Status of Online Bill Payments Made With AXIS Payment Management

If a library used AXIS Payment Management (by Capita Business Services, Ltd.) to accept online payment a patron for library bills, the patron would see a blank screen when the online payment request was processed. The patron had no way of knowing if the payment was successful or if it had been rejected.

The following message now displays when an online payment is successfully made using AXIS.

The payment was processed.

If the payment is not successful, the following message displays.

The payment was declined.


If a library used AXIS Payment Management (by Capita Business Services, Ltd.) to accept online payment from a patron for library bills, the patron would see a blank screen when the online payment request was processed. The following message now displays when an online payment is successfully made using AXIS.

The payment was processed.

If the payment is not successful, the following message displays.

The payment was declined.

(UNI-12597)

Electronic Bill Payments Work Correctly in the e-Library revD Pages

If a library implemented the updated interface for e-Library (known as “the revD pages,” released in SirsiDynix Symphony patch cluster 1), the following message displayed if patrons tried to use PayPal, PayPal Payflow Pro, or EnvisionWare eCommerce Services to make an online bill payment.

Invalid CGI request type

The updated e-Library interface has been corrected so the message no longer displays when a patron pays bills online with a form of electronic bill payment.

The message text is not localized according to the selected system language; however, the system administrator can change the message text by editing the text in the Unicorn/Bin/axisPI file.

e-Library 89


In libraries that use PayPal Payflow Pro with a Microsoft Windows server, the system administrator must define an environment variable, PFPRO_CERT_PATH, to specify the certificate file pathname. PayPal Payflow Pro must find the certificate file to complete a payment transaction successfully. The variable definition is as follows.

PFPRO_CERT_PATH = drive:\home directory\webcat\config

The following example shows the variable definition when the certificate file is in the d:\sirsi\unicorn\webcat\config directory on the server.

PFPRO_CERT_PATH = d:\sirsi\unicorn\webcat\config

Refer to the Microsoft Windows help for instructions to define Windows environment variables.

The following e-Library files were changed in this correction.

• Unicorn/Webcatcommon/Pages_deliv/Elib_revD/25_bills.h



(UNI-21261) (UNI-21535) (UNI-21285) (UNI-22065)


Reports 91

Reports

Administration Group Reports

Enhancements

Refactor User Name Report

With Version 3.3, user names in the user records were expanded to include the following fields: Last Name, First Name, Middle Name, and Suffix. Using the Refactor User Name report, a site can populate user records in the SirsiDynix Symphony user database that contain no data in the First Name, Middle Name, and Suffix fields.

The Refactor User Name report will create two finished reports.

• Refactor User Name (default report title) — This report will list the user records that are selected for User Name field reformatting. The report output will contain the original user’s name and ID and an example of how the name will be converted to the new First Name, Middle Name, Last Name, and Suffix fields.

• Refactor User Name (unknown name formats) — This report will list all the selected user records that have an unrecognized user name format. Sites can use this report to manually adjust user records that the report cannot reformat. The report output will contain the user’s name and ID.

When the report is run in the Update Database Records mode, the original user name will be saved in the Extended Information field of the user record.

This report includes the following tabs.

• Basic Tab — This tab lists the report name and brief description of the report.

• User IDs Tab — This report tab allows selecting a specified list of users to include in the report.

• User Selection Tab — This tab contains options that are used to select user records.

• Refactor User Name Tab — This tab is used to indicate whether or not the report is run in the update database mode, what extended information field should be used to store the original user name (such as the Note field), and what format was used for the existing User Name field.

This report should be run after the Version 3.3 upgrade. It is recommended that the site run the report in test mode first, and review the report output to see how the user records will be changed.

For more information, see “Refactor User Name Report” in the WorkFlows Java client online Help.



This report should be run after the Version 3.3 upgrade. The report will only update user records that do not contain data in the First Name, Middle Name, and Suffix fields. It is recommended that administrators first run this report in test mode. After running the Refactor User Name report, the administrator must run the Rebuild User Text report to re-index the new user names. If the library’s user database is very large, administrators should consider running this report after hours or during library “down time.”

(UNI-17260)

Load Users Report Updated to Load New User Name Fields

The Load Users (Userload) report has been updated to use the new user name fields for the user’s name information. The user record load formats have also been updated to accommodate the new fields.

The following new fields were added to the flat ASCII user record format (LDUSER):

• .USER_FIRST_NAME. (20 characters maximum)

• .USER_PREFERRED_NAME. (20 characters maximum)

• .USER_NAME_DSP_PREF. (Integer value 1 or 0)

• .USER_MIDDLE_NAME. (20 characters maximum)

• .USER_LAST_NAME. (60 characters maximum)

• .USER_SUFFIX. (10 characters maximum)

The new LDUSER flat ASCII format is as follows:

*** DOCUMENT BOUNDARY ***

FORM=LDUSER

.USER_ID. User ID

.USER_ALT_ID. User alternative ID

.USER_ROUTING_FLAG. Routing allowed flag

.USER_GROUP_ID. Group ID

.USER_TITLE. Title

.USER_NAME. Name

The User Name field is the name field used by pre-Version 3.3 systems. Sites that have user record input files created before the Version 3.3 upgrade can still load these files using the updated Load Users report. If the input file contains name data in the User Name field, the data will be loaded into the Last Name field in Version 3.3. If the user record input file has data in the User Name field and also in the Last Name field, the data in the Last Name field will be loaded into the user record.

Reports 93

.USER_FIRST_NAME. First name

.USER_PREFERRED_NAME. Preferred name

.USER_NAME_DSP_PREF. Values 1 or 0. 1 to use preferred name or 0 to not use preferred name.

.USER_MIDDLE_NAME. Middle name

.USER_LAST_NAME. Last name

.USER_SUFFIX. Suffix

.USER_LIBRARY. Library name

.USER_PROFILE. User profile

.USER_LOCATION. Location

.USER_ACCESS. User access policy

.USER_ENVIRONMENT. Environment policy

.USER_CATEGORY1. Statistical category 1





.USER_DEPARTMENT. Department

.USER_BIRTH_DATE. Full birth date

.USER_PRIV_GRANTED. Date privilege granted

.USER_PRIV_EXPIRES. Date privilege expires

.USER_LAST_ACTIVITY. Last activity date

.USER_PIN. PIN

.USER_STATUS. Delinquency status

.USER_CLAIMS_RET. Number of claims returned

.USER_MAILINGADDR. Mailing address

.USER_ADDR1_BEGIN.

.USER_ADDR1_END.

.USER_ADDR2_BEGIN.

.USER_ADDR2_END.

.USER_ADDR3_BEGIN.

.USER_ADDR3_END.

.USER_XINFO_BEGIN.


.USER_XINFO_END.

.UACNT_CLEARANCE. Accountability clearance

.UACNT_CITIZENSHIP. Accountability citizenship

.UACNT_ACCESS_RESTR. Accountability access restrictions

.UACNT_NEED_TO_KNOW. Accountability need-to-knows

.UACNT_PATRONTYPE. Accountability patron type

.UACNT_AUTHORITY. Accountability clearance granting authority

.UACNT_SSN. Accountability social security number

.UACNT_BIRTHDATE. Accountability date of birth

.UACNT_BIRTHPLACE. Accountability place of birth

.USER_WEB_AUTH. Web authentication key

.USER_CHG_HIST_RULE. Charge history rule

.USERGROUP_DEFAULT. Default user group

.UGRP_RSPB. User group responsibility

For example, the following sample flat ASCII record displays the new user name fields. (Non-required fields that were not used have been omitted.)

*** DOCUMENT BOUNDARY ***

FORM=LDUSER

.USER_ID. |a1000100000206

.USER_ALT_ID. |aALTID206

.USER_ROUTING_FLAG. |aY

.USER_GROUP_ID. |aCLAUS

.USER_TITLE. |aMr

.USER_NAME. |aMr Santa Claus

.USER_FIRST_NAME. |aSanta

.USER_PREFERRED_NAME. |aSandy

.USER_NAME_DSP_PREF. |a1

.USER_MIDDLE_NAME. |aA.

.USER_LAST_NAME. |aClaus

.USER_LIBRARY. |aMAIN

.USER_PROFILE. |aPUBLIC

.USER_ACCESS. |aPUBLIC

.USER_ENVIRONMENT. |aPUBLIC

Reports 95

.USER_CATEGORY1. |aENGLISH

.USER_CATEGORY2. |aINCITY

.USER_CATEGORY3. |aUNKNOWN

.USER_CATEGORY4. |aUNKNOWN

.USER_CATEGORY5. |aBOOKMOBILE

.USER_BIRTH_DATE. |a19881212

.USER_PRIV_GRANTED. |a20080425

.USER_PRIV_EXPIRES. |a20090425

.USER_LAST_ACTIVITY. |a20080808

.USER_PIN. |a1111

.USER_CHG_HIST_RULE. |aALLCHARGES

.USERGROUP_DEFAULT. |aCLAUS1

.USER_MAILINGADDR. |a1

.USER_ADDR1_BEGIN.

.PHONE. |a555-555-3333

.DAYPHONE. |a555-555-4444

.LINE. |aTEST

.STREET. |a101 Main St #100

.CITY/STATE. |aAnytown, AL

.USER_ADDR1_END.

For the pipe-delimited input file, the six fields (47-52) were added to the end of the user record format as follows:

first_name|middle_name|last_name|suffix|preferred name|name display

preference|

For the new pipe-delimited format, the fields must be listed in the following required order. Policy fields are marked with an asterisk.

user alt ID|user ID|name|title|user access*

|user environment*|address flag|address1 line 1|address1 line2

|address1 line3|address1 line4|address1 line5




|address3 line5|department|user category1*|user category2*

|birth year|library*|location*|profile*|date privilege granted

|date privilege expires|date last activity|PIN

|group ID|responsibility code*|clearance*|citizenship*

|access restriction*|need to know*|routings active

|user category3*|user category4*|user category5*|birth date

|charge history rule|usergroup default|first name|middle name

|last name|suffix|preferred name|name display preference|


For example, the following pipe-delimited record includes the new user name fields in positions 47, 48, 49, 50, 51, and 52.

ALTID529|1000100000529|Mr. Samuel Yongue Caldwell Phd|Mr.|PUBLIC|PUBLIC|1

|.PHONE. 555-555-1111|.DAYPHONE. 555-555-2222|.STREET. 555 Milky Way Lane

|.CITY/STATE. Anytown, MO|.ZIP. 55555|||||||||||MUSIC|ENGLISH|INCITY|

|MAIN||PUBLIC|20071207|20081207|20080808|1111|CALDWELL||||||Y|UNKNOWN

|UNKNOWN|BOOKMOBILE|19510712|ALLCHARGES||Samuel|Yongue|Caldwell|Phd|Skip|1|


Sites that have user record input files created before the Version 3.3 upgrade can still load these files loaded using the updated Load Users report. If the input file contains name data in the User Name field, the data will be loaded into the Last Name field in Version 3.3. If the user record input file has data in the User Name field and also in the Last Name field, the data in the Last Name field will be loaded into the user record.

(UNI-16775, UNI-18727, UNI-18971)

Authority Group Reports

Enhancements

Added Ability to Sort Headings in List Authority Records Report

The List Authority Records (Authlist) report has been enhanced with the ability to perform an alphabetical sort on headings based on the 1XX tags in the MARC authority record. This new sorting option will allow users to create an in-house thesaurus of approved subject terms. Such a thesaurus could be used either by library staff (such as for off-line authority maintenance work) or by the public.

The Sorting tab was added to the List Authority Records report. On this tab, in the Sort By box, the user can select None (for the no sort option) or Headings. If the user selects Headings, the report results will be sorted on the 1XX tag in the authority record. All subfields of the 1XX will be included in the sort. By default, the None option is selected.


If the List Authority Records report is saved as a template or scheduled to run periodically prior to the upgrade, it will still run successfully after the upgrade. Whether or not it the report uses the new sorting option depends on how the report is run after the upgrade:

• If the user clicks the Sort tab before running the report, the report will run using the new sort option (default of headings sort).

• If the user runs the report without changing any options or without clicking the Sort tab, the report will run as before with None as the sort option.

Reports 97

(UNI-15673)

Debt Collection Group Reports

Enhancements

Updates to Debt Collection Reports

Changes have been made to the Debt Collection group reports to function better in a consortia environment and to improve the speed of creating, processing, and updating the debt collection files.

The debt collection reports have been modified to write information to new debt collection databases or tables in SirsiDynix Symphony. The debt collection tables store information about users sent to collection agency, the bill information sent, and the debt totals. These tables are updated when a user is sent to collections, when a user sent to collections makes payments or gets new bills, or when all bills are paid and the user is removed from collection agency.

When a user qualifies for collection agency based on selections in the Collections Information report, the user will be updated with a status of COLLECTIONS. The date/time the user is sent to collections and subsequent bill information is written to the debt collection tables. The Collections Update report will update the user collections information previously sent to the collection agency with new payment activity, new bills, and so forth. Because the Collections Update report also includes a new “synchronization” mode, the Collections Synchronization report was no longer needed and has been removed.

Changes to the Collections Information Report

The Collections Information (Collectiondata) report (or debt collection submission report) creates the initial electronic file that is sent to Unique Management for collection.

If this report was previously scheduled before the Version 3.3 upgrade, sites will need to reschedule the report after upgrading.

For detailed information about the new Debt Collection reports see the report topics and FAQs: Using the Debt Collection Reports in the WorkFlows Java client online Help.


This report was enhanced with the ability to select users by age range. On the User Selection tab, in the Age field, the library staff member can select users whose age is less than (<), equal to (=), or greater than (>) the age specified. this allows the library to prevent under aged patrons from being sent to collections (minimum age for collection) and/or to exempt senior citizens from collections (maximum age for collection).

The patron collection information is now output by the report in an XML-formatted file which is then sent via ftp to Unique Management for collection (previously it was a pipe-delimited file named collectsummary).

Additionally, the collection date is no longer stored in the user record STAFF entry, but will be linked to the user record from the debt collection tables.

Since collection information is now stored in separate debt collection tables in SirsiDynix Symphony and changes were made to the report output, several selection options previously included in this report are no longer valid. The following changes were made to the report.

• The Charge Selection tab was removed.

• On the Debt Collection tab, the Value of Charged Items option was removed. The Minimum Amount of Fees Due field can now include an unpaid bill/fee range. For example, a site can send users to collection agency if the amount owed falls between $10.00 and $35.00, by using the gadget in this field to select a range greater than 10.00 and less than 35.00. The report will only select users if the total amount of unpaid bills/fees falls within this range.

• The Export File tab was added. This tab now includes the following selections.

– Export File — In this field, the user must type name for the export file, and after the report is run, the file will be placed in the /Unicorn/Rpttemp directory on the SirsiDynix Symphony server. For example, the user can type the name “debtcollectMAIN” when running this report for the MAIN library. If the user does not name the report, the report output will appear in the finished report; no XML file will be created.

– Include Date/Time in Filename — If this check box is selected, a date/time stamp will be appended to the filename. The user will not have to specify a new name for the report each time it is run, and so will avoid overwriting existing reports. For example, if the user typed the name “debtcollectMAIN”, selected this option, and ran the report on May 30, 2008, the output file would be debtcollectMAIN.20080530.

• On the Fee/Update Options tab, the Include All Charges in Total Owed option was removed. A new Include All Bills option was added. Using this option, the user can determine if all bills from all libraries are included in the total owed, or only the bills from the selected libraries are included in the total owed. The user can select libraries on the Bill Selection tab.

Reports 99

Changes to the Collections Update Report

The Collections Update (Collectupdate) report will report any bill or payment activity for the specified library or all libraries against a user account that has been reported to collection agency (has the user status of COLLECTIONS).

If a patron account selected by the Update Process has a $0.00 balance for the library, the Collections Update report checks to see if the COLLECTIONS status should be cleared. If the user is reported to collections for another library, this report does not clear the COLLECTIONS status. If the user no longer has bills for any library or is in collections for any library, this report does clear the COLLECTIONS status (if it is not cleared already).

The patron collection information is now output by the report to an XML-formatted file which is then sent via ftp to Unique Management for updating collection information (previously there were two pipe-delimited files named collupdpartpay and collupdfullpay).

Since debt collection information is now stored in separate debt collection tables in SirsiDynix Symphony and changes were made to the report ouput, several selection options previously included in this report are no longer valid. The following changes were made to the report.

• The Bills tab no longer displays the Date Billed, Bill Associated with Item, Reason, and Balance Owed fields.

• The Charge Selection tab was removed.

• The Debt Collection tab was removed.

• The Export File tab was added. This tab includes the following selections.

– Export File — In this field, the user must type name for the export file, and after the report is run, the file will be placed in the /Unicorn/Rpttemp directory on the SirsiDynix Symphony server. For example, the user can type the name “debtupdateMAIN” when running this report for the MAIN library. If the user does not name the report, the report output will appear in the finished report; no XML file will be created.

– Include Date/Time in Filename — If this check box is selected, a date/time stamp will be appended to the file name. The user will not have to specify a new name for the report each time it is run, and so will avoid overwriting existing reports. For example, if the user typed the name “debtupdateMAIN”, selected this option, and ran the report on May 30, 2008, the output file would be debtupdateMAIN.20080530.

• On the Fee/Update Options tab, the option to Include All Charges In Total Owed was removed. This tab includes the following selections.

– Mode — The user can run the report in a “synchronization” mode by selecting to include all patrons in collections for a specified library or libraries. The output file will include only patron information and total amount due. Or, the user can select to include only those patrons with activity in the report output. The activity would include any new bills or payments, and will be for the bill library specified on the Bill Selection tab of the report. If the user doesn’t select a library, then any activity at any library will be included.


– Update Database Records — If selected, the report will update the database records. Clearing this check box will run the report in test only mode.

Collections Synchronization Report Removed

Because the Collections Update report now includes a “synchronization” mode that allows for reporting all users in collections for a specified library or libraries, the Collections Synchronization (Collectionsync) report was no longer needed. This report has been removed from the Debt Collection report group.

How Collections Are Handled for Selected Libraries

When running the Collections Information report for selected libraries, the debt collection records for users selected during the run of the report will specify that the user was selected for specific libraries. Only bills from the selected libraries will be added to the debt collection records. This also means that, when the Collection Update report runs, only new bills from the selected libraries and/or payments for those bills will be included in the report output. Once a user is sent to collections for specific libraries, the user will not be sent to collections for other libraries until the user is marked as all paid. If the library is part of a consortia and only certain libraries participate in debt collection, the Debt Collection reports should be run for all libraries that participate in order to ensure that users are correctly reported to the collection agency.

When a user is reported to collections for specific libraries, the user will come out of collections when all bills for the specified libraries are paid. For example, if a user is reported to collections for bills owed at the Main and Carnegie libraries, the user will be removed from collections when all bills for Main and Carnegie are paid. The user will be removed even if he or she has bills for another library, as along as the bills for Main and Carnegie are paid in full. (UNI-15817, UNI-13126, UNI-15827, UNI-16567, UNI-18869)


The updated debt collection reports are delivered with the Version 3.3 upgrade, and the Collections Synchronization report will be removed during the upgrade. The SirsiDynix Administrator needs to review the new functionality of these debt collection reports and make changes to the report selections, if needed. Additionally, the debt collection reports will need to be re-scheduled after the Version 3.3 upgrade.

During the Version 3.3 upgrade, a program will run that will move users reported to a collection agency on a 3.1 or 3.2.1 system into the new debt collection data structures added in 3.3. The program will select all userstatus records where the estimated fines are more than $0.00. The selected user records will be reported when the Staff Note Extended Information field contains the values “COLLECT-” or “COLLUPD-”, but not “PDINFULLRPT-”. These will be the users placed into debt collection for Version 3.3.

Sites should run the pre-3.3 Collections Update report one last time before upgrading to Version 3.3.

Reports 101

Maintenance Group Reports

Enhancements

New Report Added to Remove X12 Files That Do Not Have a Corresponding EDI Transaction

The Find Orphaned X12 Files (Edirpt) report has been added to the Maintenance report group to remove X12 files that do not have a corresponding transaction in the EDI Manager.


The Find Orphaned X12 Files (Edirpt) report has been added to the Maintenance report group to remove X12 files that do not have a corresponding transaction in the EDI Manager.

When the report runs, it compares the transaction list (EDI/Data/translist) with the EDI transaction files on the server. If a /Unicorn/Edi/Receive file or /Unicorn/Edi/Outgoing/vendorkey file exists but does not have a corresponding transaction, the file name is added to a list. If the report is run in test mode, the report prints a list of files found but does not remove them. If the report is run to actually delete the files, the files are removed immediately.

SirsiDynix recommends running the report first in test mode so users can see a list of files that will be removed by this report. To run the report in test mode, clear the Remove EDI X12 Files That Do Not Appear in EDI Manger check box on the report’s Remove tab. When the user is satisfied with the test results of the report, select the check box before running the report again to actually remove the listed files.

If the report is run to remove the selected files, and a file cannot be removed for any reason, the report output lists the name of the file and the reason it could not be removed. Either correct the condition that prevented the file' removal, or manually remove the file from the /Unicorn/Edi/Receive directory or the /Unicorn/Edi/Outgoing directory.

(UNI-16674)


Outreach Reports Group

Enhancements

Outreach Reports Required to be Rescheduled For Outreach Route Feature

If the following Outreach reports are scheduled prior to the SirsiDynix Symphony 3.3 upgrade, the reports will continue to run without the need for rescheduling after the upgrade.

• Purge Specific Interest (Purgeinterest)

• Purge User Records (Purgeoutreach)

All other Outreach reports that are scheduled prior to the SirsiDynix Symphony 3.3 upgrade must be rescheduled after the SirsiDynix Symphony 3.3 upgrade converts them. Contact the SirsiDynix Symphony administrator to reschedule the reports.


If the following Outreach reports are scheduled prior to the SirsiDynix Symphony 3.3 upgrade, the reports will continue to run without the need for rescheduling after the upgrade.

• Purge Specific Interest (Purgeinterest)

• Purge User Records (Purgeoutreach)

If the following Outreach reports are scheduled prior to the SirsiDynix Symphony 3.3 upgrade, the upgrade script will convert the scheduled reports into template reports with a run date set to NEVER. The converted reports must be rescheduled after the SirsiDynix Symphony 3.3 upgrade for them to run.

• Count Outreach Users (Outreachusrcnt)

• List Outreach Users (Outreachusrlst)

• List User Histories (Outreachusrlst)

• Print Route Pickup, Ship List (Routepickup)

• Print User Pickup, Ship List (Userpickup)

• Purge Specific History (Purgehistory)

• Search Route Interest Records (Routesearchint)

• Search User Interest Records (Searchinterest)

Reports 103

• Set Route Delivery ,Skip Date (Routedelivery)

• Set User Delivery, Skip Date (Userdelivery)

• Suggest User Interest Records (Srchintsug)

The Outreach report group has been removed from the WorkFlows C client. The report tab and the individual reports have been removed from Reports.

(UNI-17620)

Oracle Report Group

Enhancements

Extract Snapshots for Reporting Report Added to the Oracle Report Group

The new Extract Snapshots for Reporting (Rptviewextract) report has been added to the Oracle report group. The Extract Snapshots for Reporting report creates or refreshes “materialized views” or “snapshots” of certain catalog information and user address information in the SirsiDynix Symphony databases. These data snapshots can be used by a SQL reporting tool, such as Web Reporter, when producing “non-materialized views” or “normal views” for its reports.

Example

The Extract Snapshots for Reporting report creates a snapshot of cataloging data. Web Reporter can look at this data snapshot and create a view to print a report that lists just titles and author names.

Contact SirsiDynix Client Care for information on using Web Reporter or other SQL reporting tools with SirsiDynix Symphony.

The Outreach report group has been removed from the WorkFlows C client. The report tab and the individual reports have been removed from Reports. If Outreach reports were already been scheduled or set as a template before the WorkFlows C client upgrade to SirsiDynix Symphony 3.3, the scheduled report or template can still be modified, and new reports can be created from the template. In addition, the Outreach report group can still be added to an access list using the User Access policy. However, SirsiDynix does not support the use of Outreach reports in the WorkFlows C client.

If Outreach reports were already been scheduled or set as a template before the upgrade to SirsiDynix Symphony 3.3, the scheduled report or template can still be modified, and new reports can be created from the template. In addition, the Outreach report group can still be added to an access list using the User Access policy. However, SirsiDynix does not support the use of Outreach reports in the WorkFlows C client.



The new Extract Snapshots for Reporting (Rptviewextract) report has been added to the Oracle report group. The Extract Snapshots for Reporting report creates or refreshes “materialized views” or “snapshots” of certain catalog information and user address information in the SirsiDynix Symphony databases. These data snapshots can be used by a SQL reporting tool, such as Web Reporter, when producing “non-materialized views” or “normal views” for its reports.

Example

The Extract Snapshots for Reporting report creates a snapshot of cataloging data. Web Reporter can look at this data snapshot and create a view to print a report that lists just titles and author names.

This report is used only in libraries that use Oracle databases, and can only be run by a user with a user profile that has access to this report.

The Extract Snapshots for Reporting report should be scheduled to run daily, during off-peak hours, to refresh the data snapshots regularly. If this report is used to create or recreate the data snapshots from scratch, the report should be scheduled to run on the weekend or other off-peak time since the report may require hours to run, especially in library systems with large amounts of data.

Contact SirsiDynix Client Care for information on using Web Reporter or other SQL reporting tools with SirsiDynix Symphony.

(UNI-10355, UNI-10358)

When this report is run for the first time after the SirsiDynix Symphony upgrade, clear the Perform Incremental Refresh ASAP check box on the Snapshot tab so the report will create the data snapshots from scratch. After the data snapshots have been created, schedule the report to update the data snapshots each night or other off-peak time. Updating or refreshing data tables does not require as much time or processing as completely recreating the data tables.

SirsiDynix StaffWeb 105

SirsiDynix StaffWeb

Circulation

Enhancements

Due Date Receipts Can Print for Checkouts and Renewals

SirsiDynix StaffWeb has been enhanced to print due date receipts for checkouts and renewals. If the settings on the new Receipt tab in the Station Setup screen are configured to print due date receipts, a receipt will print when checkouts and renewals are completed on the Check Out or Patron Status screens.

The due date receipt can be configured to have a header message and/or a footer message. The body of the receipt can be configured to print certain pieces of information, such as the patron name, patron ID, checkout or renewal library, the current date, the date format used, copy information (author, title, call number, and/or copy ID), the total number of checkouts or renewals, and a list of the patron’s current checkouts.

Refer to the SirsiDynix StaffWeb online help for information on printing due date receipts from the Check Out screen or the Patron Status screen. Contact the library SirsiDynix StaffWeb administrator to configure due date receipt printing for checkouts and renewals.

SirsiDynix StaffWeb Administrator Notes

The Receipt tab has been added to the Administration tabs in SirsiDynix StaffWeb’s Station Setup screen. The Receipt tab is used to enable the printing of due date receipts for checkouts and renewals, and to configure the information that prints on the receipt.

To enable due date receipt printing, click Yes in the Print Due Date Slip option on the Receipt tab.

The due date receipt can be configured to have a header message, a footer message, and certain pieces of information.

• The header message can have up to five lines of text.

• Check boxes on the Receipt tab control which pieces of information will be printed on the due date receipt, such as the patron name, current date, copy information, and so on. Refer to the SirsiDynix StaffWeb online help for information about each check box.

• The footer message can have one line of text.


The following limitations apply to the due date receipts.

• The order of information presented on the receipt cannot be changed.

• The font and font size of the receipt text cannot be changed. By default, the Verdana font at 10-point size is used. If the workstation does not have the Verdana font installed, the Arial font or Helvetica font is used. If none of these fonts is available, the default sans serif font is used.

Refer to the SirsiDynix StaffWeb online help for detailed instructions on setting up receipt printing. (UNI-15803)

System Configuration 107

System Configuration

General

Enhancements

New Wizard Added For Outreach Module Configuration

The Module Configuration Wizards group on the Configuration toolbar has been enhanced with the Outreach module configuration wizard. The Outreach module configuration wizard specifies the hold range that will be used when Title level holds are placed automatically by the Search Interest wizard, the Search Route Interest Records report, and the Search User Interest Records report on materials that are requested for outreach users.


The Module Configuration Wizards group on the Configuration toolbar has been enhanced with the Outreach module configuration wizard. The Outreach module configuration wizard specifies the hold range that will be used when Title level holds are placed automatically by the Search Interest wizard, the Search Route Interest Records report, and the Search User Interest Records report on materials that are requested for outreach users.

The Outreach wizard is delivered with user access granted to the SIRSI and ADMIN users. SirsiDynix Symphony administrators should configure the User Access policies as desired to grant or deny access to the Outreach wizard.

(UNI-15630)

Acquisitions Configuration Group

Enhancements

Two New Fund Level Wizards Added

Two more Fund Level wizards, Fund Level 5 and Fund Level 6, have been added to the Acquisitions Configuration wizard group. Users can now assign up to 6 fund levels to a fund. The fund levels are optional fields.

The Outreach module configuration wizard is available only in library systems that use Demand Management.



The Fund Level 5 and Fund Level 6 wizards are enabled in the access lists for the sirsi and admin logins. Additionally, when a site upgrades to Version 3.3, logins that have the Fund Level 4 wizard enabled in their access lists will also have the Fund Level 5 and Fund Level 6 wizards enabled. (UNI-14400)

Cataloging Configuration Group

Enhancements

New Label Template Profiles Wizard

The Label Template Profiles Map wizard allows the user to define cataloging label templates to be used by specific library and item type combinations. For example, when the cataloger searches for a title and adds a new item for the MAIN item library with an item type of BOOK, the cataloging wizards can be configured to automatically print a book or spine label and use a label template specifically defined for MAIN/BOOK. If no label template profile is found for the particular library/item type combination, the label will not be printed, and the cataloging wizard will display a message.

As with the other map policies (such as the circulation map), the order of the map lines is important. The Label Template Profiles map is read by SirsiDynix Symphony from the bottom up, where the library/item type combinations are evaluated against the lowest lines in the map first.

The Label Template Profiles Map wizard contains the following attributes.

• Name — This attribute uniquely identifies the policy.

• Description — This attribute provides more information about the policy and its use by the library.

• Item Library — This attribute identifies the owning or item library. Select a library from the drop-down list.

• Item Type — This attribute identifies the item type for this label template profile. Select an item type from the drop-down list.

• Label Template — This attribute identifies the label template that will be used for this library/item type combination. Only bibliographic type templates are available for selection. Label templates are defined using the Label Designer wizard.


The Label Template Profiles wizard is delivered for the sirsi and admin logins with the Version 3.3 upgrade. Administrators should review the Label Template Profiles functionality and determine whether or not other users require access to this wizard.

(UNI-15148)

System Configuration 109

Circulation Configuration Group

Enhancements

Default Price Policy — Added Ability to Control the Number of Days Auto-refunds for Lost Items Can Be Accepted

Previously, a patron who lost an item and paid for it could have the paid lost bill refunded when the item was returned to the library regardless of how long ago the lost bill was paid. The time period between when the item was lost and when it was returned could be years as long as the Default Price policy allowed for automatic refunds. Now, libraries can set a practical limit between the time the lost item returned and the time in which the refund is allowed.

The Default Price policy contains a new attribute, Number of Days to Refund Paid-lost Bill. If the Automatic Refund attribute is selected, this new attribute becomes available. In this attribute, the user can type or select the number of days a lost item can be refunded (0-24999 days). If the user types the value 0 (zero), the system will interpret it as unlimited.


With the Version 3.3 upgrade, the Default Price policies will be updated with the new Number of Days to Refund Paid-lost Bill attribute. The default value is 0 (zero). Administrators should review the policies to see if this attribute should be set to another value.

(UNI-15829)

New Circulation Set Category Wizard

To support the new Circulation Sets feature in SirsiDynix Symphony 3.3, a new policy wizard was added to the Circulation Configuration group. The Circulation Set Category wizard allows users to define categories for circulation sets. The primary purpose of the Circulation Set Category policy is to establish controlled vocabulary that describes a group's characteristics for reporting purposes.

This policy contains the following attributes:

• Name — This attribute uniquely identifies the Circulation Set Category policy.

• Description — This attribute provides more information about the policy and its use by the library.


The new Circulation Set Category policy wizard will only display if Circulation Sets is configured for your system. Contact SirsiDynix Client Care to configure Circulation Sets. (UNI-1025)


Global Configuration Group

Enhancements

Can Configure System to Display Only MARC21 Formats, Only UNIMARC Formats, or Both MARC21 and UNIMARC

The Display UNIMARC Formats Global Configuration policy has been changed so that sites can configure their systems to display only MARC21 formats, only UNIMARC formats, or both MARC21 and UNIMARC formats in the WorkFlows client. The policy is now named “MARC Format Display.” By default, only MARC21 formats display.

The MARC Format Display policy appears on the Cataloging tab of the Global Configuration wizard and contains the following attributes.

• Display MARC21 Formats — Click this radio button to display only MARC21 formats in the client. This is the default value. If selected, Catalog Format policies with a record type of MARC are listed; policies with a record type of UNIMARC are not listed. The Bibliographic Map policy will only list MARC21 formats, and in cataloging wizards and reports, only MARC21 formats will display in the policy lists.

• Display UNIMARC Formats — Click this radio button to display only the UNIMARC formats in the client. The Bibliographic Map policy will include only UNIMARC formats, and the cataloging wizards and reports will display only UNIMARC formats in the policy lists. If selected, users will be able to create UNIMARC-formatted bibliographic records.

• Display Both MARC21 and UNIMARC — Click this radio button and both MARC 21 and UNIMARC formats will display in the client. The Bibliographic Map policy will include both types of formats, and the cataloging wizards and reports will include both types of formats in the policy lists.


With the Version 3.3 upgrade, the Display UNIMARC Formats policy will be replaced with the new MARC Format Display policy. By default, only MARC21 formats will display. The administrator should review the values of this new policy and determine if this default value should be changed for the library’s system. (UNI-16253)

Utilities 111

Utilities

General

Enhancements

Environment Variables Added to Run Commands or Scripts for Starting and Stopping an Oracle Database

In previous versions of Unicorn and SirsiDynix Symphony, delivered scripts could be used to stop and start an Oracle database along with SirsiDynix Symphony as needed for the library. However, some Oracle configurations prevented the delivered scripts from stopping and starting an Oracle database.

New environment variables have been added to allow system administrators specify the commands that are to be used to stop and start an Oracle database instead of using the delivered scripts. The environment variables also offer the ability to display a message or the contents of a text file if the library does not want to stop and start an Oracle database from a script.


In previous versions of Unicorn and SirsiDynix Symphony, scripts (such as the stop_oracle and start_oracle scripts in the Unicorn/Bin directory) could be used to stop and start an Oracle database. The third field of the Unicorn/Config/oracle.logon field determined if an Oracle database could be stopped and started by a script. If the third field contained a value, the Oracle database was assumed to be a remote Oracle database that could not be stopped and started. If the third field was blank, the Oracle database was assumed to be a local Oracle database, and the specified command or script could be used to stop and start an Oracle database. However, some Oracle configurations could require the Oracle listener to be used in some cases for connections, even when the Oracle database was local. In those cases, utilities such as the SirsiDynix Symphony Backup utility could not run properly since the Oracle listener would have to be used to connect to the Oracle listener.

To address the situation that could be presented by Oracle configurations, two new SirsiDynix Symphony environment variables have been added to the Unicorn/Config/environ file.

• SIRSI_ORASTOPCMD specifies the commands that are required to stop an Oracle database and the Oracle listener.

• SIRSI_ORASTARTCMD specifies the commands that are required to start an Oracle database and the Oracle listener.

This enhancement applies only in libraries that use Oracle databases with the UNIX or Linux operating system.


If the variables are set, the specified commands are used to stop and start the Oracle database. If the variables are not set, the start_oracle and stop_oracle scripts in the Unicorn/Bin directory are used to stop and start an Oracle database.

The SIRSI_ORASTOPCMD and SIRSI_ORASTARTCMD environment variables can offer system administrators the option of stopping and starting an Oracle database on remote systems, if the system administrator has the skills to use advanced scripting and remote access that does not use passwords.

Creating and Running Stop and Start Scripts on UNIX and Linux Systems The scripts to stop and start the Oracle database should be owned by the oracle user. The permissions on the script files should be set such that when the scripts execute, the user ID running the script (usually the sirsi user) is switched to the oracle user so the Oracle database processes are running as the oracle user. The sirsi user must belong to the same group as the oracle user so the sirsi user may execute the script.

The method to set the permissions on the script files and run the files depends on whether the operating system is a UNIX system or a Linux system.

• On UNIX systems, create the stop and start scripts while logged in as the oracle user. Then use either of the following commands to set the permissions of the script files so the sirsi user (or other user in the same group as the oracle user) can run the scripts as the oracle user.

In this example, start_oracle.sh is the name of the script to start the Oracle database.

chmod u+s start_oracle.sh

chmod 4660 start_oracle.sh

• On Linux systems, create the stop and start scripts while logged in as the oracle user. Then, perform the one-time step of logging in as the root user and using the visudo command to allow the sirsi user to become the oracle user. This step is necessary so that when the sirsi user runs the stop or start script, the sudo facility will switch users "on the fly" to the oracle user, and run the script as the oracle user. The SIRSI_ORASTOPCMD and SIRSI_ORASTARTCMD environment variables must be set to "sudo -u oracle scriptname" so the sudo facility will switch to the oracle user and then run the specified script file.

For example, the system administrator uses visudo to enable the sirsi user to become the oracle user and run the /home/oracle/unic_start.sh and /home/oracle/unic_stop.sh script files without a password. The sudoers file will contain the following line for the sirsi user:

sirsi ALL=(oracle) NOPASSWD: /home/oracle/unic_start.sh, /home/oracle/

unic_stop.sh

If the library does not want to stop and start an Oracle database from scripts, the SIRSI_ORASTOPCMD and SIRSI_ORASTARTCMD environment variables can be set to display a message or the contents of a text file.

Always use visudo to edit the sudoers file. Never use a plain text editor like vi or Emacs to edit the sudoers file directly.

Utilities 113

Examples of Setting the Environment Variables to Commands For example, the two environment variables are set as follows on a UNIX system.

SIRSI_ORASTARTCMD=/home/oracle/unic_start.sh

SIRSI_ORASTOPCMD=/home/oracle/unic_stop.sh

In the UNIX example above, full pathnames to the start and stop scripts are specified. The unic_start.sh script will be used to start an Oracle database, and the unic_stop.sh script will be used to stop an Oracle database.

In another example, the two environment variables are set as follows on a Linux system.

SIRSI_ORASTARTCMD=”sudo -u oracle /home/oracle/unic_start.sh”

SIRSI_ORASTOPCMD=”sudo -u oracle /home/oracle/unic_stop.sh”

In the Linux example above, the sudo program is used switch to the oracle user, and run the unic_start.sh and unic_stop.sh scripts as the oracle user. Full pathnames to the script files are specified. The unic_start.sh script will be used to start an Oracle database. The unic_stop.sh script will be used to stop an Oracle database.

Sample Scripts to Stop and Start the Oracle Database The following example shows a script that uses the sqlplus command to stop an Oracle database.

In the script, the ORACLE_HOME, ORACLE_SID, and NLS_LANG should be set as needed for the library system. In the path name variables, LD_LIBRARY_PATH is used for most UNIX and Linux systems, LIBPATH is used for AIX systems, and SHLIB_PATH is used for Hewlett-Packard UNIX (HP-UX) systems. All three paths can be set, but only the path relevant for the library’s type of system is used.

#!/usr/bin/sh

ORACLE_HOME=/export/home/oracle/OraHome_10g

ORACLE_SID=unic

NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1

PATH=:${ORACLE_HOME}/bin:${PATH}:

# ld path variable name varies per unix flavor, so set all three just in

case.

LD_LIBRARY_PATH=:${ORACLE_HOME}/lib: # typical unix/linux flavors

LIBPATH=:${ORACLE_HOME}/lib: # AIX

SHLIB_PATH=:${ORACLE_HOME}/lib: # HP_UX

export ORACLE_HOME ORACLE_SID NLS_LANG PATH LD_LIBRARY_PATH


sqlplus -s "/ as sysdba" <<EOS

shutdown immediate

EOS

lsnrctl stop

The following example shows a script that uses the sqlplus command to start an Oracle database.

In the script, the ORACLE_HOME, ORACLE_SID, and NLS_LANG should be set as needed for the library system. In the path name variables, LD_LIBRARY_PATH is used for most UNIX and Linux systems, LIBPATH is used for AIX systems, and SHLIB_PATH is used for Hewlett-Packard UNIX (HP-UX) systems. All three paths can be set, but only the path relevant for the library’s type of system is used.

The script includes a check to see if the Oracle listener is already running. If the Oracle listener is not running, the script starts it. If the Oracle listener is already running, the script will display a message.

#!/usr/bin/sh

ORACLE_HOME=/export/home/oracle/OraHome_10g

ORACLE_SID=unic

NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1

PATH=:${ORACLE_HOME}/bin:${PATH}:

# ld path variable name varies per unix flavor, so set all three just in

case.

LD_LIBRARY_PATH=:${ORACLE_HOME}/lib: # typical unix/linux flavors

LIBPATH=:${ORACLE_HOME}/lib: # AIX

SHLIB_PATH=:${ORACLE_HOME}/lib: # HP_UX

export ORACLE_HOME ORACLE_SID NLS_LANG PATH LD_LIBRARY_PATH

sqlplus -s "/ as sysdba" <<EOS

startup

EOS

lsnrctl status >/dev/null 2>/dev/null

Utilities 115

if [ $? = "1" ]

then

echo ""

lsnrctl start

echo ""

else

echo ""

echo " The ORACLE listener is already running."

echo ""

# lsnrctl status

echo ""

fi

Example of Displaying a Message Instead of Stopping and Starting an Oracle Database from a Script If the library does not want to stop and start an Oracle database from scripts, the SIRSI_ORASTOPCMD and SIRSI_ORASTARTCMD environment variables can be set to display a message. This example shows the SIRSI_ORASTARTCMD environment variable being set to display a message instead of starting an Oracle database.

export SIRSI_ORASTARTCMD="echo '--- The library does not allow Oracle to

be run here. ---';echo"

> oracleadmin run noprompt

Attempting to startup Oracle

Oracle version is 11.

Using SIRSI_ORASTARTCMD env variable

--- The library does not allow Oracle to be run here. ---

>

Example of Displaying the Contents of a Text File Instead of Stopping and Starting an Oracle Database from a Script If the library does not want to stop and start an Oracle database from scripts, the SIRSI_ORASTOPCMD and SIRSI_ORASTARTCMD environment variables can be set to display the contents of a text file. In this example, the administrator has created a text file named oramsg.txt in the /home/sysmessages directory. This file contains the following unformatted text, with a blank line before and after the text characters in the file.

********************************************************************


Our policy prohibits SirsiDynix Symphony direct access to

Oracle stop or start control. Contact the system administrator

for further explanation of this policy.

*************************************************************************

The administrator sets the SIRSI_ORASTARTCMD environment variable to display the contents of the text file when a command or utility tries to start an Oracle database.

export SIRSI_ORASTARTCMD="cat /home/sysmessages/oramsg.txt"

> oracleadmin run noprompt

Attempting to startup Oracle

Oracle version is 11.

Using SIRSI_ORASTARTCMD env variable

********************************************************************

Our policy prohibits SirsiDynix Symphony direct access to

Oracle stop or start control. Contact the system administrator

for further explanation of this policy.

*************************************************************************

>

(UNI-16152)