sirsidynix symphony 3.4 - rhodes...

SirsiDynix Symphony 3.4.1

Release Notes

December 2011

© 2011 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.1. Information in this document may also be compatible with later versions.

12/2011

iii

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

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

Where to locate the upgrade instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Section 2: Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Cataloging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

OPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Serials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SIP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Section 3: Fixed bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Accountability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Acquisitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Cataloging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Circulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Collection Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

EDI /X12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

OPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Serials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

SIP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 4: SirsiDynix Agent and System Data Collection . . . . . . . . . . 37What is the SirsiDynix Agent? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

What system data is collected? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

How often is the data collected? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Contents

Contents

iv

How much network bandwidth is used for this? . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Why are you collecting this data? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Do you collect patron data? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Why are you telling us about this?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

What should I do if I have further questions? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

1

Section 1: Overview

These Release Notes cover new features, system requirements, and bug fixes since SirsiDynix Symphony 3.4. 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 15

• SirsiDynix Agent and System Data Collection on page 37

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.

Where to locate the upgrade instructionsWith previous releases of Symphony, the instructions for upgrading to a new version were accessed through the Software Delivery Service on the Client Care site. Starting with the release of 3.4.1, the upgrade instructions are available as a PDF specific for your hardware and database and are available on the SirsiDynix Support Center. You can access them by going to the Doc Browse tab, opening the Symphony tree item, and selecting Announcements. The instructions are found in the announcement for Symphony 3.4.1.

Symbol Description

This symbol indicates an enhancement or fixed bug that was the result of 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.1 software. The following includes a list of version 3.4.1 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.1:

• Authority on page 4

• Cataloging on page 4

• Circulation on page 7

• Configuration on page 8

• Miscellaneous on page 10

• OPAC on page 10

• Reports on page 11

• Serials on page 12

• SIP2 on page 13


4 Release Notes

Authority

Cataloging

Tracking No. Enhancement Details

UNI-29380 Implement client-side of Load Subfields and Export Subfields in Catalog and Authority formats

With the inclusion of the Import/Export Tab for entries in the Catalog Format, Authority Format, MARC Holdings Format, and Community Information Format wizards, users can now specify which entry subfields to include or exclude when importing or exporting catalog, authority, bibliographic, Community Information, or MARC Holdings records. The Import/Export Tab includes two attributes: Import Subfields and Export Subfields.

For more information on this new tab, please see the "Import/Export Tab for Entries" help topic in the WorkFlows Java client online helps.


UNI-29380 Implement client-side of Load Subfields and Export Subfields in Catalog and Authority formats

With the inclusion of the Import/Export Tab for entries in the Catalog Format, Authority Format, MARC Holdings Format, and Community Information Format wizards, users can now specify which entry subfields to include or exclude when importing or exporting catalog, authority, bibliographic, Community Information, or MARC Holdings records. The Import/Export Tab includes two attributes: Import Subfields and Export Subfields.

For more information on this new tab, please see the "Import/Export Tab for Entries" help topic in the WorkFlows Java client online helps.

UNI-29503 Catalog formats updated to reflect changes in the MARC 21 cataloging standard

The SirsiDynix Symphony catalog formats were updated to reflect changes in the MARC 21 cataloging standard. Symphony now adheres to the standards for fixed fields in bibliographic formats as outlined in MARC 21 Updates 10,11, and 12.

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


Cataloging 5

UNI-30101 SmartPort and DanMARC2 When some libraries used SmartPort to display and capture records encoded in DANMARC2, they encountered problems with displaying these records due to character encoding problems. SmartPort performs an auto-character conversion from the record set encoding to the Symphony character set encoding as part of the capturing process. As DANMARC2 was not a recognized record character set, SmartPort was unable to automatically convert it to the proper UTF-8 encoding, resulting in the libraries' record display problems.

This has been corrected so that libraries can define the DANMARC2 record character setting in the Gateway Destination element of the OPAC Configuration policies. By using the preprocessing script for DANMARC2, all auto-conversion done on the server when using SmartPort is skipped. This will aid in converting DANMARC2 encoded records into a supported character encoding for proper record display.

System Administrator Note System Administrators will note that in order for DANMARC2 to be available in the OPAC Configuration policies on the SirsiDynix Symphony system, the DANMARC2 MARC Family policy must be defined on the system prior to performing this encoding configuration.

UNI-31375 Improve adutext performance when indexing IUNI db (for Item Group Editor)

When enabled on a library's system, the Item Group Editor (IGE) significantly increased the length of time necessary to complete the run of the Add, Delete, Update Databases (adutext) report. Due to additional indexing required for the item record, adutext had more to process during its nightly runs, causing longer adutext runtimes. For this reason, it was delivered to users as disabled with SirsiDynix Symphony 3.4.

With the inclusion of the new Add, Delete, Update Item (aduitemtext) report, libraries will no longer experience a significantly increased runtime in the adutext report. The aduitemtext report has been created to process the additional indexing required for item records that was previously performed by the adutext report.

For more information on this report, please see the "Add, Delete, Update Item Report" topic in the WorkFlows Java client online help topics.

UNI-31457 Enhance catalogdump by adding a new flag, which when specified includes Catalog format in output

A new argument was included in the API catalogdump tool. This argument allows administrators to specify a 9xx MARC tag in which they can include the Catalog Record Format Policy. Additionally, libraries running SirsiDynix Enterprise will now be able to filter Enterprise search results based on the Catalog Record Format Policy.

For more information about this argument, please see the "SirsiDynix Symphony API Workbook."



6 Release Notes

UNI-32305 Enhance catalogdump to output call number with "substitute text"

A new flag was added to Symphony's Catalogdump tool to allow you to export call numbers with substitute text. If you set up your Classification policy to create substitute text for AUTO call numbers, you can include that text in the data Symphony makes available to SirsiDynix Enterprise. This allows libraries using Enterprise to display the same substitute call number text in Enterprise and e-Library searches.

To learn more about how to create substitute text and modify your Classification policy, see the Workflows Java client online help topic "Classification Wizard." For more information about the new catalogdump argument, see the SirsiDynix Symphony API Training Workbook section "Catalogdump Tool" on page 239.

UNI-32579 Indexing improvements for use with Item Group Editor

In order to improve performance of item indexing for use with the Item Group Editor wizard, the SirsiDynix Symphony system can be configured to selectively index certain fields. You can have the system configured so that all searchable fields are indexed, all except item extended info, all except fields related to circulation functions (circulate flag, last activity date, and current location), or all except item extended info and fields related to circulation functions. Fields that are not indexed do not display when searching in the Item Group Editor.

