MARCH Release Notes SirsiDynix Symphony Service Pack 1

Transcription

1 MARCH 2017 Release Notes SirsiDynix Symphony Service Pack 1

2

3 Contents Overview 1 Comments and suggestions 1 Enhancements 2 Circulation 2 Miscellaneous 4 SirsiDynix e-library 5 Fixed bugs 6 Cataloging 6 Circulation 7 Configuration 9 Miscellaneous 10 Reports 10 SIP2 13 SirsiDynix e-library 14 Compatibility with SirsiDynix products 16 Known issues 18 Upgrade notes 20 SirsiDynix Symphony Upgrade 20 Remote SirsiDynix e-library Upgrade 21 iii

4 Overview These SirsiDynix Symphony Service Pack 1 Release Notes cover new features and bug fixes since SirsiDynix Symphony For more information about any of these notes, please see the SirsiDynix Symphony WorkFlows Online Help. This document contains these sections: Enhancements on page 2 Fixed bugs on page 6 Compatibility with SirsiDynix products on page 16 Known issues on page 18 Upgrade notes on page 20 As a result of a security update to SirsiDynix e-library for version Service Pack 1, users must have cookies enabled in their browser in order to use SirsiDynix e-library. For more information, see UNI on page 5. Comments and suggestions SirsiDynix 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 docs@sirsidynix.com. 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. Comments and suggestions 1

