SirsiDynix Symphony 3 - lincnet.info · SirsiDynix welcomes and appreciates your comments on its documentation. We ... † SIP2 on page 22. Section 2: Enhancements 4 Release Notes

SirsiDynix Symphony 3.4

Release Notes

December 2010

© 2010 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™, and TeleCirc™ 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.4. Information in this document may also be compatible with later versions.

12/2010

iii

Section 1: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Comments and suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Section 2: Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Acquisitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Cataloging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Collection Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

OPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SIP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Section 3: Fixed bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Academic Reserves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Acquisitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Cataloging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Collection Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

EDI /X12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

OPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Serials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

SIP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

StaffWeb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Z39.50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Contents

Contents

iv

1

Section 1: Overview

These Release Notes cover new features, system requirements, and bug fixes since SirsiDynix Symphony 3.3.1. For more information about any of these notes, please see the SirsiDynix Symphony WorkFlows online help.

This document contains these sections:

• Enhancements on page 3

• Fixed bugs on page 23

Conventions used in this documentThis document uses these symbols:

Comments and suggestionsSirsiDynix welcomes and appreciates your comments on its documentation. We want to know what you think about our manuals and how we can make them better. If you have comments about this guide, please send them to [email protected].

Be sure to include the title and version number of the guide and tell how you used it. Then tell us your feelings about its strengths and weaknesses and any recommendations for improvements.

Symbol Description

This symbol indicates an enhancement or fixed bug that was the result or feedback from the user enhancement forum.

mailto:[email protected]

Section 1: Overview

2 Release Notes

3

Section 2: Enhancements

This section contains information about key features and enhancements in the SirsiDynix Symphony 3.4 software. The following includes a list of version 3.4 enhancements with their corresponding tracking numbers and a brief description of how each enhancement improves functionality. For more information on enhancements for this release, see the SirsiDynix Symphony online help.

The following components of the SirsiDynix Symphony software have been enhanced for version 3.4:

• Acquisitions on page 4

• Authority on page 7

• Cataloging on page 8

• Circulation on page 8

• Collection Exchange on page 15

• Configuration on page 15

• Miscellaneous on page 18

• OPAC on page 18

• Reports on page 21

• SIP2 on page 22


4 Release Notes

Acquisitions Tracking No. Enhancement Details

UNI-27106 Remit to Vendor field added A new tax-related invoice field, Remit to Vendor, has been added to the Invoice tab of invoice wizards. The field only appears on systems configured for tax. The Remit to Vendor amount takes rebate amounts and whether tax is paid to vendor into account. The value of the field is updated when an invoice line is created, modified or deleted. Invoice report selection and print tools have also been updated.


Acquisitions 5

UNI-27475 Enhanced audit trail information

In previous versions of SirsiDynix Symphony, audit trail information (generated when administrators created or modified a fund cycle) was stored in the Fund Extended Information entries of the fund record. Because Fund Extended Information entries are limited in size, some larger sites had reached the size limit, resulting in lost audit information.

Now with version 3.4, audit trail information is stored in its own database that can store large amounts of fund cycle audit trail information.

Note: The audit trail information collected by the Delete Selected Fund Extended Info (Delxinfo) report will only be placed in the Audit Trail database if that information was collected and is present on the 3.3.1 version previous to upgrading to version 3.4.

Sites can now enable the creation of audit trail information in the Global Configuration wizard. When this feature is enabled, the audit information will be stored in the new database with fund cycle-specific information every time a fund budget is modified or updated.

This feature replaces the audit trail option in the Acquisitions Session Setting wizard.

When an administrator adds a fund cycle, audit trail information is automatically created and stored. That information is updated when an administrator makes any modifications to any fund cycles or budget amounts in the following wizards:

• Add Fund

• Add Fund Cycle

• Duplicate Fund

• Modify Fund

• Modify Fund Budget

• Rollover Fund

• Transfer Budget Amount

Administrators can also configure the Rollover Fund Cycles Report to update audit trail information when new fund cycles are created (for more information, see “New Fiscal Cycle Selection Tab” in the Java WorkFlows help).

Administrators can retrieve audit trail information from the new Audit Trail tab that has been added to the following wizards.

• Add Fund

• Display Fund Specific Cycle

• Duplicate Fund

• Modify Fund

• Modify Fund Budget

• Transfer Budget Amount

Note: Audit trail entries display as read-only.

Tracking No. Enhancement Details


6 Release Notes

UNI-28455 Move Audit Trail In conjunction with UNI-27475, a new option has been added to the Acquisitions Session Settings to Display Archived Entry Fields in Audit Trail Tab. Administrators can use this option to control whether or not the Archived Entry field will display on the Audit Trail tab that displays in Fund wizards.

For more information, see “Session Settings Wizard: Acquisitions and Selection Lists” and “Audit Trail Tab” in the Java WorkFlows help.

UNI-30194 “Multiple funding” option no longer appears on reports where it does not apply

The “Multiple Funding” option has been removed from the Funding Selection tab of four reports where this option does not apply. The reports affected are:

• List Funded Order Lines

• Title Cost by Library/Fund

• Funded User Distributions

• Funded User Requests



Authority 7

AuthorityTracking No. Enhancement Details

UNI-25323 Propose Authority added for UNIMARC headings and for combined headings in both UNIMARC and MARC21 format

Staff who work with bibliographic records can now use the Validate Headings helper to propose an unauthorized UNIMARC heading for authorization. Furthermore, staff can now propose a combined Name/Title heading to be authorized in both UNIMARC and MARC21 format.

For more information about authorizing an unauthorized heading, see the “Validate Headings helper” topic in the SirsiDynix Symphony Online help.

UNI-25434 Thesaurus can now build up to 1000 cross-references for leading terms

In previous versions of SirsiDynix Symphony, the maximum number of cross references for a leading term was 100. Because some larger sites have more that 100 4xx terms in their authority records, the authority thesaurus has been enhanced to be able to build up to 1000 cross references for leading terms.

UNI-27006 UNIMARC authority support for multiple leading terms scripts in one authority record

The UNIMARC authority standard supports the same authorized heading in the same language but it supports multiple scripts differently. Firstly, the UNIMARC standard supports authorized headings in the same language. This standard supports authorized headings in multiple scripts similarly to the MARC21 authority standard (by having two different authority records, one for each script). UNIMARC has an additional standard which incorporates multiple scripts into a single record and differentiates them by the subfield |7 positions 4-5, script of base heading. SirsiDynix Symphony now supports this UNIMARC standard, allowing multiple authorized headings in the same language but different scripts in one authority record.


8 Release Notes

Cataloging

Circulation


UNI-20831 Item group editing The Item Group Editor wizard lets administrators create a list or group of items that can be modified together. For example, there may be a list of books that an administrator needs to move from circulation. Using the Item Group Editor, they can change the Circulate property for each item in the list at the same time. They can also save the list of items into a group that they can quickly call up for modifications without having to search the items again. Administrators can make modifications to a saved group of items or to an unsaved item list. They can also save the original settings for each item in the group so that they can restore those settings at a later time.

Administrators can manage groups of items to add or remove items to the group, create new groups, merge the items in two or more groups together, and delete groups.

For more information, see “Item Group Editor Wizard” in the Java WorkFlows help.

Note: Enabling this wizard causes unexpected variations in the adutext report’s runtime. Because of this, the Item Group Editor is delivered to users as disabled. For more information concerning this measure, please see the Symphony 3.4 Known Issues document.


UNI-16920 OPAC Hold Range attribute added to Hold Map policies

SirsiDynix Symphony's Demand Management Holds feature has been enhanced with the ability to set a hold range on holds placed from e-Library with a new OPAC Hold Range attribute in the Hold Map policies. The OPAC Hold Range attribute allows libraries to set the range by item type, library, and user profile. This will allow a consortium to honor reciprocity agreements between libraries within the system when users place holds from e-Library.