Alternately, the Item Group Editor can be turned off completely, in which case no item indexing takes place.

For more details and important considerations before having your Client Care representative configure one of these options, see the Upgrade Instructions.



Circulation 7

CirculationTracking No. Enhancement Details

UNI-31747 StaffWeb: Add an option to hide user ID

In the SirsiDynix StaffWeb client, patron, library staff, and academic faculty user IDs displayed on Circulation screens in open settings. This allowed other patrons to see any given user's private user ID.

In an effort to protect the privacy of user information, the "Display User ID in Circulation" option in the SirsiDynix StaffWeb Administration tab under Circulation allows library administrators to determine whether user IDs will display on the Checkout, User Status, and Holds Circulation screens.

To learn more about this option, please see "Circulation Setup Tab" topic in the SirsiDynix StaffWeb online help.

UNI-32156 Hold fee & web services When library patrons placed holds on items via Bookmyne, the appropriate hold fees were not applied within Symphony. This error occurred even when the Symphony system's HOLD policy was set to assess hold fees for patron-placed holds.

This has been corrected so that when a system has been configured to asses fee in patron-placed holds, patrons will be assessed hold fees on holds they place using Bookmyne.

UNI-32759 Ability to send SMS text messages

The SMS messaging add-on allows you to set up your SirsiDynix Symphony system for the manual or automated sending of text messages to your patrons. You can collect patron preferences and mobile phone numbers or you can configure e-Library so that patrons can enter their own information and preferences in the My Account area.

A library administrator can set up message templates for automated or manual sending of messages, or a librarian can type a message for a manual sending of a message to a specific patron. Messages can be created and sent for overdue item notices, holds available for pickup, bill notices, or general library announcements.

For more information about the feature, see "SMS Messaging" in the WorkFlows online help.


8 Release Notes

ConfigurationTracking No. Enhancement Details

UNI-31382 Expandable lists and sections Users found that transaction lists occupied a large amount of UI space in older versions of the WorkFlows Java client.

The WorkFlows Java client user interface has been enhanced to include expandable and collapsible transaction lists. Users can now expand and collapse these lists to make more UI space available to them in Circulation wizards. This enhancement is delivered as the default display for transaction lists. It is only displayed when the client is configured to display user transaction lists in the Circulation wizards (these being the Checkout, Renew User, and Pay Bill wizards).

For more information on how to display these lists, please see the "Display of User Transaction Lists in Circulation Wizards Policy" topic in the WorkFlows Java client online helps.

UNI-31687 Implement the configuration option to display open wizards with tabs.

Libraries running SirsiDynix Symphony 3.4.1 will note that the WorkFlows Java client user interface has been enhanced to display wizard windows as tabs in the client workspace. Users now have the option to use wizards in either multiple tabs or multiple windows. Users may also customize the tab display to have wizard tabs display at the top or bottom of the client workspace. Both the options to enable tabbed windows as well as to customize their display are performed by the user in the Desktop Setup menu of the WorkFlows Java client.

For more information on this enhancement and their customizable options, please see the topics "Wizard Tabs," "Tabbed Windows," and "Tabbed Windows On Bottom" in the WorkFlows online help documentation. The WorkFlows Java client is delivered with the tabbed windows option disabled.

UNI-32556 SDAgent items for 3.4.1 The SD Agent included in SirsiDynix Symphony has been updated to help us provide you with better support. In Symphony 3.4.1, the SD Agent collects operational data from your Symphony system and transmits it to a central SirsiDynix Support Server. The collected data allows us to understand your system better and help you recognize, troubleshoot, and prevent problems.

For more information, see SirsiDynix Agent and System Data Collection on page 37.


Configuration 9

UNI-32579 Indexing improvements for use with Item Group Editor

In order to improve performance of item indexing for use with the Item Group Editor wizard, the SirsiDynix Symphony system can be configured to selectively index certain fields. You can have the system configured so that all searchable fields are indexed, all except item extended info, all except fields related to circulation functions (circulate flag, last activity date, and current location), or all except item extended info and fields related to circulation functions. Fields that are not indexed do not display when searching in the Item Group Editor.

Alternately, the Item Group Editor can be turned off completely, in which case no item indexing takes place.

For more details and important considerations before having your Client Care representative configure one of these options, see the Upgrade Instructions.







10 Release Notes

Miscellaneous

OPAC


UNI-31382 Expandable lists & sections Users found that transaction lists occupied a large amount of UI space in older versions of the WorkFlows Java client.

The WorkFlows Java client user interface has been enhanced to include expandable and collapsible transaction lists. Users can now expand and collapse these lists to make more UI space available to them in Circulation wizards. This enhancement is delivered as the default display for transaction lists. It is only displayed when the client is configured to display user transaction lists in the Circulation wizards (these being the Checkout, Renew User, and Pay Bill wizards).

For more information on how to display these lists, please see the "Display of User Transaction Lists in Circulation Wizards Policy" topic in the WorkFlows Java client online helps.


UNI-27584 Implement pay all option for axis Symphony now allows library patrons to pay all their bills at once using Capita Axis Payment Services. Libraries set up to accept Axis Payment Services can add a pay all button to their patrons' My Account window in e-Library, allowing their patrons to pay all their bills in one easy step.

To learn more about setting up Capita Axis Payment Services, contact your Customer Support representative.






Reports 11

ReportsTracking No. Enhancement Details






12 Release Notes

SerialsTracking No. Enhancement Details

UNI-26785 Multi-lingual MARC holdings In earlier versions of SirsiDynix Symphony, displaying MARC Holdings records' Enumeration/Chronology information was dependent upon the library system's Chronology policies. The Holdings display field in these policies was localized, which caused MARC Holdings record summaries to display based on the system's language.

In SirsiDynix Symphony 3.4.1, libraries can select to display Enumeration/Chronology information in the same language as that of the associated MARC Bibliographic record. The software considers the language element in the 008 field (positions 35 - 37) in the MARC Bibliographic record and translates the Enumeration/Chronology description as determined by this field. The translation is performed on a per publication basis and is not defined by the user login environment.

System Administrator Note In order to configure the system to enable and use this feature in SirsiDynix Symphony 3.4.1, Administrators will note that this version is delivered with the following two sample files in the Unicorn/Custom directory:

• chronology.sample.ascii