5 Enhancements This section contains information about key features and enhancements in SirsiDynix Symphony Service Pack 1. Enhancements are modifications to the software from the previous version. The following topics each include a table with a list of Service Pack 1 enhancements, with their corresponding tracking numbers, and a brief description of how each enhancement improves functionality. Circulation on page 2 Miscellaneous on page 4 SirsiDynix e-library on page 5 Circulation UNI Holds on checked out items associated with active reserve records no longer allowed if the Holdable property in the RESERVES Location policy is not enabled Items with a current location of RESERVES can no longer have holds placed on them after they are checked out (moved to the CHECKEDOUT location) if the Holdable attribute in the RESERVES Location policy is not enabled. The check out transaction (and the change of the item's location to CHECKEDOUT) no longer makes the item available to fill holds as before. However, these items can still have holds placed on them using an override. The Holdable attribute for an item is determined in its associated Location policy. For more information, see the "Location Wizard" topic of the WorkFlows Online Help. Note: Items associated with non-active reserve control records do not have a current location of RESERVES; therefore, these items still qualify to fill holds as before. Circulation 2

6 Enhancements UNI UNI Prefer onshelf items having most or least recent activity Two new options, "Prefer onshelf items having most recent activity within the following number of days" and "Prefer onshelf items having least recent activity prior to the following number of days", were added to the Library policy. These options use the Date Discharged, Last Activity Date, or the Date Created attributes of an item to determine if SirsiDynix Symphony should prefer that item to fill a hold. Depending on which option is enabled, the feature can facilitate circulation of older or newer items. For more information on these options, see the "Library Wizard" help topic of the WorkFlows Online Help. Important: The availability and use of these options are mutually exclusive; you can have either one of these options enabled to appear in your library system's Library policies, but not both at once. Note: These options must be enabled to appear by SirsiDynix Customer Support; if your library site is interested in using one of these options, contact SirsiDynix Customer Support. Circulation 3

7 Miscellaneous Enhancements UNI Halt and run for other SirsiDynix agents added to SirsiDynix Symphony auto_haltrun script The auto_haltrun script can now be configured to halt and run other SirsiDynix agent services in addition to the SirsiDynix Symphony services. The auto_haltrun script can now halt and run the following SirsiDynix agent services: BLUEcloud Analytics ILS Agent BLUEcloud Harvester Enterprise ILS Agent For more information about this feature, see the "Configuring SirsiDynix agent processes to halt and run using the auto_ haltrun script" topic of the WorkFlows Online Help. Additionally, the auto_haltrun script has also been enhanced to accept arguments specific to halting and running agent processes. For more information, see the "FAQs: Creating an Automatic Server Halt and Run Script for UNIX Systems" topic or the "FAQs: Creating an Automatic Server Halt and Run Script for Windows Servers" topic of the WorkFlows Online Help, depending on which type of server your site uses. UNI Diacritics removed from SirsiDynix Symphony file names Diacritics in some SirsiDynix Symphony file names prevented some backup utilities such as fsbackup from properly backing up Symphony server files. All diacritics and special characters have been removed from SirsiDynix Symphony server file names, which will allow backup utilities such as fsbackup to properly back up the Symphony application. Miscellaneous 4

8 SirsiDynix e-library Enhancements UNI Support for use of ISSN for retrieving journal cover images from Syndetics Solutions SirsiDynix e-library has been updated to support display of journal cover images in search results and detail displays for any sites using Syndetic Solutions that has a current subscription to Bowker. UNI Autocomplete disabled by default for login fields in SirsiDynix e-library To ensure the security of user login information, autocomplete functionality has been disabled by default for User ID, Alternate ID, and PIN/Password fields within SirsiDynix e-library; Internet browsers will no longer automatically fill in these login fields by default. If your site still wants to allow Internet browsers to automatically fill User ID, Alternate ID, and PIN/Password fields in SirsiDynix e- Library, contact SirsiDynix Customer Support. UNI Enhanced protection from cross site-scripting attacks SirsiDynix e-library has been enhanced with additional security measures that protect users from cross site-scripting attacks that alter results pages. UNI Removal of session number from SirsiDynix e-library URLs As part of a series of SirsiDynix e-library security improvements, SirsiDynix e-library no longer includes user session numbers in generated URLs. Important: As a result of this security update, users must have cookies enabled in their browser in order to use SirsiDynix e- Library. SirsiDynix e-library 5

9 Fixed bugs This section contains a list of all resolved issues, or fixed bugs, for SirsiDynix Symphony Service Pack 1. Fixed bugs are problems that SirsiDynix has identified through the testing process and fixed for this release version. The following tables include a list of fixed bugs for Service Pack 1 with their 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 Service Pack 1 release. Cataloging on page 6 Circulation on page 7 Configuration on page 9 Miscellaneous on page 10 Reports on page 10 SIP2 on page 13 SirsiDynix e-library on page 14 Cataloging UNI Systems using dynamic indexing of hold database cannot delete items from titles with holds For sites using the dynamic indexing of the hold database feature, if a user attempted to remove multiple items from a title with holds, some of the items would not be deleted because of an improper "The records are currently in use. Please try again later." error message. This has been fixed so that this error message does not appear when deleting items from a title with holds for sites using the dynamic indexing of the hold database feature. Cataloging 6

10 Circulation Fixed bugs UNI Print Checkout Slip right-click option prints previous user ID for lost materials Previously, if a patron had a checkout marked lost with the Mark Item Lost wizard and the staff user used the "Print Checkout Slip" right-click option to print a receipt for the checkout, the printed slip contained the user ID of the last patron to have checked out the item instead of the user ID of the current patron. This has been fixed so that the slip printed by using the "Print Checkout Slip" right-click option contains the correct user ID. UNI Hold record's Available flag remains at "Y" after associated item is checked out before Clean Holds Shelf report is run Previously, checking out an item that had an inactive but available hold record could result in the "Available" hold property for that item remaining at Y instead of changing to N. This problem resulted in SirsiDynix Symphony including these checked out items in the results of the Clean Holds Shelf (Cleanholdshelf) report. This has been fixed so that items with inactive but available hold records have their "Available" hold property set to N when they are checked out, which ensures that SirsiDynix Symphony does not include them in the results of the Clean Holds Shelf report. Circulation 7

11 Fixed bugs UNI Multiple swipe payments using the same dollar amount within five minutes may result in an error For sites using BLUEcloud Commerce for WorkFlows or SirsiDynix e-library, users would receive a "Invalid or duplicate transaction attempt." message if multiple BLUEcloud Commerce payments of the same money amount were made to the same merchant account within a five minute period, even if the last transaction belonged to a different user or took place on a different workstation. After five minutes had passed since the last transaction, the user could make a successful transaction. To resolve this problem, the system now determines whether or not multiple transactions of the same money amount belong to different users; if the user has been specified in the transaction (in WorkFlows) or is logged in to SirsiDynix e-library, processing multiple transactions of the same money amount going to the same merchant account within a five minute period will not prompt an error message unless at least one of the transactions is anonymous (does not contain a user ID), such as in a Cash Management transaction. Important: WorkFlows still returns the "Invalid or duplicate transaction attempt." message when a transaction without a user ID of a particular money amount is made less than five minutes within another transaction of the same money amount going to the same merchant account. In this case, wait five minutes and try the transaction again. UNI WorkFlows returns "Illegal Exception Number" message when checking in a lost and paid for item on systems with Cash Management enabled Previously, when a user at a library that had Cash Management enabled attempted to check in an item that had been lost and paid for, WorkFlows returned an "Illegal Exception Number" message and did not check in the item; additionally the refunded amount was not credited to the checkin user's account and Cash Management did not receive a record of the refund. This has been fixed so that lost items that have been paid for at libraries with Cash Management enabled can be checked in; the refunded amount is credited to the checkin user's account and the refund is recorded in Cash Management. Circulation 8

12 Fixed bugs UNI Bill receipts showing wrong paid amount when "Subtotal by bill reason" option is enabled and when paying multiple bills at once Beginning with SirsiDynix Symphony 3.5, if the "Subtotal by bill reason" option was enabled for slips showing payments (via the "Print slip showing payments" options in some circulation wizard properties) and the user attempted to pay multiple bills simultaneously, WorkFlows would sometimes print incorrect "Subtotal by bill reason" amounts on the bill receipt. This has been fixed so that WorkFlows prints the correct amounts for the "Subtotal by bill reason" entries on bill receipts when a user pays multiple bills simultaneously. UNI Checkout Override alert not appearing when it should for preventing a checkout for an item with a hold In cases where a librarian removes a hold that a first patron had on an item after the item was on the holds shelf and a second patron had placed a hold on that item, a librarian could check out the item out to a third patron who had not placed a hold without being alerted. This has been fixed to display the Checkout Override alert when a librarian attempts to check out an item that was placed on hold. Configuration UNI Policies missing from policy wizard lists for containing other policy names for sites using customized policy lists Previously, if a site used customized policy lists and excluded a policy of a given type that contained a name of another policy of that type at the end of its name (for example, "ILL-BOOK" contains the name of another Item Type policy, "BOOK", at the end of its name), the policy with the shorter name was also excluded from the customized policy lists, despite not having been specified in the list of excluded policies. This has been fixed so that only policies that have been specifically excluded are excluded from customized policy lists. Configuration 9

13 Miscellaneous Fixed bugs UNI Named-type Station policies could not be used after the SirsiDynix Symphony server was cycled if the policies were in use during the cycle Beginning with SirsiDynix Symphony version 3.5.1, if WorkFlows sessions were running when the server was cycled, any Namedtype Station policies that were being used by the open WorkFlows sessions could not be used after the server was finished cycling; users would receive a "Too many tries of login" error when attempting to log in to WorkFlows using one of the affected Station policies. This has been fixed so that Named-type Station policies in use when the SirsiDynix Symphony server cycles become available again after the server finishes cycling. UNI Oracle on UNIX/Linux systems not restarting after the SirsiDynix Symphony upgrade For UNIX/Linux sites using an Oracle database and SirsiDynix Symphony 3.5.2, if a user ran the auto_haltrun script using any kind of shell aside from Bash, the script failed to stop or start Oracle. This has been fixed so that Oracle stops and starts properly on UNIX/Linux systems when a user runs the auto_haltrun script using a shell aside from Bash. Reports UNI Serial Control Records report not printing bibliographic record titles when pipe-delimited output is selected Previously, the Serial Control Records (serctllist) report would not print a bibliographic record's title associated with a serial control record, when pipe-delimited formatting was selected. This has been fixed to print the bibliographic record's title. Miscellaneous 10

14 Fixed bugs UNI Purge Finished report not removing finished reports that have a number sign character (#) in their titles Previously, if a report name contained a number sign character (#) in its title, the Purge Finished Reports (Purgefinrpts) report could not remove that report from the list of finished reports. This has been fixed so that the Purge Finished Reports report can now remove reports that have a number sign character in the name. UNI Remove Items by Location report causing SirsiDynix Symphony server to become unresponsive When the Remove Items by Location (Rembylocation) report was run with "116. Dynamic updating of the holditems db" enabled and the report removed large numbers of records, it could cause the server hosting SirsiDynix Symphony to become unresponsive. This was fixed to minimize the number of processes initiated by the report and reduce the load on the server. UNI NOSALE worksheet not being populated in Cash Management End of Day report spreadsheet Previously, SirsiDynix Symphony did not properly populate the NOSALE worksheet in the Cash Management End of Day report's spreadsheet output; population of the cells in the NOSALE worksheet required manual intervention. This has been fixed so that SirsiDynix Symphony properly populates the NOSALE worksheet in the Cash Management End of Day report's spreadsheet output without manual intervention. UNI "Rebuild DB Concurrently" report option does not work on Windows systems Previously for Windows systems using a segmented database, the "Rebuild DB Concurrently" option (which allowed the report to build more than one database segment at a time) in the Rebuild Text Database, Rebuild Item Database, and Add, Delete, Update Item reports did not work; database segments were always built sequentially regardless of the option's setting. This has been fixed so that the "Rebuild DB Concurrently" option works as expected for these reports on Windows systems. Reports 11

15 Fixed bugs UNI Optimization of setting catalog status within Rebuild Text Database report The Rebuild Text Database (Rebuildtext) report has been optimized to perform at faster speeds. Previously, the report would run the Editcatalog API tool once for each BRS segment to update catalog record statuses. For systems using an ISAM database, the report's new behavior is to only run Editcatalog once for all BRS segments together. For SQL sites, the report's new behavior is to use an SQL statement to update the catalog statuses. Additionally, the report previously ran the Prepload binary once for each BRS segment for deleting catalog keys in /Unicorn/Database/Edit; now, the report does not use Prepload to make the deletions, but makes the deletions itself. These changes result in shorter runtimes for the Rebuild Text Database report. UNI "Print Separate Reports for Each Library" option causes Clean Holds Shelf report to stop responding Previously, if the "Print Separate Reports for Each Library" option was enabled in the Clean Holds Shelf (Cleanholdshelf) report, the report would stop responding. This has been fixed so that using the "Print Separate Reports for Each Library" option in the Clean Holds Shelf report will not cause the report to stop responding. UNI Windows-formatted LDUSER files with 0D and 0A line endings not corrected by User Data Upload wizard, causing the user records not to be loaded via Load Users report SirsiDynix Symphony was not removing 0D line ending characters when a user uploaded Windows-formatted.LDUSER files to the SirsiDynix Symphony server using the User Data Upload wizard in WorkFlows; this caused the Load Users report to return "Input label not found" errors and fail to load the user records when trying to process these.lduser files. This has been fixed so that the User Data Upload wizard properly removes 0D line ending characters from.lduser files, allowing the Load Users report to load users from these files properly. Reports 12

16 SIP2 Fixed bugs UNI When the hold of an item in transit is cancelled, the item does not transit correctly when checked in using SirsiDynix Symphony SIP2 Previously, if a hold was canceled for an item in transit to the hold pickup library, the transit record remained intact when the item was checked in using a SIP2 client. The item still showed in SirsiDynix Symphony as being in transit to the pickup library; therefore, no messages were given to staff to return the item to its owning library. To address this problem, a new configuration was added to SirsiDynix Symphony SIP2 which allows libraries to specify what should happen to items in transit after they are checked in via SirsiDynix Symphony SIP2. Libraries can choose to either have SirsiDynix Symphony SIP2 untransit the item and evaluate where the item should go or to only untransit items if the checkin library is the destination library. The default behavior is to have SirsiDynix Symphony SIP2 untransit the item and evaluate for the item's next action, so there is no need to add the configuration for all your SIP2 client ports if you want SirsiDynix Symphony SIP2 to use this behavior. If you do not want SirsiDynix SIP2 to untransit items upon checkin, you will need to set the appropriate configuration for any sip2.cfg port configurations associated with SIP2 clients used to check in materials. For more information about this new option, see the "Editing the SIP2 single port configuration file (sip2.cfg)" topic of the SirsiDynix Symphony SIP2 Configuration Guide. SIP2 13

17 SirsiDynix e-library Fixed bugs UNI SirsiDynix e-library not generating weblog.z files correctly for the "You Found Titles in Categories" feature Previously for SirsiDynix e-library sites using the "You Found Titles in Categories" feature, SirsiDynix e-library would not properly generate weblog.z files (which stored information about which categories users clicked), instead generating a weblog.Z or weblog file with a log entry of WEBLOG_BLANK for each time a user clicked a category. This has been fixed so that SirsiDynix e-library generates weblog.z files with the appropriate date of category clicks and saves relevant information in the log entries. UNI Enhanced Content not retrieved by OCLC number Previously, SirsiDynix e-library did not retrieve Bowker Syndetics content (book cover images, reviews, etc.) for titles based on their OCLC number; e-library required that either an ISBN or UPC value be in the bibliographic record for retrieving Bowker Syndetics content for a title. As a result, bibliographic records that had an OCLC number but not an ISBN or UPC did not receive enhanced content for display in SirsiDynix e-library. This has been fixed so that SirsiDynix e-library can display enhanced content based on the OCLC number in a bibliographic record. UNI Edition statement never displays in Item Details display Beginning with SirsiDynix Symphony Service Pack 2, the edition information of a given title would not display in the Item Details display in SirsiDynix e-library. This has been fixed so that edition information displays as before in the Item Details display in SirsiDynix e-library. SirsiDynix e-library 14

18 Fixed bugs UNI "Remove checked titles" button for SirsiDynix e-library My Lists feature not working Since SirsiDynix Symphony Service Pack 1, the "Remove checked titles" button in for the SirsiDynix e-library My List feature did not work. This has been fixed so that the "Remove checked titles" button now works for the SirsiDynix e-library My List feature as expected. UNI SirsiDynix e-library cannot create permalinks if there is an apostrophe in the search terms Previously, if an apostrophe character was included in a SirsiDynix e-library search, e-library could not create a permalink for the search; clicking the "Permalink" button would have no effect. This has been fixed so that SirsiDynix e-library can create permalinks for searches containing an apostrophe character. UNI Permalinks generated by SirsiDynix e-library not properly URL-encoded Previously, permalinks generated by SirsiDynix e-library were not properly URL-encoded; as a result, permalinks containing searches that had any special characters (including but not limited to spaces or quotation marks) would return a "page not found" error. This has been fixed so that permalinks generated by SirsiDynix e-library are now URL-encoded; permalinks of searches containing special characters now direct to the expected page in SirsiDynix e-library. SirsiDynix e-library 15

19 Compatibility with SirsiDynix products Compatibility with SirsiDynix products This section outlines which versions of the listed SirsiDynix products offer full functionality and compatibility with SirsiDynix Symphony Service Pack 1. BLUEcloud applications Product BLUEcloud Analytics BLUEcloud Cataloging BLUEcloud Circulation BLUEcloud Commerce BLUEcloud Search Service MobileCirc Compatible versions Discovery Product BLUEcloud PAC BookMyne for Android BookMyne for ios BookMyne+ Compatible versions Enterprise eresource Central Social Library

20 Compatibility with SirsiDynix products Agents Product BLUEcloud Analytics ILS Agent BLUEcloud Harvester Enterprise ILS Agent Compatible versions Web Services Product Web Services for Symphony Compatible versions Other products Product Compatible versions Director's Station Web Reporter (1) 1. Web Reporter is not compatible with SirsiDynix Symphony systems using an Oracle 12c database. 17

21 Known issues This section contains information about known issues and possible work arounds in version Service Pack 1. Known issues are reported issues that may impact your use of the product, but have not been fixed in this version. The following are known issues for version Service Pack 1. UNI SirsiDynix e-library systems using Microsoft IIS inaccessible because of (bad gateway) error Attempts to reach a SirsiDynix e-library system that is served using Microsoft IIS may result in a (bad gateway) error, making SirsiDynix e-library inaccessible. A workaround for this problem is to push the permissions for the IIS_IUSRS group back onto the D:\Sirsi\Unicorn directory structure. To do this, temporarily remove a permission and select it again. Click Apply, then wait for IIS to push the permissions. SirsiDynix e-library systems that are served using Apache are not affected by this problem. UNI Online User Registration Activate User page allows users to be created with a lowercase User ID The Activate User page within Online User Registration wrongly allows users to create new users using a lowercase User ID. Users with a lowercase User ID cannot log in to WorkFlows or be found via searching in WorkFlows. 18

22 Known issues UNI Navigation back to SirsiDynix e-library after logging out results in an error if COOKIE_SECURITY is disabled in Webcat/Config/webconfig For systems with the COOKIE_SECURITY variable disabled in the Webcat/Config/webconfig file, if a user logs out of SirsiDynix e-library and navigates back to it, they wrongly receive the following error message: Your Internet browser seems to have cookies disabled. This website requires cookies to work. Click "OK" to refresh the page after you have enabled cookies for this website. If you're not sure how to enable cookies, see the help documentation for your Internet browser. Because of this problem, SirsiDynix recommends that sites using SirsiDynix e-library set the COOKIE_SECURITY variable to 1 in the Webcat/Config/webconfig file. UNI Navigating back to SirsiDynix e-library from CAS login page can allow users to browse e-library anonymously If a user attempts to log in to SirsiDynix e-library and is redirected to the CAS login page (while the e-library CAS_ LOGIN_TYPE environment variable is set to 2), then uses their web browser's back button to navigate back to e-library, the user can be wrongly allowed to browse e-library anonymously. There is no workaround. UNI Old help links saved in web browser cache may interfere with accessing help from context It is possible that WorkFlows users may receive a "page not found" error when accessing the WorkFlows Online Help from a given context in WorkFlows. This problem is caused when links to pages in older versions of the WorkFlows Online Help stored in the web browser's cache do not match the page links in the SirsiDynix Symphony Service Pack 1 version of the WorkFlows Online Help. The workaround for this problem is to clear the web browser's cache and try again; accessing the WorkFlows Online Help from context will then work as expected. 19

23 Upgrade notes Follow these instructions for upgrading from SirsiDynix Symphony to SirsiDynix Symphony Service Pack 1. These instructions assume a basic familiarity with your server and SirsiDynix Symphony system. SirsiDynix Symphony Upgrade Follow these steps for every instance of SirsiDynix Symphony. 1. Before upgrading, be sure to perform backups of your system, especially of your database. 2. Verify that you are set up for patches by checking for the existence of the Unicorn/Sirsiserv/Patch_delivery directory, which should include the patch_ install.pl script. If these don't exist, follow the instructions for setting up your system for service pack/patch installs, which you can find at You will need to log in with your SirsiDynix Support Center credentials and download the instructions. 3. Run perl patch_install.pl v from a command prompt/terminal in the Unicorn/Sirsiserv/Patch_delivery directory. This will check to see if the script needs to be updated and update it to the most current version. 4. Download the service pack file by running the command perl patch_install.pl e S3.5.2.SP1_GA from a command prompt/terminal in the Sirsiserv/Patch_delivery directory. 5. Halt your SirsiDynix Symphony services/servers before installing Service Pack 1. Refer to the WorkFlows Online Help for instructions on how to halt the SirsiDynix Symphony services on your system. 6. For non-windows SirsiDynix Symphony Oracle systems, run oracleadmin status from a terminal. If Oracle is halted, run oracleadmin run. On Windows Oracle systems make sure the Oracle services are running. 7. Install the service pack by running the perl patch_install.pl S3.5.2.SP1_GA command from a command prompt/terminal in the Unicorn/Sirsiserv/Patch_ delivery directory. Note: If you encounter errors, contact SirsiDynix Customer Support. 8. Run the prepare_web command from a command prompt/terminal on the server where Apache or IIS is installed. Answer all the questions in prepare_web and when prompted enter 'YES' to save your answers. Once prepare_web finishes, run the setup_webcat command with the parameters given from the output of prepare_web. Note: You may have to be the root user to run the setup_webcat command. 9. Start your SirsiDynix Symphony services/servers. Refer to the WorkFlows Online Help for instructions on how to start the SirsiDynix Symphony services on your system. SirsiDynix Symphony Upgrade 20

24 10. For systems using SirsiDynix e-library, make sure the value of the COOKIE_SECURITY environment variable is set to 1 in the /Unicorn/Webcat/Config/webconfig file. Upgrade notes Remote SirsiDynix e-library Upgrade Follow these steps for every instance of remote SirsiDynix e-library. 1. Before upgrading, be sure to perform backups of your remote SirsiDynix e-library system, especially of your database. 2. Verify that you are set up for patches by checking for the existence of the Unicorn/Sirsiserv/Patch_delivery directory, which should include the patch_ install.pl script. If these don't exist, follow the instructions for setting up your system for service pack/patch installs, which you can find at You will need to log in with your SirsiDynix Support Center credentials and download the instructions. 3. Run perl patch_install.pl v from a command prompt/terminal in the Unicorn/Sirsiserv/Patch_delivery directory. This will check to see if the script needs to be updated and update it to the most current version. 4. Download the service pack file by running the perl patch_install.pl e S3.5.2.SP1_REMOTE_GA command from a command prompt/terminal in the Sirsiserv/Patch_delivery directory. 5. Halt your remote SirsiDynix e-library services before installing Service Pack 1. Refer to the WorkFlows Online Help for instructions on how to halt remote SirsiDynix e-library services on your system. 6. Install the service pack by running the perl patch_install.pl S3.5.2.SP1_REMOTE_ GA command from a command prompt/terminal in the Unicorn/Sirsiserv/Patch_ delivery directory. Note: If you encounter errors, contact SirsiDynix Customer Support. 7. Run the command prepare_web from a command prompt/terminal on the server where Apache or IIS is installed. Answer all the questions in prepare_web and when prompted enter 'YES' to save your answers. Once prepare_web finishes run the setup_webcat command with the parameters given from the output of prepare_web. Note: You may have to be the root user to run the setup_webcat command. 8. Make sure the value of the COOKIE_SECURITY environment variable is set to 1 in the /Unicorn/Webcat/Config/webconfig file. 9. Start your remote SirsiDynix e-library services/servers. Refer to the WorkFlows Online Help for instructions on how to start the remote SirsiDynix e-library services on your system. Remote SirsiDynix e-library Upgrade 21