For example, if Rockefeller library only wants Rockefeller users to place holds on a NEWBOOK item type (so that users from other libraries are not allowed to place holds against Rockefeller's NEWBOOK), then Rockefeller library can control which users can place holds on NEWBOOK items by using the OPAC Hold Range feature.

The available OPAC Hold Range types are: System, Group, Library, and NO_HOLDS.

For more information, see “Hold Map Wizard” and “FAQ's: OPAC Hold Range Feature” in the Java WorkFlows help.


Circulation 9

UNI-16921 Mifare smart card reader functionality added to circulation wizards

Mifare Smart Card reader functionality has been added to the SirsiDynix Symphony circulation wizards and helpers. When this functionality is configured, users can scan Smart Cards with a Mifare Smart Card reader to automatically populate User ID fields in the wizards and helpers with Smart Card data.

When Mifare Smart Card is configured, administrators can automatically input and update information in the user records with the data embedded in the Smart Card. Wherever user ID input is required, administrators can scan the user's Smart Card to populate the User ID field with Smart Card data. When registering a new user, the user record will be populated with the Smart Card data. When wither modifying a user record or replacing a lost card, administrators can choose whether or not the Smart Card data will automatically replace the current user information. Administrators are also alerted when the user record fields contain values that differ from the Smart Card data, and they can then select which fields will be replaced by data from the Smart Card.

Three new Global Configuration policies have been added to support the Mifare Smart Card functionality in which administrators can define which address fields will be populated with the Smart Card data for each user address format (for more information, see “Configure Smart Card Address 1, 2, 3 Fields” in the Java WorkFlows help).

In conjunction with this new functionality, these Behavior properties have been added to the following wizards and helpers:

• New User Registration - This wizard and helper now display the “Prompt for Address# for Smart Card” Behavior property.

• Modify User - This wizard and helper now display the “Replace with Smart Card Data” Behavior property.

• User Lost Card - This wizard and helper now display the “Replace with Smart Card Data” Behavior property.

For more information, see “Smart Card Configuration” and “To configure a Smart Card reader” in the Java WorkFlows help.



10 Release Notes

UNI-20760 New Display Current Checkout counter added to the Checkout Wizard

The new Display Current Checkout Counter displays the total number of current charges for a user on the Checkout wizard window. This property has been added to the Checkout wizard and allows the user to configure the display of the current checkout counter.

If a user enables this property, the current checkout counter will appear above the checkout list.

If a user sets the Global Configuration policy “Configure Display of User Information Header” to display the user status header, the current Checkout count will appear in the status header.

If a user configures the Global Configuration policy “Configure Display of User Transaction Lists” to display lists in circulation wizards, a total checkout count will appear above the list of checkouts and current user checkouts.

UNI-20763 Change button names to “Save” and “Close” in user related wizards

To be consistent with other wizards in the WorkFlows client interface, next step button names have been changed to “Save” and “Close” in the Modify User wizard, Register New User wizard, and Copy User wizard.

UNI-20764 Improved browsing in user records with the User Search helper

While using the User Search helper in the Circulation module, users now can browse through a hitlist of user records, navigate away from the hitlist, and return to it without losing their place in the hitlist.

This change will affect all wizards that can be configured to start with the User Search helper.



Circulation 11

UNI-23922 Non-holdable item can now fill an active unavailable hold when charged

SirsiDynix Symphony now allows a non-holdable item to fill an active unavailable title hold when it is checked out.

For example, a patron places a title level hold on a book. The library has multiple titles across the system, including copies with non-holdable item types (such as NEW_BOOKS). While in the library, the patron sees a copy of the title on the new book shelf and pulls this non-holdable copy to check out. When the patron checks out this copy, the system will automatically fill the user's existing title level hold for the book.

The following configuration options are available for non-holdable items:

• Fill active unavailable hold when charging a holdable copy (default).

• Fill active available or unavailable title hold when holdable copy is charged.

• Fill active available or unavailable title hold when holdable or non-holdable copy is charged.

These configuration options affect items checked out by library staff, by self-checkout systems, and in WorkFlows offline mode. Books by mail holds and blanket holds are also affected.

For more information, see “FAQs: Automatically Filling an Active Unavailable Hold When Charging a Non-holdable Item” in the Java WorkFlows help.

UNI-24055 User Standing Map A User Standing Map policy wizard has been added to SirsiDynix Symphony. This policy provides libraries with the ability to control the library privileges allowed in a specific client (WorkFlows, e-library, self-check, etc.) when a user is assigned a certain status. The User Standing Map policy includes the following attributes: Command, User Standing, Client Types, Action. By creating specific attribute combinations, libraries can control a user's library privileges for checkout, renewal, paying bills, and placing and suspending holds. The library also controls which Symphony client (WorkFlows, e-Library, self-check, and more) will extend or deny these privileges.

For more information, see “User Standing Map Wizard” in the Java WorkFlows help.

UNI-24832 Birth date may now be searched in user record

Library staff can now search user records by birth date in the Java WorkFlows client. When using the User Search helper, staff members can select “Birth Date” from the Index drop down to search user records by birth date.

For more information, see “User Search Helper” in the Java WorkFlows help.



12 Release Notes

UNI-25744 Smart Card configuration settings for address fields

Users now have three new global configuration policies available to support the Mifare Smart Card functionality. The user can define which address fields will be populated with the Smart Card data for each user address format. For information on these configuration options, see “Global Configuration policies to configure” in the Java WorkFlows online help.

UNI-26830 Smart Card corrected User Address Template.

Previously in any wizard or helper where a user address could be created or edited, all editable user address fields were available for selection regardless of address template policy.

This has been fixed so that only proper address template policy fields are displayed in the available user address fields.

UNI-27341 New right-click menu options for Circulation wizards

The WorkFlows client now supports right-click menus for several Circulation wizards and other WorkFlows functions. These right-click menus are “popup” menus that contain commands and options that can be performed against a selected record or group of records. The right-click menus are available using the mouse right-click or the CTRL+click command.

Users can configure the right-click menu options via the new Configure Context Menu policy. This policy is available from the Circulation tab of the Global Configuration wizard.

For more information about the new right-click menu options, please see the WorkFlows help topic “Right-click Menus.”

UNI-27430 Add an option to user search helper to display birth date

Libraries can now configure the User Search helper to display a user's birth date in the user search results list. The “Display Birth Date” property is found on the Behavior tab of the User Search helper properties.

For more information, see “User Search Helper Properties” in the Java WorkFlows help.

UNI-27840 Transaction list only displays “active” checkouts -need an option to pull back all checkouts

The transaction lists that display in circulation wizards will now display all checkouts for a user, including active and inactive checkouts. Circulation transaction lists display when the Global Configuration policy “Display Circulation Transaction Lists in Circulation Wizards” is enabled. This feature is primarily used by SirsiDynix Symphony K12 systems.

For more information, see “Display of User Transaction Lists In Circulation Wizard Policy” in the Java WorkFlows help.



Circulation 13

UNI-27898 New Onshelf Items wizard to display contents of the hold item database

The Onshelf Items wizard, found in the holds wizard group, is used to display items from the hold item database. Administrators can now view the output of the List Onshelf Items with Holds report from a single wizard. This wizard imitates the functionality of the List Onshelf Items with Holds (Pullonshelfhld) report, but it can be configured to update in real-time as holds are placed, cancelled, suspended, or unsuspended manually throughout the day, allowing administrators to update the hold item list interactively. By default, this option is disabled. Contact SirsiDynix support to request this configuration.

If the system is configured to dynamically update the Onshelf Hold Items list, a Global Configuration policy, “Configure Locations for Onshelf Items Wizard,” is available. This policy appears on the Circulation tab and allows administrators to control the holdable locations that will be considered when building the hold items list for the Onshelf Items Wizard (for details, see “Configure Locations for Onshelf Items Wizard” in the Java WorkFlows help).

For more information, see “Onshelf Items Wizard” in the Java WorkFlows help.

UNI-28365 WorkFlows supports custom PIN policy control

In the WorkFlows Java client, the User PIN policy wizard allows libraries to define the PIN requirements the software enforces when staff modify a user PIN. Administrators can set the requirements for length (up to 25 characters) as well as any uppercase/lowercase, numeric, or special character requirements. This policy is used in conjunction with the Use Policy PINs configuration option. The Modify User wizard now includes a User PIN Change gadget so that staff may see whether the PIN they specify meets the PIN policy requirements.

To use a PIN policy, contact SirsiDynix support and request the Use Policy PINs configuration option. For more information, see “User PIN Policy Wizard” in the Java WorkFlows help.



14 Release Notes

UNI-28384 New server policy for the List Onshelf hold wizard

The Configure Locations for Onshelf Items Wizard policy is a Global Configuration policy that is read by the WorkFlows client at startup and stored as a global variable. It appears on the Circulation tab of the Global Configuration wizard. This policy allows administrators to control the holdable locations that will be considered when building the hold items list for the Onshelf Items wizard. This default setting is similar to that seen in the List Onshelf Items with Holds (Pullonshelfhld) report. This policy only displays when the system is configured to dynamically update the hold item list when using the Onshelf Items wizard.

For more information about this policy and the Onshelf Items wizard, see the WorkFlows client online Help topics “Configure Locations for Onshelf Items Wizard Policy” and “Onshelf Items Wizard.”

UNI-28628 Name field character limits extended

The character limits for suffix, first, middle, and preferred User Name fields have been extended, allowing library staff members the ability to enter longer names when creating new user records. The first, middle, and preferred name fields now allow up to 25 characters, and the suffix field now allows up to 15 characters.

For more information, see “Basic Info Tab: Users” in the Java WorkFlows help.

UNI-28849 Item price field added to receipt fields

A new item price (“Price”) field has been added as a configurable field for date due slips and charge receipts. When configured, the item price field will print on available date due slips and charge receipts.

For more information, see “Receipt Fields for Circulation Receipts” in the Java WorkFlows help.



Collection Exchange 15

Collection Exchange

Configuration


UNI-24298 Collection Exchange supported on Microsoft SQL

With the release of version 3.4, Symphony's Collection Exchange will now be supported on MSSQL Server. Now sites using MSSQL will be able to access and use the Collection Exchange module.

UNI-26231 New policies added for Exchange Dates and Pending item location

The Global Configuration wizard has been enhanced with two new policies on the wizard's Collection Exchange tab. The new Collection Exchange policies are as follows:

• The Exchange Date When Shipping Items policy gives libraries the option of specifying which date is to be used as the exchange date when confirming item shipments. This policy has the following attributes.

• Use Date of Activation as the Exchange Date populates the Date Exchanged field in the exchange item record with the date that was specified in the Exchange Date in the Activate Exchange Libraries wizard. This attribute is the default selection.

• Use Current Date as the Exchange Date populates the Date Exchanged field in the exchange item record with today's date.

• The Pending Item Location policy allows the library to select the current location that is to be used when the item is exchanged but not yet shipped. The attributes for this policy are defined with the Location wizard. Libraries may use a customized Location policy name to indicate that the exchanged items are pending shipping, thus preventing patrons using the e-Library or an OPAC from thinking that the items are in the stacks.


UNI-1736 Zip codes print on same line as city and state on notices

Formerly, when an administrator printed a notice that contained an address, the address zip code appeared on a separate line below the city and state. Now administrators have the option to print the address with the zip code on the same line as the city and state. This option is found in the Report wizard in the Configuration module.

For more information, see “Report Wizard” in the Java WorkFlows help.


16 Release Notes

UNI-26653 Configuration option added to control how the user name key is built

A new configuration option for building user name keys now allows libraries to determine the order of the name fields in the user name key when they create or edit a user record. The following options are available in this configuration:

• Last name, suffix, first name, middle name (this is the default option)

• Last name, first name, middle name, suffix

• Last name, first name, middle name

The name key is used for browse searching. This option also affects how names are sorted (or the order in which they will appear) in the user browse search results and on reports. For more information, see “FAQ's: Searching User Records” in the Java WorkFlows help.

Note: In order to change the name key configuration, please contact SirsiDynix Support to request the option of your choice.

Additionally, a new Rebuild User Name Keys (Rebldusernmkey) report has been added to the Administrative group reports. This report runs through all user records and modifies the name keys in existing user records to match the format configured on the Symphony server. For more information, see “Rebuild User Name Keys Report” in the Java WorkFlows help.

UNI-28655 Label in library policy for checking closed dates/days -onshelf hold wizard modified

Because the Library policy's Closed Dates in List Onshelf Holds attribute is now used by both the Onshelf Items wizard and the List Onshelf Items with Holds report, the attribute was renamed “Onshelf Items Will Not Be Selected for Holds on Closed Dates.” This attribute is used to determine whether or not closed dates should be considered when libraries are selected for inclusion in the List Onshelf Items with Holds report and the Onshelf Items wizard.

For more information, see “Closed Day Tab” in the Java WorkFlows help.



Configuration 17

UNI-29123 “Bill Maintenance Libraries” setting separated for Bill User and Pay Bill wizards

Previously, in a multi-library system, library staff used the “Bill Maintenance Libraries” setting in the Library policy to specify the libraries they could access to create user bills in the Billing a User wizard. This setting also controlled the specific libraries the user could access to pay bills using the Paying Bills wizard. A new “Pay Maintenance Libraries” setting in the Library policy separates library specifications for billing and bill payment. Libraries can now use the “Pay Maintenance Libraries” attribute to limit access to pay bills for specific libraries and still allow library staff the ability to create bills for all users with the “Bill Maintenance Libraries” setting.

This new “Pay Maintenance Libraries” setting is available by upgrading to SirsiDynix Symphony 3.4 or by installing 3.3.1 Patch Cluster 2, and it is delivered as a set to the “Bill Maintenance Libraries” attribute.

For more information on this setting, see the “Library Wizard” topic in the Java WorkFlows help.



18 Release Notes

Miscellaneous

OPAC


UNI-28881 Wizard name and subsequent wizard actions reflected in main window captions

The WorkFlows client windows have been enhanced to reflect the wizard name and subsequent wizard actions in the main window caption. Now, the wizard's name will display at the top of the WorkFlows main window, next to the SirsiDynix Symphony WorkFlows logo, when library staff opens a wizard. When a new window is opened within the wizard flow, or when message or confirmation windows pop up, the caption will reflect the wizard name; a colon; and the wizard action, message, or confirmation. (For example, when a staff member opens the Checkout wizard and an alert message displays for a patron during checkout, the caption will say “SirsiDynix Symphony WorkFlows: Checkout: User is DELINQUENT.”) When multiple windows are open, the window name that is active (in focus) will display in the caption.

This change supports screen readers and RFID applications, and allows them to more easily read where the staff member is in the wizard flow.

UNI-30766 Gnuwin32 and Cygwin changes in Symphony 3.4

Users will note that Gnuwin32 has replaced Cygwin as the default UNIX utility tool on Windows systems in Symphony 3.4. This enhancement was made in order to minimize Symphony upgrade and install problems, increase the process speed of UNIX commands, and improve Symphony's stability.

Some customers running custom reports including Cygwin commands may need to modify those reports, replacing problem Cygwin commands with Gnuwin32 commands.

For a list of those commands, please see the API note titled “Variations between Gnuwin32 and Cygwin” in the API notes.


UNI-17075 Right-to-left display in RevD e-Library revD now displays right-to-left oriented languages. In the past, the individual characters in these fonts displayed correctly, but the words displayed from left to right. e-Library now automatically adjusts the display settings when a user chooses a right-to-left oriented language for display.


OPAC 19

UNI-21926 Increased character limit for SOPT_CUSTOM fields

Previously in e-Library, there was a 500 character limit for any SOPT_CUSTOM fields defined in the environment files. This limit has been increased to 1950 characters for UNIX systems and 950 characters for Windows systems.

SirsiDynix Symphony Administrator Note

The increase to 1950 or 950 characters affects the following variables when defined in the system.env and the local envn#.env files:

SOPT_CUSTOMFORMAT||

SOPT_CUSTOMLANGUAGE||

SOPT_CUSTOMFORMAT||

SOPT_CUSTOMITEMTYPE||

SOPT_CUSTOMLOCATION||

SOPT_CUSTOMICAT1||

SOPT_CUSTOMICAT2||

SOPT_CUSTOMCLASS||

UNI-21953 Persistent user login Previously, a user's login would persist if they logged in at the upper-right login box. It would only fail to persist if the user logged in at the time of a requested action, such as in My Account or when placing holds.

New functionality has been added to e-Library that allows the system to remember the user's login credentials and automatically use them for the user's entire web session, which requires the user to log in only one time, no matter which login box they use.

Libraries can change this setting back to the previous functionality through the e-Library Configuration Admin. See the Configuration Admin online help for more information.

UNI-29031 New Enterprise integration themes for e-Library

e-Library includes four new themes that integrate with SirsiDynix Enterprise 3.3x. The new themes are named DarkGrey, RedGrey, Tabs, and Lite. Administrators can select a theme by changing the THEME variable in the system.env file for e-Library.

For more information about choosing a theme, see “Choosing an Enterprise integration theme” in the e-Library Administrator's Guide.

UNI-29429 Use local cache for translations on remote e-Library servers

By default, new installations of remote e-Library use the local cache of multi-lingual labels, rather than pulling the labels from the ILS. This change was made to provide better performance for remote e-Library servers. This setting can be changed in the WEBSESSION_TRANSLATE variable in the Webcat\Config\webconfig file.

For more information, see “Look and feel” in the e-Library Administrator Help.



20 Release Notes

UNI-29949 Use Syndetics widget on the item detail page in e-Library

In the “A Look Inside” section of the item details page, e-Library now uses the Syndetics widget to display item information. In order to use the widget, users must enable Syndetics enriched content. For more information, see “Integrating third party enriched content” in the e-Library Admin Help. The Video Clip enriched content requires that Adobe Flash Player be installed on the computer with the web browser that accesses e-Library.



Reports 21

ReportsTracking No. Enhancement Details

UNI-26852 New Onshelf Items wizard to display contents of the hold item database

The Onshelf Items wizard, found in the holds wizard group, is used to display items from the hold item database. Administrators can now view the output of the List Onshelf Items with Holds report from a single wizard. This wizard imitates the functionality of the List Onshelf Items with Holds (Pullonshelfhld) report, but it can be configured to update in real-time as holds are placed, cancelled, suspended, or unsuspended manually throughout the day, allowing administrators to update the hold item list interactively. By default, this option is disabled. Contact SirsiDynix support to request this configuration.

If the system is configured to dynamically update the Onshelf Hold Items list, a Global Configuration policy, “Configure Locations for Onshelf Items Wizard,” is available. This policy appears on the Circulation tab and allows administrators to control the holdable locations that will be considered when building the hold items list for the Onshelf Items Wizard (for details, see “Configure Locations for Onshelf Items Wizard” in the Java WorkFlows help).

For more information, see “Onshelf Items Wizard” in the Java WorkFlows help.

UNI-26891 Many WorkFlows reports output in standard format (XML) for use in third-party programs

SirsiDynix Symphony now supports XML output for many reports that use a print tool (such as Print Item or Print User) to generate results in the Java WorkFlows client. This new feature allows administrators to export report results into a third-party program for further use. XML can be read by a wide variety of programs, including commonly available Internet browsers, word processors, spreadsheets, and database applications.

Each printing tool that can produce XML output comes with a default style sheet. This style sheet defines the look and feel of the XML output for all reports that use that specific print tool. Administrators can also create custom style sheets to apply to a single report, group of reports, or all reports. The Java WorkFlows client allows administrators to select a default program for viewing report output formatted by a style sheet. For more information, see “Style Sheet Tab” in the Java WorkFlows help.

Reports that use a notice tool to generate XML output (such as Bill Notice or Hold Notice reports) may be exported to a third-party program. However, these reports do not support style sheets at this time and may not be viewed from within the Java WorkFlows client.

For more information about using XML output and for a complete list of reports with XML output, see “Using reports with XML output” in the Java WorkFlows help.


22 Release Notes

SIP2

UNI-29219 Print Item tool displays checkout and renewal information in XML output

In connection with the XML output enhancement (see UNI-26891), any report that uses the Print Item tool will include extended circulation information when the XML output option is selected. The following additional fields are included in the XML output of the reports created with the Print Item tool.

• Total Checkouts and Renewals

• Ongoing Checkouts and Renewals

• Date Last Cleared

UNI-29716 User name needs expanded into XML elements

Previously, the user name field would display as a single element, the same for each report. Now, reports with XML output that display user records provide enhanced flexibility for displaying user names. Libraries can arrange and display the individual elements of the user name field by customizing the style sheet. For example, libraries can configure one report to refer to a user as “Mr. Doe,” and another report to refer to the same user as “Doe, John.”

For more information, see “Style Sheet Tab” in the Java WorkFlows help.


UNI-29865 SIP checkin is not sending an audible alert when a “LOST” item is checked in.

When a user attempted to discharge a “LOST” item, SIP2 checkin would not send an audible alert or a screen message to indicate that the item had been reported “LOST.” This would occur when a site's configuration allowed the checkin of “LOST” items. When a site's configuration settings did not allow the checkin of “LOST” items, the user would receive a screen message about handling the item manually, but not an audible alert.

Now a new SEND_LOST_CHECKIN_ALERT configuration flag option can be added to the sip2.cfg file. When you enable this option, the SIP server will send alerts and messages when users attempt to check in “LOST” items whether or not your library's configuration settings allow the checkin of “LOST” items.

For more information on this configuration flag, see the “SIP2 Single Port Configuration File (sip2.cfg)” topic in the Setting up the SIP2 Server guide.


23

Section 3: Fixed bugs

This section contains a list of all resolved issues, or fixed bugs, for SirsiDynix Symphony 3.4. The following includes a list of fixed bugs for the SirsiDynix Symphony 3.4 release, sorted by the component in which they appear. Each note includes the corresponding tracking numbers, and a brief description of each issue and how it has been fixed

Issues have been resolved in each of the following components for the SirsiDynix Symphony 3.4 release:

• Academic Reserves on page 24

• Acquisitions on page 24

• Authority on page 27

• Automation on page 27

• Cataloging on page 28

• Circulation on page 30

• Collection Exchange on page 37

• Configuration on page 40

• EDI /X12 on page 42

• Miscellaneous on page 42

• OPAC on page 44

• Performance on page 50

• Reports on page 50

• Request on page 56

• Searching on page 56

• Serials on page 56

• SIP2 on page 58

• StaffWeb on page 61

• Z39.50 on page 62


24 Release Notes

Academic Reserves

Acquisitions

Tracking No. Summary Description

UNI-22133 Reserves Pickup List, Update report was not producing expected output

The Reserves Pickup List, Update (Rsvpickup) report should produce two lists for available holds made unavailable: one showing holds for which availability notices have been sent, and one showing holds for which availability notices have not been sent. Previously, this report was instead producing a single list of the holds that have been made available.

This has been fixed so that the Reserves Pickup List, Update report will now produce the two expected lists of available holds made unavailable, along with details about these unavailable holds.

UNI-27766 Reserve copy hold filled and hold counter in item record decremented incorrectly

Previously, when library staff changed a reserve record's status to DORMANT and then to COLLECT, a reserve copy's hold would be filled (set to inactive status or inactive reason FILLED), and the item's hold counter would be decremented twice.

This has been fixed so that the reserve programs now check for active holds before the status of the reserve record is updated, and the same hold will not be cancelled twice.


UNI-19202 Reports with funding and funding segment type information left out the last “amount split” funding segment

Previously, when the “Amount split” radio button was selected on the Funding Selection tab of the List Funded Orderlines report, the report incorrectly excluded the funds used for the last amount split funding segment (REST). Other reports that are affected are: Count Order Fundings, List Order Fundings, Title Cost by Library/Fund, Funded User Distributions and Funded User Requests.

This has been fixed, so that “Amount split” displays all the amount split funding segments in a funding with multiple sources, including the last (REST) funding segment.

UNI-24123 Display All Orderlines helper would hang in Duplicate Order wizard

Previously, if library staff duplicated an orderline and then clicked on the Display All Orderlines helper in the Duplicate Order wizard, an exception error would occur causing the WorkFlows client to hang.

This has been fixed so that the Display All Orderlines helper will open without error.


Acquisitions 25

UNI-25936 Wizard fields were not retaining data when moved between wizards in Multiple Windows Mode

When using the WorkFlows client in Multiple Windows Mode, if a library staff member had multiple wizards open, including the Add Vendor and/or the Modify Vendor wizard, then data entered in the wizard fields was not retained. When the staff member moved between wizards, the data was cleared.

This has been fixed so that moving between wizards in Multiple Windows Mode does not cause the user to lose any information in wizard fields.

UNI-26219 Incorrect workslip information when libraries received two standing orders

If a user selected the Always Print a Workslip When an Orderline is Received property in the Receive Orders wizard properties, when the user received two different standing orders, the first workslip would print correctly, but the second workslip printed with the Quantity and Distribution information from the first workslip.

This has been fixed so that the workslips for the corresponding orders now prints with the correct Quantity and Distribution information.

UNI-26227 Receive Orders wizard search by ISBN would not show correct title

Previously, when using the receive order setting in default properties, a bibliographic search (like ISBN) in the Receive Orders would not highlight the orderline associated with the title.

This has been corrected so that the search will go directly to the orderline of the title based off of the bibliographic search.

UNI-27665 Problem with invoice data after 3.3 upgrade

When upgrading to SirsiDynix Symphony 3.3 or 3.3.1 from version 3.1 or earlier versions, sites using the acquisitions module were experiencing corruption of the invoice and invoice line databases. This only occurred on ISAM systems and did not occur when a site upgraded from version 3.2.

This has been fixed so that there is no corruption of the invoice and invoice line databases during upgrade.

UNI-27775 “Make items available at owning library” property ignored in Add Ordered Items to Catalog wizard

This problem occurred when library staff used the Add Ordered Items to Catalog wizard. If the “Make items available at owning library/location; do not trap items to satisfy holds” property was selected in the wizard behavior properties, the item would show a location of IN_TRANSIT when the staff member tried to add an item. This resulted in the staff member having an extra step to change the location.

This has been fixed so that when the “Make Items Available at Owning Library/Location; Do Not Trap Items To Satisfy Holds” option is used, added items are available at their owning library/location (not IN_TRANSIT).



26 Release Notes

UNI-27792 9xx Ordering was not honoring ISBN selected for ordering on book vendor website

Previously, when a library created an order from a vendor's website, the order would select the correct title, but the wrong ISBN.

To ensure that the correct item with the correct ISBN is received by the vendor, the new Orderline ISBN and subfield fields have been added to the Order Options Tab in the Load Bib with Order Info (Biborderload) report. This tag and subfield allows sites to specify which 9xx tag (anything except 999) contains the vendor's preferred ISBN. If the 9xx field and subfield is provided by the library, then the report will use that ISBN. Alternatively, if the tag does not contain an ISBN (if it is empty or contains other data), the first ISBN of the vendor's record is retrieved and copied to the specified 9xx field and subfield. Then the ISBN present in the 9xx field is the one used for the order.

If the provided 9xx field does not contain an ISBN (if it is empty or contains other data), the 9xx field from the existing record will be removed completely and replaced with the new one.

UNI-28174 Wrong ISBN auto-populated when creating orders from keyboard

Sites using SirsiDynix Symphony 3.3.1 found that using the Add Basic Order wizard to create an orderline for a new title for which there was a single existing title from the same author caused the newly created orderline to use the ISBN from the already existing title.

This has been fixed so that the new orderline for the new title will have a different ISBN than the existing title.

UNI-29403 Holds message did not display when using Add Ordered Items to Catalogue in 3.3

Users adding or updating on-order titles via the Add Ordered Items to Catalog wizard in the Acquisitions module would find that the default message, “This title has holds” would not display when they loaded on-order titles which had linked holds. This problem existed within the Java WorkFlows client only.

Due to modifications within the Java WorkFlows client in Symphony 3.4, users will now find that the message now displays as expected.



Authority 27

Authority

Automation


UNI-25422 Cross references incorrect for reference tags missing subfield

Previously, if a cross reference tag did not contain a subfield “a” when UNIMARC authority records were loaded, the generated cross references were incorrect.

This has been fixed so that the authority load program will not generate cross references if the tag does not contain the subfield “a” (which is used to find the beginning of the data portion of the tag).

UNI-26697 Problem with UNIMARC authority indexing

With the implementation of UNIMARC authority in SirsiDynix Symphony 3.3, a new routine was written to find the beginning of an authority entry by looking for the |a. This was to enable skipping over control subfields that could exist in the records prior to the subfield “a”. If the subfield “a” was not found, the entry was not returned.

This implementation meant that 1xx and 4xx tags of authority records that did not contain subfield “a” as the first subfield were not posted to authority indexes. MARC21 authority subdivision formats indexed in 3.2.1 that did not contain subfield “a” were also not included.

This has been corrected so that if a subfield “a” is not found, the entire entry will be returned.

UNI-27366 Indexing broken when authority record had no data in subfield

Previously, if there was any authority record with a subfield “a” that contained no data, when a library tried to index or re-index that record, the indexing process would go into an infinite loop. The index would never process the authority record with the empty subfield “a”, so it could not continue to the next record.

This has been fixed so that indexing will continue, even if there is an authority record with no data in subfield “a”.


UNI-25454 Full System Backup Operation Corrected

Previously, an unexpected error message would display in the BACKUP/SYSTEM Root Password screen when if a user attempted a full system backup of the SirsiDynix Symphony system. When the user pressed Enter, the backup returned to the Operation selection. If the user selected Save and typed a password, the backup prompted for the root password again.

This has been fixed so that both paths (hitting Enter, or selecting Save and entering a password) will have the desired outcome.


28 Release Notes

CatalogingTracking No. Summary Description

UNI-24989 Items with the “AVAIL_SOON” location appeared to be available for circulation prematurely

Before this fix, items in the library catalog with the current location of available soon (AVAIL_SOON) would lose that current location if staff changed the home location before saving the record. Instead of “AVAIL_SOON,” the current location would change to match the new home location. This caused the items to appear in the catalog prematurely as if they were available for circulation.

This has been fixed so that the current location of “AVAIL_SOON” will not change when the home location is changed. When the items are later scanned in a circulation wizard (e.g., Checkout, Discharging), the current location will be updated automatically.

UNI-26055 Analytic was stripped from call number when record was overlaid via SmartPort

Previously, the call number analytic (|z) was being removed from the first call number when a matching record was overlaid with SmartPort in the Java WorkFlows client.

This has been fixed so that the call number record will retain its analytic (|z).

UNI-26503 Display of shelving location was missing from WorkFlows Java Client

Previously, when users accessed the item information in the call number/item tree via the Item Search and Display wizard, the Current Location field would not display for any item that had a current location with the RESHELVING type of location. The RESHELVING location would only display in the item glossaries and the item lists display of the Bibliographic Description helper. This was not a problem in the WorkFlows C client.

This has been corrected so that items in the tree will display RESHELVING in the Current Location field.

UNI-27012 Setting catalog format assumed MARC21 record if unable to be determined from bib map policy

Previously, when users would load UNIMARC records, if the bib level could not be found in the bibliographic map policies, the catalogload report would display this absence as a warning. The system would then assume that the record MARC standard was MARC21. This caused an error that the character set didn't match, since the system thought the MARC standard was MARC21 and was looking in the leader instead of the 100 tag.

This has been corrected so that the catalogload report should only display the first warning and load the record in the UNIMARC format.

UNI-27141 False error message when copy number was changed

When a staff member edited an existing copy number, an error message would appear stating that the item was not in the catalog, even though the item had been correctly saved.

This has been fixed so that there is no error message when a copy number is edited and saved.


Cataloging 29

UNI-28000 Users unable to enter file name in MARC Export wizard on Mac client

Previously, two errors were occurring in the MARC Export wizard. First, library staff could not enter a file name before saving. Second, if the user tried to use the gadget next to the “File Name on Client” field and typed the file name, the OK button grayed out. The file could not be saved. This error occurred on WorkFlows Mac clients only.

This has been fixed so that users can enter file names and files can be saved in the MARC Export wizard as expected.

UNI-28277 MARC-8 to Unicode conversion corrupted Arabic text in 880

Previously, when the SmartPort wizard captured a MARC-8 record from the Library of Congress and converted it to Unicode, the Arabic text in the 880 field was being corrupted. The conversion program was not properly handling the conversion of the Arabic text in MARC-8 to Unicode.

This has been corrected and now the Arabic text in MARC-8 records is converted to Unicode correctly.



30 Release Notes

CirculationTracking No. Summary Description

UNI-13190 Error viewing or downloading Circulation Mailer report

On rare occasions, library staff could experience a problem when viewing or downloading the formatted output of the Circulation Mailer (Mlrcir) report. If the staff member tried to view or download the formatted report output from the Finished Reports list, the report output would sometimes not display or download. Other times, the report output would display with incomplete text. This problem only occurred when a .col line in the unformatted report output ended with a carriage return (CR, hexadecimal 0d).

This has been corrected so that the Circulation Mailer report displays and downloads as expected. This has been corrected so that when the user requests to view or download the formatted report output of a completed Circulation Mailer report, the report results display or are downloaded correctly.

UNI-19281 Display User wizard was not consistently displaying checkouts & bills

Previously, the Display User wizard was not always displaying the list of checkouts on the Checkouts tab or the list of bills on the Bills tab for the selected user, even though the user had checkouts and/or unpaid bills.

This has been fixed so that user checkouts and bills will always display in their respective tabs.

UNI-21021 Hold slip was not printing the first print job

Previously, when a library staff member logged into the Java WorkFlows client with a fresh session, the first receipt print job from the Discharge/Checkin wizard (for a hold receipt) would not print. If the user discharged the same item a second time, the receipt would print.

This has been fixed so that the receipt will print at the first attempt.

UNI-21811 Item Search helper window was not closing

Previously, the Item Search helper would not close when the user clicked the close button (X) in the upper right corner of the window.

This has been fixed so that clicking the close button will close the Item Search helper window.

UNI-22904 User category information was not copied when marking a user's card as lost

Previously, when you used the User Lost Card wizard to replace a lost library card, the Category 2-5 information was lost from the original record when you assigned a new user ID.

This has been fixed so that the Category 2-5 data successfully copies over to the new user record, but is also retained in the original (lost card) user record.

UNI-22918 Blanket holds were not clearing after an item was checked out

Previously, checking out an item that was part of a blanket hold did not remove the hold on the remaining item(s) in the Java WorkFlows client. This error occurred when the item met the number of copies needed in the blanket hold.

This has been corrected so that the hold on the remaining item(s) when an item that is part of a blanket hold is checked out.


Circulation 31

UNI-23506 Hold Pickup Notices report were producing multiple mailing labels for the same patron

Previously, the Hold Pickup Notices (pickup) report was producing multiple mailing labels for the same patron when there was more than one item in the notice.

This report has been fixed so that it now will only produce one mailing label for the same patron.

UNI-23648 Users unable to search for a phrase longer than 35 characters in User Search helper

Previously, the User Search helper accepted up to 35 characters in the Search For field. Libraries found that this limit was not sufficient for some user searches (such as a keyword search on the patron's full email address). The User Search helper has been enhanced with the following character limit changes.

Keyword searches now permit up to 200 characters in the Search For field.

Browse user searches now permit up to 70 characters in the Search For field.

Browse user group searches now have a 20 character limit, which is the maximum length for a user group name.

UNI-23799 Cursor focus was lost in the User Search helper in the Display User wizard

In the Java WorkFlows client, the cursor focus was lost when doing a second search in the User Search helper within the Display User wizard.

This has been fixed so that cursor focus is not lost in the User Search helper.

UNI-24024 Users could not modify a hold for past suspension dates

Previously, when library staff tried to modify a hold with a suspension date and unsuspension date for a past date, an error message would display and no modification to the hold was possible.

This has been fixed so that users can modify a hold's suspension or unsuspension date with a past date without error.

UNI-24263 Hold status was not displaying for the first hold in blanket hold lists

Previously, when library staff used the Display User wizard, the blanket hold list on the Holds tab did not display the status of the first hold. This occurred only with blanket hold lists.

This has been corrected so that the status of the first hold will display.

UNI-25017 Billing error when “Bill User” button was disabled

Some libraries disable the “Bill User” button in the Billing a User wizard properties, so that only the Pay Now button is available. Previously, when the “Bill User” button had been disabled, there was a problem with the workflow when library staff tried to bill a user. In the Billing a User wizard, if a staff member typed in the user ID, selected the bill reason, typed in the bill amount, and then pressed ENTER before retrieving user information, the wizard would process the bill as “Billed” and not as “Paid.”

This has been fixed so that all bills will be processed as “Paid” when the “Bill User” button is disabled in the Billing a User wizard properties.



32 Release Notes

UNI-25293 Web Authentication ID field was not in pipe-delimited user record format

In a previous version of SirsiDynix Symphony, the Web Authentication ID (Web Auth ID) field was added to the flat ASCII user record format that is used with the Load Users report for batch loading records. Some sites still use the pipe-delimited user record format for batch loading records, and that format did not include the new Web Auth ID field.

This has been fixed so that the pipe-delimited user record format now includes Web Auth ID in the last field position (field 54).

UNI-25313 Hold expiration date would default to library policy if “NO DATE” was selected in calendar gadget

Previously, when library staff placed a hold on an item and selected “NO DATE” from the Expires field, the Expires field would be populated with the value “NEVER.” However, when staff viewed the same hold in the Display User Holds wizard, the expiration date instead showed the date set by the Library policy's Days for Holds to Expire attribute setting.

This has been corrected so that the Library policy attribute will not override the “NO DATE” expiration date.

UNI-25343 Preferred name was not recognized in sorting

Previously, when library staff did a search by name from the User Search helper (with the properties set to sort by name), the search results would sort using the user's first name, even if a preferred name was configured.

This has been fixed so that search results will sort according to preferred name.

UNI-25541 Cursor focus was lost in Change Item ID wizard

When library staff used the Change Item ID wizard, they were prompted three times to scan the original item ID (previously, they only needed to scan the item twice). The extra scan seemed to have been caused by a change in the cursor focus. This problem only occurred if the Change Item ID wizard property was set to “Perform Selected Action.”

This has been fixed so that the cursor focus stays and the original item only needs to be scanned twice.

UNI-25924 Extra transit message in Trap Holds wizard

Previously, the Trap Holds wizard was displaying an extra “Item in Transit” message when trapping a hold for an item. The second time, if library staff clicked the Release Item button, an error message would display.

This has been fixed so that the “Item in Transit” message window will only appear once.

UNI-25930 Suffix and Title fields were not searchable

After a site had moved the Name fields of their user records to the new name fields (Last, First, Middle, Preferred, etc.) that were introduced in SirsiDynix Symphony 3.3.0, the library staff could no longer search user records by the Suffix or Title fields. Previously, those fields had been searchable.

This has been corrected so that those fields are again searchable.



Circulation 33

UNI-26062 Place Holds wizard displayed Group ID and Category 1 info for user that currently had item checked out

This problem occurred when libraries set the User Information Global Configurations to display User Group ID field and User Category One field. When library staff used the Place Holds wizard to place a hold on an item that was currently checked out, the User Group ID and the User Category 1 fields displayed the information of the user to whom the item was currently checked out, instead of the user placing the hold.

This has been fixed so that these two fields will now display information for the user placing the hold.

UNI-26250 Hold Queue Reorder wizard would move e-Library holds up in the holds queue

When holds placed in the Java WorkFlows client were reordered using the Holds Queue Reorder wizard, any holds subsequently placed in e-Library appeared at the top of the queue. This occurred only when the recall status of the holds was standard recall.

This has been corrected so that new holds are added to the bottom of the queue, regardless of where the holds were placed.

UNI-26655 Problem moving the user ID to active/inactive when primary ID was modified

This problem occurred when the “Configure Checking Previous ID When User ID Is Not Found” Global Configuration option was set to “Check Active, Inactive, & previous id when user ID is not found.” The Modify User wizard and the Modify User helper were not working correctly when modifying a user ID. If the Modify User wizard or Modify User helper was used to modify the primary user ID, the original primary user ID was incorrectly placed on the inactive user ID list.

This has been fixed so that the Modify User wizard and Modify User helper will place the original primary user ID on the list of active user IDs when it is modified.

UNI-26769 Pay Bills helper was disabled in Discharge wizard when user had fines

Previously, when an item that was not overdue was checked in from a user who had existing fines or bills, library staff was not able to open the Pay Bills helper in the Discharge wizard. This occurred even when the Pay Bills helper was enabled in the Discharge wizard properties.

This has been corrected so that the Pay Bills helper will be available to library staff for users who have existing bills as well as for users who are returning overdue items.

UNI-26792 Paying Bills wizard and helper allowed a negative number in Payment field

When the Paying Bills wizard and the Pay Bills helper were used to accept bill payments from patrons, it was possible for library staff to enter a negative number in the Payment field. When this happened, the wizard and helper ignored the negative sign and incorrectly applied the number as a payment amount to the bill.

This has been fixed so that a negative number in the Payment field will cause an error message to display, and the negative number will not be applied to the bill.



34 Release Notes

UNI-26960 Hold wrapper was not printing correct date format

When the “Configure Display of Dates on Receipts” policy was set to “Display Month as Text on Receipts,” and Circulation wizards were configured to print hold wrappers, libraries using the European date format found that the format was not honored when they printed hold wrappers. For example, the date on the hold wrapper should have printed “20 December 2009,” but instead printed in the American date format “December 20, 2009.”

This has been corrected so that the date printed on hold wrappers will appear in the European format for libraries configured to do so.

UNI-27457 Floating items were not floating if attached to a suspended group range hold

Previously, an item with a floating item type was not moving (floating) correctly to the new library if the item was linked to a suspended group range hold. The item would go “internist” to the hold pickup library and the its owning library would not change.

This has been corrected so that floating items will behave as expected.

UNI-27502 Server was returning a full list of holds

Previously on the Java WorkFlows client, the server was returning the full list of holds for the item when displaying the circulation note if the note was configured to display at check in, check out, or renewal. For systems that contained a large amount of hold information, this was causing performance problems.

This has been fixed so that the server will not return the full list of holds when it displays item circulation information, which will improve system performance.

UNI-27504 Non-reserve items flagged as reserve items at check out

If a reserve item and a non-reserve item were checked out to the same user, the non-reserve item was getting flagged as a reserve item. This problem artificially inflated sites' reserve circulation statistics.

This has been fixed so that non-reserve items will not be flagged as reserve items in the check out transaction.

UNI-27538 Renew user wizard would freeze This problem occurred with the “Extend User's Library Privilege” property in the Renew User wizard was disabled. If library staff opened the Renew User wizard and entered (or scanned) a user ID for a user with an expired privilege, the Java WorkFlows client was unresponsive. The staff member had to use the Windows Task Manager to end the WorkFlows session.

This has been fixed so that when a staff member enters a user ID for a user with an expired privilege, an error message appears stating that the user record has expired, and the wizard will reset to receive the next user ID.



Circulation 35

UNI-27753 Users unable to pay bills for “Bill Maintenance” library

Previously, after upgrading to SirsiDynix Symphony 3.3.1, libraries no longer had access to pay bills that belong to the library listed in the “Bill Maintenance” attribute for the station library.

This has been fixed so that the Paying Bills wizard will now allow bills to display even if the user library is not among the Bill Maintenance libraries for a login library. Users will be able to pay any of their bills as long as the user library is one of the Circulation Maintenance libraries.

Note: The User Lookup helper for the Paying Bills wizard has also been changed to limit search by Circulation Maintenance Libraries, instead of Bill Maintenance Libraries.

UNI-28477 Item trapped for a suspended hold

Previously, if a hold was suspended after the List Onshelf Items with Holds report had selected an item to fill the hold, users could still trap the selected item to fill the suspended hold.

This has been fixed so that users can never trap a suspended hold in any wizard.

UNI-28844 Item appeared to be put intransit when hold was removed

When library staff removed an available hold in the Java WorkFlows client, the client was sending a message that the item was placed in transit, though the item had not been placed in transit. This error only occurred when the Remove User Holds wizard properties were set to “Remove From Holds Shelf.” This automatic transit problem occurred even when the “Make next hold available” property was disabled.

This has been fixed so that there will only be an “in transit” message if the “Make next hold available” property is enabled and there is a hold for the item in another library.

UNI-29309 No sound alert in barcode validation

Previously, the sound alert that plays when an item is not found would not play when barcode validation failed.

This has been fixed so that library staff can configure an alert to sound when an item is not found, and when barcode validation fails. (This configuration is only available if barcode validation is turned on.)

UNI-29655 Releasing an in-transit item with the Trap Holds wizard displayed item as on “HOLD” at pickup library

Previously, if library staff tried to use the Trap Holds wizard to release an item that was in transit to fill a hold, the software would prematurely indicate that the item was in the “HOLDS” location and that the item on hold was available for pickup. The patron could then prematurely receive notification that the item was available at the pickup library, when in fact it was not.

This has been fixed so that when an item is released from transit with the Trap Holds wizard, the item is released from that particular hold as expected.



36 Release Notes

UNI-29964 Offline client did not load transactions after PC login changed

Library staff discovered that the Offline WorkFlows client did not load transactions after they changed the user login profile for their PC. The Offline client was trying to write its log in a directory in which the new user profile did not have permission to write. Instead of sending an error message, the Offline client acted as if the transaction had loaded correctly.

This has been corrected so that the Offline client sends an error message if it cannot access the transaction log. In the message it names the inaccessible directory path.

UNI-30298 Interval circ counts did not display correctly for titles

Library staff can use the Item Search and Display wizard to show the circulation counts for titles, including total checkouts, total renewals, ongoing checkouts and ongoing renewals. Some libraries reported that this wizard would periodically show the wrong counts for an item. The problem arose because the wizard used the wrong field to identify which counts to display.

This has been fixed so that the Item Search and Display wizard displays the correct counts for each title in the database.

UNI-30572 Random database errors on SQL system

When MSSQL customers used the Pay Bills wizard to pay bills for new users they occasionally received database error messages, inhibiting the transaction.

This has been corrected so that customers will no longer receive these random database errors when carrying out payment transactions.

UNI-30764 No Overdue Notice report was pulling checkouts that did not fall within the selected dates

Some users encountered problems with selecting checkout records when running the No Overdue Notice report and specifying those checkouts that fall within a given date range. Rather than select the checkouts that fell within the specified date range, the displayed checkouts fell outside of the specified date range given for the report.

This has been corrected so that the report is able to handle given date ranges as expected.

UNI-31041 “Date Charged” column would not sort correctly

Previously, users found record sorting problems when displaying an item in the Item search and Display wizard under the Call Number/Item and Charge History tabs. These problems were related to the Date charged column only.

These problems have been fixed so that now the records displayed and sorted by the date charged are displayed and sorted correctly.




Collection ExchangeTracking No. Summary Description

UNI-25472 Problem with Exchange Items wizard

Previously, libraries were unable to exchange certain items using the Exchange Items wizard.

This has been fixed so that library staff can activate exchanges when there are items currently in exchange with types/categories that do not match the library's profile.

UNI-25942 Collection Exchange system did not recognize new items

Previously, collection exchange items were not getting recognized as NEW, even though library staff had marked the bibliographic record and item records with a “New Category Date.”

This has been fixed so that when the “New Category Date” value is stored in the exchange catalog record, the date is recognized.

UNI-26876 Collection Exchange (CE) group of reports did not process data from CE catalog records

Previously, some items could not be processed in various Collection Exchange reports after they were exchanged and confirmed for shipping. The Collection Exchange group of reports incorrectly excluded relevant information that was stored in the collection exchange catalog record associated with these items.

The following reports were affected:

• Count - Collection Status (Xcollstatus)

• Count - Items in Exchange (Xitemlibcount)

• List - History per Item (Xitemhistory)

• List - Incomplete Sets Notices (Xlistsets)

• Maintenance - Modify Exchange Item Records (Xmodifyitem).

This has been fixed so that the CE group of reports processes this information as well as any CE information stored in the item record itself.

UNI-27966 Confirming shipping on large numbers of items caused the system to time out

The WorkFlows client could cease responding when library staff confirmed shipping on large numbers of items, typically 1500 or more. As a result, the items being confirmed could be assigned to the wrong library.

This has been corrected so that the system can confirm shipping on large numbers of items without timing out.

UNI-27977 Item scoping rules prevented exchanged item's library from updating

Previously, for collection exchange to work properly, the headquarters library had to have item scoping rules that allowed it to modify branch libraries' items. Otherwise, the library field in the item record would not update when the item was exchanged.

This has been fixed so that item scoping rules will not interfere with updating the item library values for exchanged items.


38 Release Notes

UNI-28301 Results from default selections in the Collection Exchange Counters report were too limited

The Exchange Counters (Xlibcounters) report only showed the exchanges for a single library when the report ran with no selections on the Exchange Library tab.

This has been corrected so that the Xlibcounters report shows the exchanges for all libraries if no selection is made on the Exchange Library tab.

UNI-28857 Items could not be added to existing sets

Previously, if library staff tried to use the Manage Sets wizard to add a collection exchange item to an existing set, they would get an error message.

This has been fixed so that library staff can add a collection exchange item to a set using the Manage Sets wizard without any problem.

UNI-28997 Exchange quota thresholds ignored

Previously, administrators could exchange an item when the exchange library had already reached its quota threshold for the item type or category without the system requiring an override. This problem occurred with the following configuration:

• The “Apply profile quotas for Modify Destination” property selected in the Exchange Item wizard

• The profile set up to exchange all core items

• The “Suggest per exchange quantity when below target” Global Configuration option enabled

This has been fixed so that administrators will be alerted if they attempt to exchange an item of a specific type or category that exceeded the exchange library's quota threshold for that type or category. If administrators want to make the exchange anyway, they will be prompted for an override.

UNI-29502 Status qualification ignored in xlibcounters report

Previously, when an administrator ran the collection exchange xlibcounters report and qualified the report by library status, the software ignored the status qualification and ran the report for “Active” libraries even though only “Inactive” status had been selected.

This has been fixed so that the xlibcounters report will, by default, update only “Inactive” status libraries, unless administrators also select the exchange library status to “Active,” in which case, both active and inactive libraries will be updated.

UNI-29534 Exchange types and categories duplicated on Oracle databases

Previously, the same exchange types and categories would show up multiple times for the same library in the My Exchange State wizard. This problem only appeared on Oracle databases.

This has been fixed so that the same exchange types and categories will no longer be needlessly duplicated.




UNI-29662 Title Information disappeared if library exchange destination was modified

Previously when administrators used the Exchange Items wizard to manually modify a library exchange destination, the item's Title Information would no longer appear on the screen.

This has been fixed so that Title Information is preserved when administrators manually modify a library exchange destination.



40 Release Notes

ConfigurationTracking No. Summary Description

UNI-23924 Users could not enter decimal in Tax policy on French OS

Previously, library staff could not enter a decimal (for example, 7.5%) in the Percentage field of the Acquisitions Tax policy in the Java WorkFlows client on a French OS.

This has been fixed so that libraries can now enter decimals in the Percentage fields of the Acquisitions Tax policy on a French system. This functionality was never broken for an English OS.

UNI-25359 Users could not add valid indicator 2 values to certain tags

Users were unable to update their catalog formats with new indicator values for several tags. After users updated these tags with the new Indicator 2 values and clicked Save, the Java WorkFlows client would become unresponsive. The following tags were affected.

• 083

• 085

• 542

• 653

• 751

• 882

This has been fixed so that changes to these tags can be saved with no problem.

UNI-25606 Users were unable to add new entries to UNIMARC catalog formats

Previously, users were not able to add new entries to the UNIMARC catalog formats. For example, when a user selected a new entry ID, U091, for the CNSERIAL format, an error message would appear stating that the entry already existed.

This has been fixed so that now when a UNIMARC entry is created, the Java WorkFlows client will ignore the initial U of the UNIMARC tag and the remaining digits will be used to create the internal entry number. If that number already exists, the next available internal number will be assigned.

UNI-27511 Library Calendar wizard allowed users to enter invalid date information

Users could manually enter Closed Dates in the Library Calendar wizard closed date field in excess of the 64 closed-date limit. The next time the workstation server was halted (in order to pick up policy changes) the server could not be restarted, and library staff could not access the WorkFlows Java client.

This has been corrected so that the user cannot manually enter more closed dates than the 64 date limit.


Configuration 41

UNI-30817 “Update Wizard Accesslist for Previous Client” option

An option within the User Access Wizard labeled, “Update Wizard Accesslist for Previous Client” has been causing access problems for users seeking to terminate use of the WorkFlows C-client and solely use the Java WorkFlows client. This was primarily a problem for libraries which had both the Java client and the C-client installed. When enabled, the option would grant C-client access to users, counteracting the library's efforts to migrate away from that client.

To avoid these problems, the “Update Wizard Accesslist for Previous Client” option has been permanently removed in Symphony 3.4. Users will no longer have the option to access the C-client via this option.



42 Release Notes

EDI /X12

Miscellaneous


UNI-24942 Book X12 acknowledgements with PO Update Report returned error: “User ID must contain at least two digits”

In the WorkFlows Java client, the Book X12 ACK with PO Update (bookx12POAack) report returned the following error:

User ID must contain at least two digits

This prevented the EDI files from being processed.

The error was caused by the report assuming that the Library policy user ID was the same as the Library policy name.

This has been corrected. The Library policy user ID is now retrieved from the user ID field of the Library policy.

UNI-25662 Improved Report Log Error Message for Incorrectly Formatted REC_TRANS Entry in Vendor EDI Address

Previously, if a user had incorrectly formatted the POA REC_TRANS entry of an vendor's EDI address, the X12 reports (Book X12 Orders, Serial X12 Orders, and more) would display the following error message in the report log:

**Error in field size

This message did not provide enough information, and the user was not certain whether the issue was with the incoming X12 file or the EDI address.

Now, if a REC_TRANS entry is incorrectly formatted in the vendor's EDI address, the report log will display a message similar to the following:

**Error in vendor EDI Address REC_TRANS entry -- 855;bookpoaX12.map -- INGRAM/ROCKEFELLR/2009

This message now lists the errant entry text and the affected vendor EDI address.


UNI-25358 Renew wizards did not check for overlapping Booking due dates before renewal

Previously, library staff could not check for overlapping booking due dates/times and could, potentially, allow for renewing a user's booking beyond the start date/time of the next booking for a different uservia the Renew Item and Renew User wizards.

This has been corrected so that the Renew Item and Renew User wizards check for overlapping booking due dates before renewing booked items, and will truncate the due date if any future bookings are found for a different user.

UNI-26103 Add, Delete, Update User report non-responsive if a dynamic indexing lock file existed

Previously, if an empty user dynamic indexing lock file was present on the Symphony system, the Add, Delete, Update User (Adusertext) report would become unresponsive and never finish.

This has been corrected to more properly handle dynamic indexing lock files and to ignore the presence of an empty lock file.


Miscellaneous 43

UNI-26214 Print Screen in ISAD displayed raw HTML

Previously, when library staff would use the “Print Screen” option in the Item Search and Display Wizard, some of the tabs displayed the raw HTML coding.

This has been corrected so that the tabs display with proper formatting.

UNI-26255 Custom toolbars did not work for users with administrator access

After Symphony 3.3, users with administrator access could not use any custom toolbars that were saved on the workstation. The custom toolbar would display as a navigation tab, but clicking on the tab did not change the user's view.

This has been fixed so that administrators can use custom toolbars.

UNI-27442 Changing the Library of an item on hold caused processing error

If staff changed the Library on an item with an inactive hold, sometimes the system created a looping process. This happened when the new library was not in the hold range for the Library or Library group where the hold was first set up.

This has been fixed, so that changing the Library will not cause a looping process.



44 Release Notes

OPACTracking No. Summary Description

UNI-3017 iBistro Recommended Reading and best Seller Lists displayed policy name instead of policy description

Previously, users saw that the recommended reading and best seller lists displayed the location policy name.

This has been corrected to now display the location policy descriptions instead of the policy names.

UNI-17563 Placing holds on a title with multiple volumes would fail despite displaying a success message

Previously, when users would place holds on a title with multiple volumes, the holds would fail, but the system would display a success message.

This has been fixed so that the message is consistent with the actual result of the hold request.

UNI-20524 “HERE” library selection was lost when gateway policy modified

In e-Library Kids' Library users have an option to set the default library to “HERE,” which means that the e-Library's login library will be used when using the Kids' Library search options. If any settings were changed in the Gateway Database for Kids' Library, however, the “HERE” library was lost as an option.

This has been corrected to retain the “HERE” option despite any settings changes staff members choose to make.

UNI-22112 e-Library Item details configuration ITEMINFO_OPTION2 was not working in revD

ITEMINFO_OPTION2 allows libraries to customize what appears on the item details page besides the default information for publisher, publication date, and pages. In e-Library revD, only field labels were displaying on the item details page instead of both the labels and the data.

This has been fixed so that the item details page now displays the labels and data in the appropriate locations when ITEMINFO_OPTION2 is used to customize the page.

UNI-22826 Blank box appeared when Library Info group suppressed

When library staff used the IBISTRO_LIBINFO_CONFIG environment variable to suppress the display of the LIB_INFO gateway group elements in e-Library, some pages, such as My Account and Knowledge Portal, displayed an empty box where the elements would have appeared.

This has been corrected so that the system now suppresses everything correctly, without displaying the empty placeholder.

UNI-25469 Loss of OPAC session resulted in Miscib/LIBLOGO instead of IMG_OTHER/LIBLOGO

When an OPAC session timed out (or any other occasion when there was not a session), the LIBLOGO file in the IMG_OTHER path was not being used, but instead defaulted to the /English/Other/Miscib/ path.

The path being used was not coded as a variable. This has been changed so that the system uses the path in IMG_OTHER.


OPAC 45

UNI-26189 Copy-level shadow indexing corrects misleading “Unavailable for display” messages for shadowed titles

When a user performed a library-specific search for a title in e-Library, if the only copies at that library were shadowed, the search hitlist still displayed shadowed entries for that title. Also, an “Unavailable for display” message showed for this entry, which was confusing for the user.

To remedy this confusing display in the e-Library, administrators would change a variable in the e-Library environment files (.env) to suppress the display of shadowed titles/copies. While this option would present a better hitlist, a shadowed copy could still appear in the search hitlist.

This has been corrected so that users will not see shadowed titles in hitlist results. Copy-level shadow indexing was added to correct this errant display of shadowed copies. This indexing marks items as visible only or shadow only. With this change, when a user searches titles specific to a library or library group, if the e-Library's search shadow flag is set to NO, then the search hitlist will return hits that contain only visible copies for that library or library group. If the e-Library's search shadow flag is set to YES, then the search hitlist will return hits that contain shadow copies for that library or library group. If the e-Library's search shadow flag is set to BOTH, then the library's (or library group's) visible and shadow copies will display in the hitlist.

UNI-27078 Users were unable to place on-order hold on single library system

Previously in e-Library, when a staff member attempted to place an on-order hold on a system with a single library, they would receive a message saying, “item information missing” and the attempt to place the hold would be unsuccessful.

This has been corrected so that library staff will be able to successfully place on-order holds of this type as expected.!

UNI-27708 Emailing failed in Arabic e-Library (RevD) and iLink (RevC)

Previously, when users would email Kept records in the Arabic interface, they encountered an “Undetermined response error” in both iLink (RevC) and e-Library (RevD).

This has been fixed by adding NORTL to hidden fields so that email works when the language is Arabic.

UNI-27740 “Ready for pickup” not formatted as a header

The “Ready for pickup” heading in the Review My Account area did not display as a heading consistent with the other headings.

This has been fixed so that “Ready for pickup” displays as a heading.

UNI-27743 Extra “Results not sorted” message displayed

Previously, users would note that the “Results not sorted” message displayed at both the top of the results page and on the right side under the “Try these too” group.

This has been fixed so that the message only displays at the top of the results page.



46 Release Notes

UNI-27744 “Items eligible for renewal” message display problem

Previously, users would find that the “Items available for renewal” text displayed below the number instead of on the same line.

This has been fixed so that the number and the text appear together on the same line.

UNI-27784 Web Admin drop-downs were not populating (Windows-specific)

In the e-Library Admin Configuration, users found that some drop-down lists were not showing the selection options. This was due to a Microsoft Windows issue with the printing of trailing spaces.

This has been corrected so that the string is now assembled and sent as one item so that the spaces are embedded. The drop-downs now display the proper options.

UNI-27812 Syndetics Deluxe content was not available at 3.3.1

In e-Library, subscribers to deluxe Syndetics content were no longer receiving it at SirsiDynix Symphony version 3.3.1. This was a result of a change in the way the content was delivered.

This has been corrected so that subscribers to the deluxe content will now be able to see it as an “All content” link under the Item Information tab in e-Library.

UNI-27869 Extra space after heading on Holds tab in Review My Account

Library staff discovered that the Outstanding Holds heading in the Review My Account area showed extra space before the table when viewed in Internet Explorer 7. This was a browser-specific issue.

The CSS has been updated so that the page displays similarly on all browsers.

UNI-27890 Error in e-Library 3.3.1 My Account page when holds were available

On the My Account page, when a patron had an available hold, the tab links did not work and the Holds link resulted in an error page.

This has been fixed so that the My Account page and all the links function as expected.

UNI-28052 Special characters in the URL “path_info” section caused hyperlinks to fail

Previously, users found that on Windows Server 2003 and 2008, hyperlinks that had special characters, such as spaces, punctuation marks, or diacritic characters (e.g., Ä, ç, etc.), occasionally returned an error message rather than showing the intended page.

The problem occurred when these characters ended up in the path_info section of the URL instead of the query_string section.

This error has been corrected so that all links pass their information into the query_string section of the URL instead of the path_info section.



OPAC 47

UNI-28371 Copyright before “DOCTYPE” tag would break Internet Explorer

Users found on several e-Library pages that the copyright statement was placed before the DOCTYPE tag. Users viewing e-Library sites with Internet Explorer versions 7 or 8 found that the default style sheet was used instead of a customized style sheet (CSS).

This has been corrected and now the copyright statement has been moved to the appropriate location in the page files.

UNI-29293 Syndetics content was only available from ISBN, not UPC or OCLC

Previously, e-Library 3.3.1 users found that enriched content only displayed for items that had an ISBN.

This has been fixed so that e-Library requests enriched content using the ISBN, UPC, or OCLC information for each item.

UNI-29426 Invalid username or blank password could create an e-Library session

E-Library uses LDAP to log patrons in based on a unique username and password. In the past, due to a default LDAP setting, some patrons were able to log in to e-Library with an invalid username or a blank password.

If the username or password entered were not found in the library's LDAP directory (such as the student directory of a university library), by default the system attempted to connect with a username or password of NULL instead.

Then, if e-Library found a webauth ID in SirsiDynix Symphony that matched with the username or password of NULL, it created an individual session for the patron.

This has been fixed. E-Library will not create an individual session if a user enters a username or password are not found or left blank.

UNI-29567 Alignment on Item Information tab in IE7

The Item Details page for e-Library RevD did not align all information appropriately.

This has been fixed so that missing or blank information does not affect the layout of the page.

UNI-29578 Problem using e-Library and Syndetics enriched content through an SSL connection

Previously, when using an SSL connection to Syndetics enriched content in e-Library, not all the anticipated content was returned.

This has been fixed so that the Syndetics content displays as expected as long as the Apache server is set up to handle SSL requests. See the Configuring e-Library for enriched content topic in the e-Library Administrator help.

UNI-29616 Enriched content slowed performance due to increased file requests

Some high-traffic sites noticed a significant loss of performance with the addition of enriched content. Investigation determined that the total number of requested images and other page elements had risen sharply. The requested files were small, but the high volume of requests slowed the system perceptibly.

This has been fixed. Many of the requested files could be combined into a much smaller number of slightly larger files. This reduces the number of requests for page elements and corrects the performance slowdown.



48 Release Notes

UNI-30330 “Bookmark this page” was not working in Google Chrome

Because of web browser security constraints in Google Chrome and some versions of Apple Safari, e-Library 3.4 users who click the Bookmark This Page link get an error message. This is a function of the web browser's own internal security and is outside the control of SirsiDynix. As a workaround, the error message instructs users to use the web browser's own bookmarking feature and to edit the URL to remove session information. Alternately, users could use a different web browser.

UNI-30344 Enriched content was disabled for k12.env

In SirsiDynix Symphony 3.3.1, the k12.env file had not been updated with the new enriched content variables. This resulted in no content appearing for sites using the K12 environment, when enriched content was configured.

This has been fixed so that k12.env has all the necessary enriched content variables.

UNI-30369 Delivery and shipping policies were not set when booking an item in e-Library

When library staff would create a booking using a user profile that included a shipping schedule policy, e-Library would not set the shipping information.

This has been fixed so that the shipping information is set at this stage.

UNI-30511 NoveList URLs updated e-Library users found that the Novelist URL, referenced in the NOVELIST_BASE_URL variable, pointed to an old server.

This has been fixed so that the URL points to the correct Novelist server.

UNI-30684 3.4 upgrade may cause former RevD customers to switch to RevC

When a library upgraded to e-Library 3.3.1, if there was no PAGES_SET variable in the system.env file, the variable was added and set to RevC.

For e-Library 3.4, this functionality has been removed because the default page set is now RevD instead of RevC. Therefore, the system does not add or change the PAGES_SET variable in upgrades to version 3.4. If there is a PAGES_SET variable set in system.env, that value stays the same. If there is not a PAGES_SET variable in system.env, the system uses the value from the specific environment file (such as ibistro.env), which would be the default of RevD.

UNI-30729 Syndetics Widgets did not allow use of custom stylesheets

Previously, the Syndetics widgets implementation in e-Library did not allow users to easily link to a custom stylesheet or to change the URL.

Two new environment variables have been added to the widget implementation to make it easier to configure and to customize: SYNDETICS_WIDGET_BASE_URL and SYNDETICS_WIDGET_CSS_URL.

UNI-31066 “Account Summary Tab” label was not translated

In e-Library, the “Account Summary Tab” label was not showing the translated versions of the label. This was caused by the tab label being coded into the page rather than as a label.

This has been fixed so that the label displays as expected for translated versions of e-Library.



OPAC 49

UNI-31125 iPhone accommodation would break Android and other smartphone devices

A change to e-Library for iPhone devices caused a menu to disappear for Android and other smartphone devices.

This has been fixed so that the menu displays for all supported mobile devices.



50 Release Notes

Performance

Reports


UNI-22551 Performance problem with loading user records

Previously in SirsiDynix Symphony, when library staff loaded a large number of user records, the process would not complete at the time of the scheduled halt and run, which was causing errors in the user load.

This has been corrected so that the process will complete by the time of the scheduled halt and run.

UNI-30038 Windows 2008 memory allocation error

Sites running Symphony 3.3.1 on Windows Server encountered problems with CPU usage and memory allocation. When the memory was exhausted, staff on the WorkFlows client and other clients could not log into Symphony.

To resolve these problems, new mserver, websession, webstarter, sockserver, sipstarter, sipserver and sipsession files have been created for Symphony 3.4.

Now these sites will not encounter these CPU usage and memory allocation problems.

UNI-30039 Multiple dynamic indexing programs running in Windows caused resource exhaustion

The tasklist command was taking too long to return the process list. This was causing problems with dynamic indexing which resulted in an overuse of client system resources. For customers using Windows Server 2008, the tasklist command has been modified to use the Perl kill command. This change eliminated the problems.


UNI-21182 “Run Now” option in template reports would not email notices automatically

Previously in the Java WorkFlows client, if users selected the Automatically Send Email Notices property in the Report Session Settings and the “Run Now” option for a Template report, notices could be sent automatically. This was not a desired result. In the WorkFlows C client, notices were not sent automatically from the Run Now option in Template reports.

This has been corrected so that now in the WorkFlows Java client, if a user selects the “Run Now” option from a Template report, email notices will not be automatically sent, even if the user had selected Automatically Send Email Notices in the Report Session Settings.

The following options are set from Report Session Settings when using the “Run Now” button:

• Notify owner when report is finished

• Include log (when viewing, printing, etc. finished reports)

• Include results (when viewing printing, etc. finished reports)

• The setting of the Recipients option (all, only those with email addresses, or only those without email addresses).


Reports 51

UNI-21187 Zero-byte files in /Unicorn/Edi/Incoming Directory

Previously, the EDI File Retrieval Via FTP (Ediretrieveftp) report was not creating unique file names. The result was a zero-byte file for every *.x12 file that was retrieved to the Edi/Incoming directory. (For example, the EDI file “ftp_hyaid4.x12” would import, and in the Incoming directory, there would also be a zero-byte file named “ftp_hyaid4.”)

This has been fixed so that the extraneous zero-byte files are not created and no longer appear in the /Unicorn/Edi/Incoming directory after running the Ediretrieveftp report.

UNI-22914 Library address not included pipe delimited file

In the Java WorkFlows client, when running the Generalized Bill Notices (bill) report, if users selected the library from the “Select From” Library selection box, the library address did not display when generating pipe delimited output.

This has been corrected so that the address will display.

UNI-23503 Regularly scheduled reports could run without selections and incorrectly modify too many user records

In certain circumstances, reports that were scheduled to run on a regular basis could run without selections and, as a result, incorrectly modify too many records. For example, an Edit User Characteristics (Edituser) report that was scheduled to run nightly could incorrectly modify a large number of user records because no selections were made. It was determined that the report was not able to read its corresponding .set file (the file that stores the report selections), and this would cause the report to run without selections. Now, if a report cannot read the .set file, the report will stop running and write an error message to the report log.

UNI-24161 No Overdue Notice report not sending notices for overdue checkouts to notice master

Previously, the New Overdue Notices (Noverdue) report was not sending notices for overdue checkouts to the notice master for a user group. If a user had charges outside the group and inside the group, the user (not the notice master) received the notices for all of his or her charges. This has been corrected.

UNI-25214 Load Bibs with Order Info report incorrectly created call numbers for copies with auto-generated call numbers

In specific cases when the Load Bibs with Order Info (Biborderload) report was configured to create copies with a SirsiDynix-generated call number, the subfield |z (analytics) could be incorrectly added to the generated call numbers.

This has been fixed so that the subfield |z will not be added to the SirsiDynix-generated call numbers created by the Biborderload report.

UNI-25663 Load Bibliographic Records report was not updating XX call numbers as expected

Previously, when users ran the Load Bibliographic Records (Bibload) report with the “Update AUTO-assigned call numbers” option selected, the report was not updating the auto-generated (XX) call numbers, and it would instead create another call number.

This has been fixed so that the Bibload report will now update the XX call numbers when that option is selected.



52 Release Notes

UNI-26073 Refactor User Name report modified

The Refactor User Name (Refactoruname) report has been modified. In the Last, First user name format, the second word in the First name field will now be placed in the Middle name field, unless a middle initial is found. If a middle initial is found, it will go into the Middle name field in the user record.

Additionally, the original name entry is no longer saved by default to the “NOTE” User Extended Information field, regardless of the user name format. Instead, the original name entry is not saved. However, the capability still exists to allow saving the original name entry to a selected User Extended Information field, if desired.

The Refactor User Name report only needs to be run at the time of upgrading to SirsiDynix Symphony 3.3 or later.

UNI-26213 Overlay on indexed fields would not happen as expected

This problem would occur for any report used to load bibliographic records to the catalog. If when scheduling one of these reports a library staff member selected the “Match on Indexed MARC Tag” option and then selected some field (ISBN type, for example) as the first field for matching with other subsequent fields for matching, when the report could not find a match for the first field, it would also not match for the subsequent fields in the list. This resulted in the report creating new records, instead of overlaying existing records as expected.

This has been corrected so that running one of these reports with the “Match on Indexed MARC Tag” option selected will overlay existing records by matching on an indexed MARC tag, instead of creating new records. This correction was made to the following reports.

• Load Bibliographic Records (Bibload)

• Load Bibs for Selection (Selectbib)

• Load Bibs with Order Info (Biborderload)

• Load Bibs with Selections and Decisions (Selectbibemb)

• Load OCLC MARC w/049s Report (Loadoclc)

• Reload Bibliographic Records (Bibreload)

• Review Bibliographic Records (Bibreview)



Reports 53

UNI-26223 List Invoices report included results for funds for multiple libraries

Previously, the List Invoices (Invoicelist) report's Fund Summary Totals option was listing fund totals for other libraries even though the user had selected only one library on the Invoice Selection tab. This also occurred in other reports that use the Print Invoice output options and allow output of Fund Summary Totals.

The following reports have been corrected.

• Book X12 Invoices (Bookinvoicex12)

• Invoice Lines by Check Number (Checknumber)

• List Invoices, Lines (Invlinelist)

• List Invoices (Invoicelist)

• List Vendor Invoices (Listvendinv)

• Remove Partial Invoices (Rempartinvoice)

• Serials X12 Invoices (Serinvoicex12)

• Update Invoice Exchange Rates (Updateinvexch)

UNI-26228 Vendor Acquisition Claim report produced odd spacing on Oracle systems

Previously, the Vendor Acquisition Claim (Acqclaim) report had odd spacing in the report output between the Ordered, Date, and Amount fields. This only happened on Oracle systems.

This report has been fixed so that the output is formatted as expected.

UNI-26350 Link Order Holds report corrected

After a site upgraded to SirsiDynix Symphony version 3.3, the Link Order Holds report was taking hours to run, when it should only take a few minutes. This problem only occurred on Oracle systems.

This has been fixed so that the Link Order Holds reports now runs as expected.

UNI-26626 Change Invalid Hdgs by Authority and Change Invalid Headings by Bib reports didn't print correct UNIMARC tags

Previously in the WorkFlows Java client, users found that the Change Invalid Hdgs by Authority (fliphdngbyauth) and Change Invalid Headings by Bib (fliphdngbycat) reports were not printing the correct UNIMARC tags in the report output.

This has been corrected.

UNI-27557 Selitem change in 3.3.1 caused problems in custom reports

After users would upgrade to SirsiDynix Symphony 3.3.1, some custom reports would fail at selitem or seluser with the following message:

**Must have option(s) -E for selitem

This has been corrected.



54 Release Notes

UNI-27585 Load Users Report would erase extended information fields in current user records

When a site upgraded to Version 3.3.1, library staff noticed that after running the Load Users (Userload) report to update user records, some extended information fields in the existing user records were erased. This occurred when the incoming user record contained less or different extended information fields from the existing record. The report was replacing the extended information fields instead of updating them. This could also occur when updating user address fields.

This has been corrected so that Load Users report runs as expected.

UNI-28234 Load User report failed When library staff would run the Load User report to upload user records on the Java WorkFlows client, the uploaded records would not appear on the finished list. This would occur because some user records were written in a non-standard record format, placing white space before and after the equal sign (e.g. “FORM = LDUSER”). When the Loadflatuser partial file would encounter one of these records it would skip the record and process the next without logging the error.

The get_ld_flat.c file has been modified to force Loadflatuser to log error messages when it encounters records created in this non-standard record format.

Now when Loadflatuser encounters a record written in this non-standard format, it skips the record, processes the next, and enters the error message in the userload.err file.

For more information on the proper record format for use in the Load User report, see the Java WorkFlows help topic User Record Format for Loading User Information With the Load Users Report.

UNI-28475 Transaction Statistics report now delivered with Exclude Multi-circ Transactions enabled

Users will find that the Exclude Multi-circ Transactions? option on the Transaction Statistics Selection tab of the Transaction Statistics (Transtat) report is now delivered enabled (the check box is selected). The report, as delivered, will not include multi-circ transactions in the report output (since most sites do not use this option).

UNI-29314 Book X12 Acknowledgements report user ID error message

Previously, libraries were encountering an error message when running the Book X12 Acknowledgements (Bookx12POA) report using a vendor with multiple fiscal cycles. This was prohibiting the libraries from running the report for those kinds of vendors.

This has been corrected so that libraries can now run this report using vendors with multiple fiscal cycles.



Reports 55

UNI-29364 Correct language footer not used in notice reports

When a user selected a non-English language setting and chose to print closing text on a notice, the closing text would print in English rather than the user's selected language.

This problem stemmed from the search function that extracted files to be printed. The search was not performed based on the user's language settings.

This has been fixed so that now a user can print these documents and the closing text will appear according to the user's language settings.

UNI-30040 Windows: “auto_haltrun halt” would leave some symphony processes running

On Symphony systems using Windows Server 2008, the taskkill command contained an invalid syntax that would prevent the auto_haltrun script from forcing running processes to exit. This would produce an error for users in the error log citing a problem with taskkill. This bug could result in orphaned SIP and websession programs after running auto_haltrun halt and, consequently, could cause some of the library's nightly reports to fail or freeze.

Users will find that new versions of the unicorn_process.pm and unicorn_services.pm modules have been created to fix these errors.

This bug has been corrected so that now the auto_haltrun script will run as intended without any errors caused by Windows's taskkill command.

UNI-30041 Windows: “killtask” was not recognized as internal or external command errors in nightly reports

Previously, users found that the halt order in the Windows auto_haltrun script had the halt order incorrect. This resulted in some processes, such as the websession and sip processes, remaining active even after the Unicorn services were halted. In addition, the auto_haltrun script and the various report scripts which halt the Unicorn services on Windows were updated to use the Windows taskkill program instead of the Symphony killtask program, since the latter is not supported by Windows 2008.

Both of these problems have been fixed for Symphony 3.4.



56 Release Notes

Request

Searching

Serials


UNI-26078 Users unable to select a title with no item in Create Request wizard

Previously in the WorkFlows Java client, if a user created a request using the Create Request wizard with a Request Type of REQUISITN, the user could not select a title/call number without an item.

This has been corrected so that users are now allowed to select a call number with no items when creating a request.


UNI-30044 Hanging and crashing BRS processes on Windows

Customers using Windows were having problems with the brsload processes. A brsload process would fail to complete during the update phase which would result in incorrectly indexed records and a backlog of brsload processes.

Now if a customer is running Windows Server 2008 they will not encounter problems concerning hanging brsload processes when running the audtext report.

UNI-30204 MSSQL problem with title browse

Previously, when a user on a Microsoft SQL system would search a title or subject in the Item Search and Display wizard with the Browse radio button selected, they would find that the browse hit list would loop. This caused users to unexpectedly return to the beginning of the list when scrolling to the bottom, rather than finding that the hit list has a definitive end.

This has been corrected so that when users scroll to the bottom of the hit list they are not returned to the beginning, but stopped at the end of the list.


UNI-22282 Enter key did not work on “OK” button of Checkin Special Instruction screen

Previously in the WorkFlows Java client, when users attempted to check in serials that had special instructions, they found that the “OK” button on the Special Instructions screen did not work using Alt+O or Enter for a shortcut.

This has been corrected so that the “OK” button appears as expected.


Serials 57

UNI-22283 Special Issue duplicate Previously, when a user checked in a special serial issue in the Checkin Serial Control wizard, duplicate predictions for serial issues could be created with the same enumeration, and this could cause multiple receipts to be created.

For example, a user checked in a special serial issue with an enumeration of “SPECIAL ISSUE” and a chronology of “2007.” But, when the user checked in a second special issue with the same enumeration but a different chronology of “2008,” the following error message displayed.

“Enumeration SPECIAL ISSUE issue already received”

If the user then used the Modify Control wizard and changed the enumeration of the duplicate issue, the enumeration was also changed in the duplicated issue. When the user deleted the duplicated special issue, both special issues were deleted.

This has been corrected to not create duplicate predictions for serial issues with the same enumerations.

UNI-22337 Java WorkFlows could not be set to print a routing list on an A4 sheet

Previously, users could not configure the Java WorkFlows client to print a routing list on A4-size paper. Even though the user had set default printing properties in the Preference/Peripherals/Receipt Printer menu and had selected the Print Routing Lists For Received Issues property in the Check In wizard, the printer could not recognize A4-sized paper. The user had to manually instruct the printer to use the A4 paper each time.

The WorkFlows Java client's Check In wizard did not use printer settings from the Preference menu, and making selections in the Preference menu had no affect on Receipt Printer settings, including paper size.

This has been corrected by adding the Print Routing Lists to Default Printer/Attached Receipt Printer property to the WorkFlows Java client's Checkin wizard properties. For more information about this property, see the Java WorkFlows online help topic, “Check In Issues of a Serial Wizard Properties.”

UNI-26057 Layout of routing slips boxes was different in JWF from CWF

When using the WorkFlows Java client, library staff noticed that the first user field (typically the name) appeared on the line below the checkbox on the serials routing slips. This differed from the C-client where the name appeared on the same line as the checkbox. This has been corrected so the name prints on the same line as the checkbox.



58 Release Notes

SIP2Tracking No. Summary Description

UNI-25557 SIP and renewals that have holds on them

After sites using SIP2 servers upgraded from SirsiDynix Symphony 3.1 to 3.3, if a user tried to check out an item or renew material which had a hold that had not been trapped (unavailable holds), the items were allowed to be checked out or renewed even though the action should have been blocked due to the hold.

This has been corrected so that users will not be able to check out or renew items with holds.

UNI-27249 SIP would consume Oracle processes

When users on Oracle systems would receive an item information response message, the SIP server would hang if the counters in the response did not match the actual number of materials. For example, if the counter for LOST-ASSUM returns 1 but the material is no longer on the charge list the sip server would consume Oracle processes and hang the system. The SIP server now relies on the charge/hold counts that are calculated from the list provided.

This has been corrected and the client no longer hangs due to errors with counters on Oracle systems.

UNI-27586 SIP Renew All sometimes finished before evaluating all items for a given user

Previously, when library staff evaluated a user's charged items for renewal, the SIP2 server would finish before evaluating all items, skipping over the remaining items in the user's charge list. This occurred when the SIP2 server encountered an exception or “error” condition, such as an unseen renewal.

This has been corrected so that now the SIP2 server evaluates all items in the user's charge list, and correctly marks an item in the list as un-renewed when an exception is encountered.

UNI-28041 SIP brought down Oracle systems

Library staff running SirsiDynix Symphony on an Oracle system have noticed, on occasion, that the server has been overwhelmed by the number of SIP/Oracle processes initiated by vendor devices (ports) connecting to the server.

To remedy this, a new variable (MAX_SIP_CONNECTIONS) was added to the sip2.tbl file. This variable allows users to control the maximum number of SIP connections (sipserver/sipsession combination) that are allowed. This could be beneficial in preventing rogue or unintended “chatter” on one of the ports used by SIP from bringing down the SirsiDynix Symphony server.

For more information on this variable, see the guide “Setting up the SIP2 Server” under the topic, “SIP2 Table File.”


SIP2 59

UNI-28331 SIP would not work for “MISSING” items

After upgrading to Version 3.3, library staff noticed that the self checkout systems were not allowing a checkout if the item was assigned to the “MISSING” user. This occurred if the system was configured to clear charges. The SIP2 server was not handling the clear charge override for the “MISSING” user properly. This has been corrected so that library staff can make these transactions.

UNI-29139 SIP problem with Asian date formats

When users would set the SirsiDynix Symphony server to display dates in the Asian format (YYYYMMDD), the SIP2 server was not sending back a correct 18 (item information lookup) response to a 17 request for item information.

This has been fixed so that the 18 (item information lookup) response now returns due dates in the Asian date format.

UNI-29161 SIP 64 response would send “Claims Returned” materials with the overdue list

Previously, the SIP 64 message would return “Claims Returned” materials mixed in the list of overdue (and possibly still checked out) items.

This has been corrected so that “Claims Returned” items no longer appear as part of list of overdues or list of checkouts.

UNI-29213 SIP checkin response was not trapping holds when materials were in transit

When users checked in an INTRANSIT item to be transferred to fill a hold, extraneous hold information would be added to the screen message's AF field and would cause the library to retain the item instead of transferring it to where the hold was to be filled.

The HOLD sip request (15) option of the SIP config file was returning an incorrect message when an item was both labeled as INTRANSIT and had a hold on it.

This has been corrected so that now the HOLD sip request (15) withholds this extraneous information in the screen message's AF field. By doing so, the system will now allow items that are labeled INTRANSIT and on hold to be transferred to the appropriate destination libraries rather than retaining them in the checkin library.

UNI-29214 SIP checkin alert was not always set correctly

When library staff checked in an in transit or in branch item using a third-party, self-check system, Symphony, through the SIP server, would respond to the item checkin with a failed checkin flag.

These self-check systems were unable to provide the proper response when they detected a failed checkin flag from the SIP server.

This has been corrected by adding a new setting to the sip2.cfg file called CHECKIN_FAILS_OPTION. For more information on this setting, please see the Setting up the SIP2 Server guide under the topic, “SIP2 Table File.”



60 Release Notes

UNI-29653 SIP checkin “please handle manually” problems

Library staff using third-party checkin devices with SIP sometimes had problems when checking in materials with holds. SIP would produce an error message in the SIP AF segment telling the user to “Please handle manually.”

This has been corrected so that users will no longer encounter this error message.



StaffWeb 61

StaffWebTracking No. Summary Description

UNI-25266 User Previous ID were editable Previously, in the StaffWeb client, the Previous ID and Previous ID2 fields in the Extended Information could be edited. These fields are populated automatically when changing a user ID and are not supposed to be editable.

This has been fixed so that the Previous ID and Previous ID2 fields can no longer be manually edited in the StaffWeb client.

UNI-25426 Lose cursor focus after selecting “Clear”

In the StaffWeb client, when library staff used Check In to check in an item, the cursor would disappear from the Item/Copy ID field if they clicked the Clear button. They then had to click back in the field to make the cursor appear again.

This has been fixed so that the cursor will stay in the field after the user clicks the Clear button.

UNI-26094 Add Brief Title displayed more fields than those defined in the template

This problem occurred in the StaffWeb client. When library staff used the Add Brief Title wizard to add a new copy, fields were appearing on the Title Information tab that did not belong in the Add Brief Title template.

This has been fixed so that the Add Brief Title template only contains the fields that it should.

UNI-26784 Inconsistent display of PIN field in Maintain Users wizard

In the StaffWeb client, the PIN label was displaying without the PIN field when library staff used the Maintain Users wizard to register a new user or display an existing user.

This has been fixed so that the PIN field will also display.

UNI-27013 User ID was not printing on transit slips

In the StaffWeb client, the user ID was not printing on transit slips. Instead, “Undefined” appeared in place of the user ID.

This has been fixed so that the user ID will now print correctly on transit slips.

UNI-27019 Item Activity report was not returning results if “Suppress Item Detail” was set to “No”

In the StaffWeb client, the Item Activity report was not displaying the report result if the option for “Suppress Item Detail” was set to “No.” This error was due to an invalid character in the call number, but the report did not return that information.

This has been corrected so that if a call number has an invalid character, the report will now return that information.

UNI-27026 Add Brief Title wizard failed regularly when adding multiple items

Previously in the StaffWeb client, the Add Brief Title wizard would occasionally display errors when library staff tried to create the title and add the copy.

The Add Brief Title wizard has been fixed so that this workflow will function without error.

UNI-27030 Performance enhancements Maintain User wizard

Some users encountered timing out issues when creating a new user in the Staffweb client.

This has been corrected by performance enhancements that have been made to Create User in the Staffweb client.


62 Release Notes

Z39.50

UNI-27368 Unable to display “MISSING” item in item status

In the StaffWeb client, users found that items with a status of “MISSING” were not displaying in the Item Status wizard.

This has been fixed so that items with “MISSING” status will display in the Item Status wizard.

UNI-29315 Items would not trap to fill holds In StaffWeb, users found that an item in transit to fill a hold would not update the hold to “Available” when it was received at the hold pickup library. The item would remain in transit rather than moving to “HOLD.”

This has been corrected so that items received from in transit at the hold pickup library will be marked as available for patron pickup.


UNI-23420 Core file was no longer produced and message no longer displayed when users tried to start Z39.50 sessions

Library staff found that the Z Server (catzserver) transaction server would sometimes stop responding. When this happened, users trying to start Z39.50 sessions would see the following message even though the library had configured a sufficient number of Z39.50 connections:

“Too many clients connected”

In addition, a core file would be created when the Z Server stopped responding.

This has been corrected so that core files are no longer created, and users can successfully start Z39.50 sessions.


Documents

SirsiDynix Symphony 3 - lincnet.info · SirsiDynix welcomes and appreciates your comments on its documentation. We ... † SIP2 on page 22. Section 2: Enhancements 4 Release Notes