• chronology.sample.utf8

The chronology file is what SirsiDynix Symphony uses to translate the Chronology field content. According to the system's encoding, administrators will rename the appropriate file "chronology." Administrators will then edit the files to use the values and languages they require and perform an HIR on their system. SirsiDynix Symphony will identify the file and perform the necessary translations at run-time. By default, the software will look for this file before using the Chronology policy to determine the MARC Holdings record Chronology display, which has been the default policy used to determine Chronology display.

Note: Chronology files are limited to 20 bytes for each display string, with no more than 256 bytes per line.


SIP2 13

SIP2Tracking No. Enhancement Details

UNI-28196 3m pad staff workstation RFID interface SDK

Libraries were previously unable to integrate the latest 3M RFID pad with their SirsiDynix Symphony systems. Previous versions of SirsiDynix Symphony were unable to support using the 3M RFID pad to streamline their day-to-day circulation workflow.

SirsiDynix Symphony now supports the latest 3M RFID pad. Libraries running SirsiDynix Symphony are now able to effectively integrate it into their day-to-day work seamlessly. See the WorkFlows Java client online help topics under the "Checkout Wizard Properties" and "Discharge Wizard Properties" topics for more information on this feature enhancement.


14 Release Notes

15

Section 3: Fixed bugs

This section contains a list of all resolved issues, or fixed bugs, for SirsiDynix Symphony 3.4.1. The following includes a list of fixed bugs for the SirsiDynix Symphony 3.4.1 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.1 release:

• Accountability on page 16

• Acquisitions on page 16

• Authority on page 18

• Cataloging on page 18

• Circulation on page 20

• Collection Exchange on page 24

• Configuration on page 24

• EDI /X12 on page 26

• OPAC on page 26

• Performance on page 29

• Reports on page 29

• Request on page 32

• Searching on page 32

• Serials on page 34

• SIP2 on page 35


16 Release Notes

Accountability

Acquisitions

Tracking No. Summary Description

UNI-29508 Set CD Number report fails When users would run the Set CD Number report set to select items with a Pending Destruct Date and within a date range specified in the Restrict Selection tab, the report would fail to select those items in the Certificate of Destruction.

This has been corrected so that the report will now select items with a Pending Destruct Date within the date range that users specify in the Restrict Selection tab.


UNI-26711 VIP not working with certain ordering services

Previously, when a library staff member used the Vendor Information Port (VIP) helper in the Acquisitions module wizards with certain ordering services, the VIP helper would indefinitely hang.

This has been fixed so that the VIP helper works properly with these and other ordering services.

UNI-30937 EDI x12 and remit to vendor field

Previously users were unable to use EDI invoicing to automatically calculate taxes based on Acquisitions tax policies. In order to perform this task, users would manually create invoices and calculate taxes by setting the Session Settings of the Acquisitions module to calculate invoice taxes automatically.

Users can now perform this function automatically via EDI. The option to calculate invoice taxes automatically has been added to the Book X12 Invoices report's Tax tab. For more information on this enhancement, see the WorkFlows online help under the "Book X12 Invoices" topic.

UNI-31444 Order rollover does not roll over Material Type in orderline

Acquisitions staff that use Acquisitions Tax and Material Type in their orders were unable to roll over an order's Material Type. This occurred when the staff would run the Rollover Basic Orders, Rollover Dated Orders, and Rollover Recurring Orders reports.

This has been corrected so that the Material Type is rolled over in all orders when using the Rollover Basic Orders, Rollover Dated Orders, and Rollover Recurring Orders reports.

UNI-31699 Link Order Hold report is removing the call number sequence in the hold record for holds against on-order titles with no items

When running the Link Order Hold report, users found that the report would remove the call number sequence in the on-order title's hold record. Only on-order titles without items were affected.

This has been corrected so that the Link Order Hold report will no longer remove the call number sequence from hold records for holds on on-order titles without items.


Acquisitions 17

UNI-32278 Modify invoice unpays tax invoice lines in 3.4

When modifying invoices using the Modify Invoice wizard, some users noticed that modifying an invoice would unpay the tax lines in the invoice. With automatic tax calculation set in the Acquisitions Session Settings wizard, users would create an invoice and pay all of the lines in the invoice. Users would then open the invoice in the Modify Invoice wizard, click the button to modify the invoice, and would find that the date the taxes were paid was changed to NEVER. This error was only produced for libraries using an Oracle database.

This has been corrected so that when users modify invoices with the "Calculate invoice taxes automatically" option selected in their Acquisitions Session Settings, the Modify Invoice wizard will not unpay the invoices' taxes.



18 Release Notes

Authority

Cataloging


UNI-32283 961 tag not created in authority record when existing authority is overlaid by SmartPort capture

When updating or replacing an existing authority record with a new authority record using SmartPort, users discovered that SmartPort would not create the 961 tag in the authority record.

This has been corrected so that the 961 tag is created and saved correctly when using SmartPort to update or replace existing authority records.

UNI-32713 Windows adutext report not observing addprovisional setting

When running the Add, Delete, Update Databases (adutext) report, the addprovisional variable was not working properly on Windows and Unicode systems. When the addprovisional variable is set to "yes," this report should create new PROVISIONAL authority records from headings found in bibliographic records.

This has been fixed so that the new PROVISIONAL authority records are created.


UNI-29258 Print labels w/ Item Cat1 or Cat2 if blank shows value from previous

Users printing labels for an item found that if the item's Item Cat1 or Item Cat2 fields were blank, they were filled with the Item Cat1 or Item Cat2 from the last item's printed label.

This has been corrected so that if any field in an item record is left blank, the printed label for that item will reflect those blank fields.

UNI-29859 Large number of Edit Item Globally processes cause Windows CPU to spike to 100%

When libraries modified a large number of items using the Edit Item Globally wizard in SirsiDynix Symphony, they often found that these edits caused their Windows CPU usage to increase up to 100%. This elevated usage would result in a large amount of orphaned cataloging, bibload, circulation, OPAC searching, and SIP processes.

This has been corrected so that users can use the Edit Item Globally wizard to modify a large number of items without occupying their entire CPU usage.

UNI-30531 Problem with display of UNIMARC titles with NSB/NSE characters

In Symphony 3.4, UNIMARC records with NSB/NSE (Non-Sorting Begin/Non-Sorting End) characters displayed repeated letters in their headings in the Java WorkFlows client. These records could also create errors when you exported them. This has been fixed so that records with NSB/NSE characters display correctly. To learn more about NSB/NSE characters, see "FAQs: Working with UNIMARC Formats" in the Java WorkFlows client help.


Cataloging 19

UNI-30897 The mhldload tool not setting MARClist values properly

Administrators noted problems with setting the Record Type and Location MARClist fields using the mhldload tool. When Administrators used this tool to load MARC Holdings records into their systems, they noticed corruption in these records that inhibited them from running reports which depended on filtering these records using the Record Type and Location MARClist fields. The mhldload tool is intended to set these values automatically, however, when the Record Type and Location MARClist fields were included in the SirsiDynix Symphony 3.2 release, the mhldload tool was not updated to include those fields.

This has been corrected so that, when called, the mhldload tool will appropriately set the values for the Record Type and Location MARClist fields.

UNI-30981 Problems with browsing headings on MSSQL

Previously, when Microsoft SQL users performed browse searches they encountered hitlist corruption, specifically when the hitlist contained headings with diacritics. Users found that some records would be missing from the hitlist if it contained headings with diacritics.

This has been corrected so that users will no longer encounter this type of hitlist corruption.

UNI-31817 Dynamic indexing of bib. records noticeably slower on Windows

Libraries running SirsiDynix Symphony 3.4 or 3.3.1 with the UNI-29290 patch experienced noticeably slower dynamic indexing of bibliographic records when performing tasks in the WorkFlows Java client. This problem was unique to libraries using Windows Server.

The dynamic indexing process has been streamlined so that libraries on Windows will not experience such slowness when performing tasks involving dynamic indexing.

UNI-32371 Call numbers are sorted incorrectly

When running the List Bibliography and List Call Number reports, users found an error in the sorting of the call numbers. The call Numbers did not follow logical numerical order.

This has been corrected so that call numbers are ordered properly within these reports.

UNI-32408 BRS is matching on records that it should not, which is causing "duplicate item key in text with following ckey" errors

Library staff found intermittent errors when running the Add Delete Update Databases report on SirsiDynix Symphony 3.4. The errors indicated that some BRS queries were not processing when they contained more than one document with the same catalog key, sequence, and copy number, producing the following error message: Duplicate item key in text.

This has been corrected so that users will not encounter the duplicate item key in text message when running the Add Delete Update Databases report.



20 Release Notes

CirculationTracking No. Summary Description

UNI-21564 StaffWeb: Search by full user name results in no checkouts displaying

Circulation librarians could not view a user's current list of checked out items in the Checkout and Place Hold tabs in the StaffWeb client. This regularly occurred when librarians performed a full name user search, with the search returning a single user.

This has been corrected so that circulation librarians can now view a user's current checked out items when performing a full name user search.

UNI-21765 List on shelf hold report fails halfway through the run

Some consortium libraries running SirsiDynix Symphony 3.3 reported that the List on Shelf Hold report would occasionally fail when they selected the option to generate an individual report for each library in their group.

This has been fixed so that the List on Shelf Hold report now finishes successfully, even if the individual report option is selected.

UNI-27505 Clean on shelf hold report ignoring the date inactive selection

Users running the Clean Holds Shelf report noticed that the report was ignoring their selections when filtering holds. This issue was unique to libraries with Oracle systems.

This has been fixed so that the Clean Holds Shelf report takes the user's selections for all hold fields into account when running and selecting holds.

UNI-28560 Clean hold shelf report - Item shows at home library when it's not

Libraries running the Clean Holds Shelf report found that the report would erroneously change the current location of some items. This occurred when users ran the report with the "Trap hold" option unchecked and the "Transit item" option checked. The problem occurred in the report when clearing items belonging to another library from the hold shelf. If the next hold for a given item was for pickup from the current location, the report would change the item's status to STACKS in the item's home library. This caused circulation problems as these items would then appear in the home libraries' List Onshelf Items with Holds report. Additionally, library patrons could search the home libraries' catalogs for these items and find them listed as being in their STACKS without them actually being there.

This has been fixed so that the Clean Holds Shelf report appropriately modifies these items' current location when run as described above. A new drop down menu labeled Current Location has been included in the Trap Holds tab of the report. This drop down menu allows the user to specify the current location to which the hold items are sent when the report is run.

For more information on the Current Location drop down menu, please see the "Trap Holds Tab" topic in the WorkFlows Java client online help.


Circulation 21

UNI-30298 Interval circ counts do 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-30954 Clean on shelf hold report fails halfway through

Some consortium libraries running SirsiDynix Symphony 3.3.1 or 3.4 reported that the Clean Holds Shelf report would occasionally fail when they selected the option to generate an individual report for each library in their group.

This has been fixed so that the Clean Holds Shelf report now finishes successfully, even if the individual report option is selected.

UNI-31323 OPAC NO_HOLDS hold range not working correctly

Some libraries experienced difficulties with the OPAC NO_HOLDS hold map line. Occasionally, users were able to place holds on items after they had already reached the NO_HOLDS line, a feature which should impede users from making holds on certain items.

This has been fixed so that the OPAC NO_HOLDS hold map line functions as expected.

UNI-31619 Charge history helper is disabled in checkout when user has charge history records

The Charge History helper was erroneously disabled on various libraries' systems even after it had been configured for use on their systems. Libraries discovered this when attempting to display users who had charge history records. This bug occurred when the user status header and transaction list were not configured to display.

This has been corrected so that the user record is read when the Charge History helper is enabled. Libraries can now use the Charge History helper regardless of the user status header and transaction list configuration.

UNI-31620 Properties for renew item wizard Users who selected the "Item seen" checkbox in the Renew Item wizard's properties to mark the item as seen at wizard startup discovered that this property configuration selection was not carried over to the Renew Item wizard on startup as expected. Despite the Item seen checkbox being selected, the Mark Item as Seen checkbox was not automatically selected when the Renew Item wizard was started.

This has been fixed so that the Item seen checkbox in the Renew Item wizard's properties properly initializes the Mark Item as Seen checkbox in the Renew Item wizard.



22 Release Notes

UNI-31653 Volume holds - All holds placed on single volume

Users often encountered difficulties placing multiple volume holds using e-Library. When users searched for a title with multiple volumes and attempted to place a hold on each volume, they later discovered that e-Library placed multiple holds against the title's first volume rather than one hold on each of the title's volumes. Only libraries who had configured the OPAC Hold Range option experienced this problem.

This has been corrected so that when users place holds on a title's multiple volumes e-Library will place the holds on each of the title's volumes as expected.

UNI-31681 Onshelf items with hold wizard - Selecting items with current location of ON ORDER when system is configured not to

Some users encountered configuration problems with displaying specific hold items in the Onshelf Item wizard. After setting the Configure locations for Onshelf Items wizard policy to exclude items whose current locations were ONORDER and/or UNAVAILABLE, users found that these ONORDER items would still appear in the Onshelf Holds Items list for the their owning libraries.

This has been corrected so that if a user sets the Configure locations for Onshelf Items wizard policy to exclude items whose current locations are ONORDER and/or UNAVAILABLE, the Onshelf Items wizard will not display those items.

UNI-31699 Link Order Hold report is removing the call num sequence in the hold record for holds against on order titles with no items

When running the Link Order Hold report, users found that the report would remove the call number sequence in the on-order title's hold record. Only on-order titles without items were affected.

This has been corrected so that the Link Order Hold report will no longer remove the call number sequence from hold records for holds on on-order titles without items.

UNI-31749 Assumed Lost report using a location that does not exist when marking items lost

Some libraries reported that after upgrading to SirsiDynix Symphony 3.4 the Assumed Lost report would attach items and charges to a location policy that did not exist. These location types are normally designated as NOPOLICY, however, the report would include these types at random when users ran the Assumed Lost report.

This has been corrected so that the Assumed Lost report no longer looks for location types that are not in the policies file.

UNI-31778 User alerts displaying in Catalan but not in English

Libraries running SirsiDynix Symphony in Catalan discovered erroneous user alerts that did not appear when running SirsiDynix Symphony in English. These user alerts displayed in all wizards in the Circulation module and were due to an error in the UI translation of user statuses.

This has been corrected so that the user alert functionality does not differ between the English and Catalan localizations.



Circulation 23

UNI-32297 StaffWeb PIN - Cannot edit if global configuration is set to hide PINs

When library staff changed PIN numbers using SirsiDynix StaffWeb they found that their changes were not saved. This primarily occurred when the Display PIN in Hidden Format option in the WorkFlows Java client's global configuration was enabled, thus displaying user PINs with asterisks.

This has been corrected so that changes to PIN numbers using the StaffWeb client will be saved, even when the WorkFlows Java client has been configured to not display user PINs.

UNI-32412 Hold transit slip prints wrong user

Library circulation staff found that they could not print transit slips containing accurate information when trapping items to fill blanket holds. The incorrect transit slips, when printed, displayed an incorrect user name for the item's hold.

This has been corrected so that library circulation staff can print transit slips with the correct user name when trapping items to fill blanket holds.

UNI-32463 SVA not working on Linux systems

Users could not create notice records (specifically phone notifications) when running the Prepare Notices report in the SVA group of reports. This error occurred due to a size problem in the database table used for notices. Only libraries running SirsiDynix Symphony with SVA on 64 bit Linux Oracle systems were affected.

This has been corrected so that users can create phone notifications using the Prepare Notices report as designed.

UNI-32727 Reorder Holds does not perform as expected

On systems using MS SQL or Oracle, holds placed after a hold queue was reordered using the Reorder Hold Queue wizard were not inserted into the queue in the correct position.

This has been fixed so that the hold queue gets ordered correctly.



24 Release Notes

Collection Exchange

Configuration


UNI-28656 CE module slowness especially in exchange item wizard

Some libraries experienced slowness in the Collection Exchange module. At times, a user could expect to wait up to nine seconds to place a scanned item in Collection Exchange. Additionally, a user could expect to wait over two minutes for some Collection Exchange wizards to open (e.g., the Exchange Items wizard). The slowness within the Collection Exchange module was due to a high level of structural complexity within several database queries.

This has been corrected so that libraries no longer experience performance slowness within the Collection Exchange module.

UNI-31352 The xlibcounter report still not respecting selections

Library staff discovered discrepancies between what the Maintenance - Exchange Counters (xlibcounters) report log reported and what operations the xlibcounters report performed. Users would select to update INACTIVE libraries when running the xlibcounters report, However, the report log would show more libraries than only those with an INACTIVE status as having been considered and selected. When verifying the log against the actual report output, users found that the xlibcounters report accurately respected their selections, in spite of what the report log displayed. Additionally, library staff found inaccuracies in the xlibcounters report log when combining various selections.

The WorkFlows Java client report selections have been modified to help eliminate some of the confusion regarding the report selections.

For more information on this change, please see the "Maintenance - Exchange Counters Report" online help topic in the WorkFlows Java client.

UNI-31501 Maintenance - Exchange Counters (Xlibcounters) report error

Previously, when you ran a Maintenance - Exchange Counters (Xlibcounters) report, item data with non-existent catalog data could cause your report to end prematurely. This has been fixed so that Maintenance - Exchange Counters (Xlibcounters) reports run to completion.


UNI-32325 Pre-defined catalog search error Previously, when you set up a pre-defined catalog search (such as "Find it FAST" or "Kid's Library") using the maximum number of characters allowed in each search field, performing the search in e-Library returned an error message saying ""#EYError in field size (setting general info)." This has been fixed so that you can successfully specify a value in each field using the maximum allowed number of characters.


Configuration 25

UNI-32432 Chinese policy names become corrupted after certain programs are run

Libraries using SirsiDynix Symphony in non-Latin based languages (e.g., Chinese) they found that the "Save as template" function in the Reports module corrupted non-Latin based policy names, specifically classification names, holdings codes, and sometimes even library policy names. Users experienced this corruption even on Unicode encoded systems.

This has been corrected so that users will not experience character corruption from the "Save as a template" function in the Reports module.

UNI-32468 MAC client upgrade issue The Workflows Java client for Mac continuously requested the user to update the Workflows client even after updating because of a corrupted timestamp file.

This has been corrected so that when Mac users are prompted to update their WorkFlows Java client and do so, the update successfully installs on their client.



26 Release Notes

EDI /X12

OPAC


UNI-32537 An extractx12 Segmentation Fault on RHEL 5 x64

Previously, running the EDI File Receipt (Edireceive) report on Red Hat Enterprise Linux systems could cause the report to end prematurely with a "Segmentation fault" error message. This has been fixed so that the EDI File Receipt (Edireceive) report now runs without problems.


UNI-30347 Unable to place hold for specific volume of a multi-volume item

OPAC users discovered that when they attempted to place a hold on an individual volume of a multi-volume item that they were not given the option to select their preferred volume.

This has been corrected so that when e-Library users attempt to place this type of hold, they are directed to a Place Hold page containing an option to select their desired volumes to place on hold.

UNI-31653 Volume holds - All holds placed on single volume

Users often encountered difficulties placing multiple volume holds using e-Library. When users searched for a title with multiple volumes and attempted to place a hold on each volume, they later discovered that e-Library placed multiple holds against the title's first volume rather than one hold on each of the title's volumes. Only libraries who had configured the OPAC Hold Range option experienced this problem.

This has been corrected so that when users place holds on a title's multiple volumes e-Library will place the holds on each of the title's volumes as expected.

UNI-31806 The e-Library client hangs when booking an item

When using e-Library to create bookings, some libraries were unable to create a booking for an item with existing bookings. This operation would cause e-Library to hang indefinitely.

This has been fixed so that users can successfully create multiple bookings for an item on e-Library.

UNI-31834 The e-library 9.pg file does not retain CSS customizations

Consortium libraries encountered problems with customized e-Library 9.pg files. System Administrators in these libraries would modify these pages to help patrons to discern which branch of the consortia they were accessing in e-Library. When a patron encountered a cgiopac time out error, the 9.pg files would revert to the delivered default version, thus returning patrons to an unfamiliar e-Library page.

This has been corrected so that cgiopac time out errors will not affect the customizations System Administrators make to the 9.pg files.


OPAC 27

UNI-32291 ADA compliance table compatibility

Non-sighted users had difficulty with conceptually processing increasing table sizes in the Checkouts page of the iLink My Account module.

This has been corrected by adding table headers to link cells to the column headers. By doing so, non-sighted users can orient themselves within the Checkouts page with ease.

UNI-32292 ADA compliance non-mouse navigation for non-sighted users

Users with mobility impairments, specifically those unable to use a mouse, were unable to adequately navigate through the tabs in the iLink My Account module using a keyboard.

This has been corrected so that users with mobility impairments can successfully navigate through the iLink My Account module using a keyboard.

UNI-32293 ADA compliance header descriptions

Non-sighted users encountered difficulty reading pages within the iLink My Account module using screen reading technology. This was due to size and implementation problems with HTML headings.

By removing some HTML headings, this has been corrected. Non-sighted users can now use screen reading technology to read iLink My Account pages with greater ease.

UNI-32325 Pre-defined catalog search error Previously, when you set up a pre-defined catalog search (such as "Find it FAST" or "Kid's Library") using the maximum number of characters allowed in each search field, performing the search in e-Library returned an error message saying ""#EYError in field size (setting general info)." This has been fixed so that you can successfully specify a value in each field using the maximum allowed number of characters.

UNI-32333 A search_title.h page file error When the Find it Fast! search feature was configured to include a sixth search field in a given subcategory, users found that e-Library frequently displayed the sixth search field's text in an incorrect location in the user interface.

This has been corrected so that users do not encounter this misplaced text in the Find it Fast! search feature.

UNI-32355 Search key being ignored, find it fast, first defined search key

When librarians or patrons used the e-Library Find it Fast! search feature, they noticed that the resulting hitlists returned incorrect results. Rather than performing the guided search using the search keys defined in the Gateway Database, the guided search was performed using the Gateway Database descriptions.

This has been corrected so that users can perform a guided search using the Find it Fast! feature and expect to receive the requested results.



28 Release Notes

UNI-32358 netlibrary sometimes not giving the checkout link

Some Remote e-Library administrators discovered that several binary files were missing from the Remote e-Library 3.4 build. Without these files, netlibrary would produce a broken checkout link in the Remote e-Library interface.

This has been corrected for the 3.4.1 release of Remote e-Library.

UNI-32431 OPAC display errors when content data is bad

Previously, when an incomplete book list file was generated by the "Index Content Titles" or "Update e-Library Content Lists" report in Java Workflows, e-Library would display the message "Policy does not exist" and repeat the e-Library header image. This message and the repeated image could cause patron confusion. This has been fixed so that e-Library displays a normal header image at all times and a small "Text error" error message in place of the best-seller or e-Library content list if either list is corrupt.



Performance 29

Performance

Reports


UNI-31817 Dynamic indexing of bib. records noticeably slower on Windows

Libraries running SirsiDynix Symphony 3.4 or 3.3.1 with the UNI-29290 patch experienced noticeably slower dynamic indexing of bibliographic records when performing tasks in the WorkFlows Java client. This problem was unique to libraries using Windows Server.

The dynamic indexing process has been streamlined so that libraries on Windows will not experience such slowness when performing tasks involving dynamic indexing.


UNI-27557 A selitem change in 3.3.1 causing 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.

UNI-28027 Cash reports and floating stations

Libraries found that the Cash Report Per Workstation (cash), Daily Cash (cashdaily), and Monthly Cash (cashmonthly) reports incorrectly processed some transactions from floating stations. Users logging in to the system via floating station are automatically assigned a number. Often these assigned numbers extend beyond the number of stations listed in the Station wizard. This being the case, the cash report often missed processing transactions from some of the floating stations assigned these extended numbers. Libraries would run these reports and find that many of these transactions were not caught or processed when they were performed from these floating stations.

This has been corrected so that the cash, casdaily, and cashmonthly reports will capture all transactions that users perform on floating stations, should the user choose to do so. The same Count Floating Stations option under the Count Selection tab in the cash report has been added to both the cashdaily and cashmonthly reports to ensure that all transaction from all floating stations are counted should the user select to count them in those reports.


30 Release Notes

UNI-28560 Clean Holds Shelf report - Item shows at home library when it's not

Libraries running the Clean Holds Shelf report found that the report would erroneously change the current location of some items. This occurred when users ran the report with the "Trap hold" option unchecked and the "Transit item" option checked. The problem occurred in the report when clearing items belonging to another library from the hold shelf. If the next hold for a given item was for pickup from the current location, the report would change the item's status to STACKS in the item's home library. This caused circulation problems as these items would then appear in the home libraries' List Onshelf Items with Holds report. Additionally, library patrons could search the home libraries' catalogs for these items and find them listed as being in their STACKS without them actually being there.

This has been fixed so that the Clean Holds Shelf report appropriately modifies these items' current location when run as described above. A new drop down menu labeled Current Location has been included in the Trap Holds tab of the report. This drop down menu allows the user to specify the current location to which the hold items are sent when the report is run.

For more information on the Current Location drop down menu, please see the "Trap Holds Tab" topic in the WorkFlows Java client online help.

UNI-31347 fixusercounts report is clearing counts on HP/oracle

Library staff using SirsiDynix Symphony on HP Oracle systems found problems with the Correct User Information (fixusercounts) report. Rather than updating user records with correct user counter information (e.g., the user's number of bulls, bookings, charges, holds, available holds, reserves, and routings), the report cleared all of the user counter information in each user record processed.!p:This has been corrected so that library staff can use the fixusercounts report to correct user records containing incorrect user counter information.

UNI-31496 The aduusertxt report failing at 3.4 customer sites

Libraries using SirsiDynix Symphony 3.4 on Windows systems found themselves unable to run the nightly Add, Delete, Update User (aduusertext) report. This report would frequently fail mid-process due to an error involving locked dynamic indexing files. This bug also affected some Circulation notice reports, as well as the Expire Holds report.

This has been fixed so that the locked dynamic indexing files are released, allowing libraries to successfully schedule and complete all affected reports.



Reports 31

UNI-31560 The biborderload report taking too long to run on Windows sites after install of UNI-29290 patch

Libraries running SirsiDynix Symphony on Windows found that several reports experienced a significantly longer run time after installing the UNI-29290 patch. This was due to problems with the way the reports performed their dynamic indexing. The following reports were affected:

• bibload

• biborderload

• bibreload

• fliphdngbyauth

• fliphdngbycat

• loadaccent

• loadbib

• loadmicrolif

• selectbibemb

• selectbib

• updsubfield

This has been corrected so that libraries running Windows can install the UNI-29290 patch without experiencing a lengthened run time for these reports.

UNI-32306 adutext errors for 3.4/Windows/MSSQL sites being implemented

Some libraries running SirsiDynix Symphony 3.4 on Windows or Microsoft SQL found that the adutext report finished its scheduled nightly runs with an ERROR status, producing various errors in its log. These errors contained the following message:

cat: write error: Invalid argument

The adutext report encountered these errors because of the move from cygwin to gnuwin tools on Windows platforms, which required a different method of handling some UNIX shell commands.

This has been fixed so that libraries can expect the adutext report to finish its scheduled nightly runs without producing these errors.



32 Release Notes

Request

Searching


UNI-27682 Request reply where Catalog Key optional returns Item not found in catalog

SirsiDynix Symphony users found that when they attempted to reply to a request using the Reply tab of the Modify Request wizard they were always met with an error which impeded them from replying. This occurred when the Request Type policy's "Catalog key required" option was set to optional. The error stated that the item was not found in the catalog.

This has been corrected. Users can now reply to requests without receiving this error when the Request Type policy setting 'Catalog key required' is set to optional.


UNI-30339 Search part program loops or crashes

The search part program runs each time users search for a record. This part program normally closes after the search is complete; however, if the 035 field of a bibliographic MARC record is too long (around 85 characters or more), the search part program will not close immediately.

On most systems, these trailing part programs are resolved through other processes. However, on systems running Red Hat Linux 5, the search part programs remain open, taking up the system's available memory, which can lead to the system slowing down or crashing. Although this issue is more prevalent on Red Hat Linux 5, it could occur on any operating system.

This has been fixed in SirsiDynix Symphony 3.3.1 Patch Cluster 2 so that these part programs close once searches are complete, leaving the CPU without the burden of trailing, incomplete processes that exhaust the system.

UNI-30981 Problems with browsing headings on MSSQL

Previously, when Microsoft SQL users performed browse searches they encountered hitlist corruption, specifically when the hitlist contained headings with diacritics. Users found that some records would be missing from the hitlist if it contained headings with diacritics.

This has been corrected so that users will no longer encounter this type of hitlist corruption.

UNI-31642 MSSQL -- Browse search occasionally fails to find closest match

When performing browse searches on a Microsoft SQL system, users were not directed to the closest match in the search hitlist This occurred on occasion and normally when the closest matching heading appeared alphabetically near other headings with hyphens.

This has been fixed so that when users perform a browse search they are directed to the closest matching result in the hitlist.


Searching 33

UNI-31644 MSSQL - Exact search not working correctly

Some libraries running SirsiDynix Symphony on MSSQL received an error message when attempting to perform exact searches. The error message read, "Unable to complete request." This error was due to a previous fix involving browse searches and headings with diacritics (see UNI-30981).

This error has been fixed so that SirsiDynix Symphony users on MSSQL can perform both exact searches and browse searches without experiencing these issues.

UNI=32640 Chinese keyword searching Since the introduction of Unicode into SirsiDynix Symphony, the segmentation used for Chinese language searching did not work correctly.

This has been fixed so that the correct segmentation is used for Chinese language searches.



34 Release Notes

SerialsTracking No. Summary Description

UNI-22282 Enter key does not work on OK button of Checkin Special Instruction screen

When users attempted to check in serials that had special instructions using the WorkFlows Java client, they were unable to select the OK button on the Special Instructions screen using the Alt+O or Enter keyboard shortcuts.

This has been corrected so that users may select the OK button using the designated keyboard shortcuts.

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-30549 Prediction as Late (issuelate) report ends with an ERROR status for no valid reason

Library staff found that the Finished Reports wizard would display the Prediction As Late (issuelate) report as completing in error, when it really completed successfully. Library staff saw that the report successfully created claims for the selected issues, despite the displayed error status.

This has been corrected so that the Finished Reports wizard displays the proper completion status for the Prediction As Late report.

UNI-31175 Custom reports (customized routing slips) after upgrade

Library staff found that customized routing slips were not printing as expected. Library staff would print these slips in the process of checking out serial items to library patrons. If there was no address listed on the user's record, the resulting printed slip did not align the date field correctly.

This has been corrected so that the printed slip retains the correct field alignment, even when some fields are left blank.


SIP2 35

SIP2Tracking No. Summary Description

UNI-31283 SIP checkin not working with available soon

SirsiDynix Symphony users found that when checking in an item using SIP whose current location was set as AVAIL_SOON, the item's location would not change to match the home location.

This has been fixed so that users can use SIP to check in AVAIL_SOON materials successfully.

UNI-31503 SIP won't stay connected on Windows Oracle systems

Some libraries using SIP on Windows Server experienced SIP connectivity problems when performing transactions. Often they were unable to perform more than three transactions on self-check machines before they were disconnected from the SIP server. Users would find an error message in the event log citing the disconnection. This was due to many unresponsive sipsession and sipserver processes being performed during the transactions.

This has been corrected so that Windows Server libraries no longer encounter these SIP connectivity problems and thus no longer receive this error message.


36 Release Notes

37

Chapter 4: SirsiDynix Agent and System Data Collection

This section contains information regarding the SirsiDynix Agent (SD Agent) for Symphony 3.4.1.

What is the SirsiDynix Agent?The SD Agent is a lightweight process that sits on your Symphony server and performs a number of helpful functions. For customers with Director’s Station, the SD Agent is responsible for managing the ETL process that extracts report data from your Symphony systems and makes it available to the Director’s Station application.

With the release of Symphony 3.4.1, the SD Agent will perform a new function – collecting system configuration data and sending this information to a central SirsiDynix Support Server to help us provide better customer service. The SD Agent will periodically contact the SirsiDynix Support Server to see if the server needs a system data refresh. If so, the SD Agent will collect the data from various locations and transmit that data back to the SirsiDynix Support Server.

The SD Agent will also create a local copy of the data it sends to the SirsiDynix Support Server. You can access this file on your Symphony system to see important information about your system configuration and circulation statistics.

What system data is collected?The SD Agent collects the following data from your Symphony system:

• Site Identifier – this is the 3 or 4 character code that is assigned to your system during install

• Symphony version (for example, Symphony 3.3.1 PC1)

• Database type and version (for example, Oracle 10.2.0.4)

• Operating System type and version (for example, Microsoft Windows 2003 SP2)

• Values in the Symphony configuration file (that is, the output from the prtconfig utility)

• Title count (that is, the total number of title records in your database)

• Circulation statistics, which includes the following data:

– Total checkouts

– Total renewals

– Interval checkouts (with ‘last cleared’ date)


38 Release Notes 3.4.1

– Interval renewals (with ‘last cleared’ date)

How often is the data collected?Configuration settings on the SirsiDynix Support Server control the frequency of data collection. The process works as follows:

1. Every 12 hours, the SD Agent contacts the Support Server to see if any action needs to be taken.

2. The Support Server responds with an action message if anything needs to happen. For this release of Symphony, the only available action is to collect the system data listed above. In future releases we can introduce other actions, such as changing system settings.

3. If an action is needed, then the SD Agent will perform the action and transmit any appropriate data to the Support Server. As the only available action is to collect the system data, the SD Agent will collect the data and transmit this back to the Support Server.

4. The SD Agent will write a file on your local Symphony system. This file is identical to the data transmitted to the Support Server, allowing you to see exactly what data we are collecting.

Currently, the data collection frequency is set to once every 7 days (that is, weekly). If we collect more ‘real time’ data such as CPU and memory utilization, we might increase the frequency of data collection.

How much network bandwidth is used for this?The interactions between the SD Agent and the SirsiDynix Support Server consume very little bandwidth. The initial SD Agent connection to the Support Server (step 1 above) and the action response message (step 2) are 800 bytes each. These messages occur once every twelve hours. The data collection message (step 3) is 22KB per Symphony system at your site and occurs once per week. If we modify the SD Agent to collect real-time data, we would look at segmenting the collected data so that only changed data is transmitted back to the Support Server. This segmentation would save network bandwidth.

Why are you collecting this data?We want to collect this data for a number of reasons, the primary ones being:

• To give us better knowledge of your system configuration and environment when you request help from SirsiDynix Client Care.

• When you call Client Care, the application support person who deals with you case will look up your system environment in our Salesforce.com system. However, this information is not always up to date, nor is it always comprehensive. For example, our information in Salesforce.com might say that


Do you collect patron data? 39

you are running on Red Hat Linux 4 with Oracle, even though you upgraded to Red Hat Enterprise Linux 5.0 and Oracle 10g a few months ago. The data collected by the SD Agent will ensure that we know what operating system and database you are using and the version of each.

• To help us better understand the breadth of different system configurations and environments in which Symphony is running.

• Within SirsiDynix Engineering, we run a comprehensive suite of tests prior to releasing any version of Symphony – whether a full release, a patch cluster, or a single patch for a specific customer. We always try to test the release candidate software in environments that are representative of the production systems being used by our customers. However, if the representative environments are based on inaccurate or stale data, we might be doing you a disservice. By collecting the system configuration data via the SD Agent, we can ensure that we have a better understanding of the production environments in use and that we tailor our testing environments to better match the reality of your systems.

• To provide the base data collection mechanism for a future proactive support service. For example, we could see high system usage and provide proactive optimization or configuration changes and recommendations.

• The ultimate goal of the SD Agent data collection is to provide a proactive support service to our customers. We want to gather real time data from the production Symphony systems so that we can preemptively warn you of possible problems – for example, if a log file is reaching its maximum size, or if your Symphony system has high CPU or memory usage, or if we notice a profile or property setting that is not recommended and might cause issues later. Obviously, to provide this type of service we need a data collection mechanism that allows us to detect system anomalies. The SD Agent is the first step in creating this mechanism. Over time, we will collect more system data and look for potential problems and, we hope, notify you before these problems occur or even correct the underlying issues before they become problems.

• To help you avoid breaches of contract and the associated fees.

• Some Symphony customers have licenses limited by certain License Metrics. For example, your license may limit the maximum number of titles or amount of circulation at your site. The file the SD Agent writes on your system allows you to easily keep track of your License Metrics to ensure you comply with your license. Please review your contract or contact SirsiDynix Customer Care if you have any questions about your license metrics or how to view the file the SD Agent writes on your system.

Do you collect patron data?No. We will not collect any data that will identify individual patrons, members of the library staff, or individual transactions, such as check in or check out. We respect the privacy of your patrons and the members of the library staff and we do not want to violate this privacy. We have no interest in this data. It does not add any value to the system data or help us achieve our stated goals.


40 Release Notes 3.4.1

Why are you telling us about this?We want to be completely upfront about how and why we collect this data. We believe that collecting this data will allow us to provide you with better products and a better Customer Care service. Proactive monitoring of your system will help prevent downtime or slow system responses and will help you to provide a better service to your patrons. The data will also allow us to test new releases of Symphony and e-Library on systems that are more representative of the environments that you are using day in and day out. If you would like to disable our data collection service, please contact Customer Care.

What should I do if I have further questions?We are more than willing to answer any questions that you have about the SD Agent and the system data collection. Please direct any questions to SirsiDynix Product Management at [email protected]. If necessary, our product management team will call you to discuss your concerns.

sirsidynix symphony 3.4 - rhodes...

Documents