Summary
Release Notes
Sierra 6.1 is currently in general release.
Sierra 6.1 went into general release on December 4, 2023. We released a Sierra 6.1 maintenance update on April 8, 2024. This maintenance update version of Sierra 6.1 will display in the Help | About section of the SDA as Software Release: Sierra 6.1.0_10. The version of Sierra 6.1 released on December 4, 2023 will display in the Help | About section of the SDA as Software Release: Sierra 6.1.0_9. Any library, running Sierra 6.0 or older, that preps for update to Sierra 6.1 after April 8, 2024, noon PDT will receive version Sierra 6.1.0_10. Libraries running Sierra 6.1.0_9 that want the fixes included in Sierra 6.1.0_10 can update to that version by choosing to (again) update to Sierra 6.1. For further information about which fixes are included in Sierra 6.1.0_10, see Resolved Issues in Sierra 6.1. Sierra 6.1.0_10 also includes Sierra changes to support LX Starter notices for consortia, which have been added to the end of the 6.1 features list below. |
NOTE: Customers with Encore need to be at least Encore 4.6 SP2 in order to upgrade to Sierra 6.1.
CAUTION: In Sierra 5.2 and later, the SDA must run on Java 1.8 and will no longer launch if run on Java 1.6 - see Sierra 5.2 Release Notes.
New features in Sierra 6.1
Description | Recommended Pre-Upgrade Action | Recommended Post-Upgrade Action |
---|---|---|
SAML login for staff users This enhancement allows libraries to use native SAML-based authentication in Sierra so that staff at those libraries will be able to login to the Sierra Desktop Application (SDA) and Web Management Reports using the institution's central authentication system, while those users not included in the central authentication system may still login to the SDA and Web Management Reports using Sierra's native credentials such as username and password. In this second phase of SAML login for staff, the SDA and Web Management Reports now support multiple modes of staff authentication:
Multi-factor authentication can be enabled with SAML login to provide extra security for staff user logins so libraries can move away from older security methods (e.g., VPN connections). It is expected that libraries will need to configure their identity provider for multi-factor authentication to make this work. | None | The native SAML-based authentication software must be installed separately. Contact your account manager for implementation services. Separate fees will apply if Innovative implements SAML configuration for your library. No fees apply if the customer configures SAML authentication using the self-configuration option in Sierra 6.1. |
Upload of SSO IDs for staff SAML Added an "Upload SSO IDs" command to the SAML Configuration section of the Admin app. The upload uses a simple text/csv file input. A comma-separated file of username/SSO ID pairs is expected (and a header line that will be ignored). SSO IDs must be unique to be saved in Sierra. SSO IDs are case-sensitive. | None | None |
Customer configuration for SAML Authentication To make it possible for customers to configure SAML authentication on their own, a SAML Configuration section has been added to the Sierra Admin App. To configure patron or staff SAML, the library staff user must be assigned new SAML Administrator permission (725). The self-configuration option allows library or IT staff to configure and test the connection between Sierra and the institution's IdP, customize the login screen, and enable/disable the SAML authentication use with Sierra. | None | None |
Export a table of User Permissions Exporting user permissions will enable library administrators to easily review and compare the permissions assigned to each user to:
A new option to "Export Permissions" was added to the Admin App > User Accounts > Authorizations and Authentication > (select a user). The current user is selected and additional users can be selected. Administrators can filter the list by typing in user information or "Select All" users. Clicking the "Export Permissions" button produces a csv file of the permissions for the selected users (where the rows are users and the columns are permissions). | None | None |
Re-bill Patrons for Outstanding Charges Libraries want to be able to send follow-up bills to patrons who owe the library money for lost materials and other unpaid charges. This enhancement provides a configurable setting that allows the library to send multiple bills to patrons with outstanding balances. The library can configure how many bills will be sent and how many days apart the bills can be prepared. The new Repeated Bills notices must be configured by the library after upgrade and prior to sending the follow-up bills to patrons. | None | None |
Reprint Bills Library staff will be able to reprint a previously sent bill from the patron's notice history. Bills can be reprinted from the Fines tab of the patron display using either a new right-click menu option or the Reprint Bill button. To be eligible to be reprinted, a bill must have been sent after upgrade to Sierra 6.1 and in the last 60 days and must still have a balance due. Bills that are more than 60 days old or have been fully paid or waived are automatically purged from the Sierra database. Staff users must have permission 361 to reprint bills. | None | None |
Show Time of Last Status Update Date Based on customer requests, the last status update date introduced in Sierra 6.0 has been enhanced to show the date and time the status was last changed. | None | None |
Add Last Status Update Date to Create Lists The last status update date field has been added to Create Lists to allow library staff to search for records using this field, and to list, sort, and export data using this field. | None | None |
Protect Global Update files on server from accidental overwrite Library staff members who use Global Update will see updated options in the File menu to make it easier to select either "Load" or "Save" actions and new pop-up messages to confirm the correct command file is being saved. This will help prevent accidental overwrite of command files to ensure that library staff don't replace detailed command files with others by mistake. | None | None |
Send ILL requests to RapidILL RapidILL is a fast and cost-effective interlibrary loan tool tailored for article and book chapter requests. For Sierra 6.1, Innovative has introduced a new acquisition method - RapidILL. Choosing this option and finishing the request will send the request to the RapidILL web pages. Once the request data has been transmitted, library staff can continue processing the request using the RapidILL web pages. The customer illoptions file must be configured to include this new option. Customer prompts for article and book chapter requests must conform to our documented prompt configuration - https://documentation.iii.com/sierrahelp/Default.htm#sgcir/sgcir_ill_prompts.html In order to proceed with configuration, we will need the following details for your RapidILL account:
| None | The RapidILL software must be installed separately. Contact your account manager for more information. Separate fees will apply. |
Modify INN-Reach Borrowed Report to follow renewal rule The INN-Reach Borrowed Report, originally added in Sierra 5.3, has been updated with a new option that allows renewal rules to be enforced. A new checkbox option, Enforce renewal rules, applies renewal rules based on library policies. Messages are displayed for the items that cannot be renewed. Associated permissions:
| None | None |
Support new MARC 856 subfield for linking New MARC 21 standards have been implemented recently to support hyperlinks to persistent identifiers in MARC records using 856 $g. $g - Persistent identifier (R) This enhancement adds support for hyperlinks to include the newly defined 856 $g when using record display options (DISPLAY_856 and DISPLAY_CHECKIN_856) and the URL Checker. | None | None |
Location data for items in LX Starter notices New data elements have been added to the notice data for LX Starter to provide a match location and location group to allow LX Starter to select the notice template to use when sending notices to library patrons. * This feature is new in the Sierra 6.1 Maintenance Release (6.1.0_10) | None | None |
Unique identifier in notice data sent to LX Starter A unique identifier has been included for each item in the notice data sent to LX Starter to prevent duplicate items from being listed in notices sent to library patrons. * This feature is new in the Sierra 6.1 Maintenance Release (6.1.0_10) | None | None |
Sierra 6.1 System Changes and Important Fixes
Description | Recommended Pre-Upgrade Action | Recommended Post-Upgrade Action |
Library admin option to restart Sierra Web Sierra Web can and does hang occasionally at some libraries and the short-term remedy is to restart the Sierra Web container. This enhancement adds a new choice to the Admin Corner menu: "W > Restart Sierra WEB", which allows affected libraries to conveniently resolve Sierra Web issues on their own. | None | None |
Upgrade management of SW_SESSIONS_PER_TOMCAT In Sierra 6.0, we began to work with libraries to increase the number of Sierra Web users. This enhancement in Sierra 6.1 will enforce the maximum user setting in iiiconfig.main during an upgrade. The change allows the Sierra upgrade process to continue to increase a library's user count to the assumed default (60) if the value at upgrade time is found to be lower, while not decreasing the value if it has already been set higher. | None | None |
Check Range in Scheduler Tasks Sierra 6.1 resolves Known Issue SIERRA-38667 "When creating a Scheduler Task, Scheduler saves the range start and stop as the current first and last record numbers, and these cannot be modified. This means that when new records are created, the task will never consider them." After upgrading to Sierra 6.1, please check your scheduler tasks and edit the STOP record number where needed, as the upgrade does not automatically update existing tasks. | None | Check your scheduler tasks and edit the STOP record number where needed. |
Known Issues
Please visit the Resolved Issues in Sierra 6.1 solution for information on issues fixed in Sierra 6.1. For a complete list of existing Known Issues from Sierra 2.0 through the present release, see Known Issues for Sierra (2.0-6.0).
Preparing to update your system
System Requirements
Sierra 6.0 will require Red Hat or Centos 7x or higher. During the Prep Phase, the Sierra 6.1 self upgrade checks for the required Operating System and Red Hat Network requirements and will fail if those requirements are not met. Details are contained in the Sierra Self-Upgrade Solution.
Red Hat Network
Access to several repositories and new packages are needed and the upgrade process for Sierra 6.1 will automatically issue Linux package install requests for packages matching the following patterns:
- apr
- apr-devel
- apr-util
- apr-util-devel
- ansible
- curl
- expat
- expat-devel
- expect
- expect-devel
- git
- jq
- json-c-devel
- libcurl-devel
- librabbitmq
- librabbitmq-devel
- libxml2
- libxml2-devel
- makeself
- openssl
- openssl-devel
- p7zip
- pcre
- pcre-devel
- perl-LDAP
- python
- python-jinja2
- python-requests
- python2-pip
- python3-dnf-plugin-versionlock
- python3-jinja2
- python3-pip
- python3-requests
- python36
- rabbitmq-server
- readline
- readline-devel
- stunnel
- tcl
- unzip
- wget
- xorg-x11-fonts-misc
- xorg-x11-server-Xvfb
- xorg-x11-utils
- xz-devel
- yum-plugin-versionlock
- zip
- zlib
- zlib-devel
- epel-release (repo)
- erlang-solutions (repo)
- erlang
- logstash (repo)
- logstash
By issuing these requests automatically during the upgrade, if the system being upgraded to Sierra 6.1 is subscribed to the Red Hat Network (or has otherwise been configured to have online access to a repository of operating system packages) at the time of the Sierra 6.1 upgrade, the package additions for Sierra 6.1 will be made automatically and no action is required on the part of the library even for those libraries ordinarily responsible for operating system updates.
For more information on the Sierra Upgrade External Access, Package, and Maintenance Requirements, please see the Sierra Self-Upgrade Solution.
Operating System
For Sierra systems running Red Hat Enterprise Linux 4, or running a 32 bit version of Red Hat Enterprise Linux 5, it will be necessary to upgrade the operating system to one of the 64 bit Linux versions above to upgrade to Sierra 6.1.
Solaris
For Sierra systems running any version of Solaris as their operating system, it will be necessary to migrate from that SPARC based server running Solaris to a new physical or virtual Intel/AMD server running 64 bit Linux in order to upgrade to Sierra 6.1.
Release Notes
Release notes include software behavior changes introduced in the update (some may have implications for training or data review prior to upgrade), any actions library staff should take prior to or just after updating the system, and notification of new features and other enhancements included in the update.
NOTE: If you are upgrading from a version older than Sierra 5.0, after you restart the upgrade process via Admin Corner to begin the Commit Phase, you will see a new prompt before you reboot the server into maintenance mode. The prompt is for a new passkey that you can obtain from CSDirect (https://csdirect.iii.com/custconv-aws) using your login credentials. This will allow for all future software upgrades to use signed URLs for all software downloads. Please refer to page 15 in the Sierra Self-Upgrade Solution.
NOTE: If you are upgrading from a version older than Sierra 5.0, after the Sierra 6.1 conversion is complete, a background task is immediately started to recalculate bibliographic record scopes. This is to correct previous scoping changes made in Sierra 4.0 that caused some items to not be properly ordered in display or included in explicit scoped searches. This background task should be completed within a few hours even for the largest databases and should not impact your system. If you are upgrading from Sierra 5.0-6.0 to Sierra 6.1, this task was run as part of a previous conversion.
Sierra customers who use INN-Reach will not be able to upgrade to Sierra 6.1 at this time if the INN-Reach central server is not on Resource Sharing 3.1 or higher which includes the development to support the expanded codes feature of Sierra 4.0. The Sierra 6.1 upgrade will produce an error in the Prep Phase if the INN-Reach central server you are partnered with is not running Resource Sharing 3.1 or higher. Please contact Customer Support if you receive this error or have any questions.
If you have Encore, we highly recommend that you upgrade your Encore to Encore 6.1 soon after installing Sierra 6.1 to keep both Sierra and Encore up to date on the latest and aligning software.
For MyLibrary! customers and Sierra API users who also have the Patron Update Web Service, additional configuration may be necessary to enable all functions in MyLibrary! and the Sierra API. Please contact Customer Support if you are having trouble updating patron information using the Sierra API or within MyLibrary!.
If you are upgrading from a version older than Sierra 3.4, the Sierra 6.1 update will enable the 2018 Sierra Fines Paid and Collection Agency feature. This was an optional feature in Sierra 3.4 and Sierra 4.0 and if you answered “no” in either previous update, it will automatically be enabled when you upgrade to Sierra 6.1.
Actions staff must take
This update consists of a Prep and a Commit Phase. The Commit Phase will require approximately 30 minutes to 1 hour of downtime and a reboot of the Sierra servers (application and database). A full backup (both application and DB servers) is required within 24 hours of the Commit Phase. Please review your backup schedule and choose the day/time for the Commit Phase accordingly. Note, if you own an Encore server, it will also be inaccessible during the Commit Phase.
At the end of the Prep Phase, the update process checks for a successfully completed backup within the last 24 hours and will alert you of potential problems. For customers on 5-day backup schedules, this may indicate that the Prep Phase ran on a day outside the normally scheduled backup. This same check is also performed at the beginning of the Commit Phase. You will not be able to proceed with the Commit Phase until a successful backup is verified.
Innovative customers can request the update via the "Updating your System" section below. Please use the same request form if your library is running a pre-2.0 Sierra version. You can check your version of Sierra by selecting 'About' after clicking 'Help' in the client menu.
Some libraries have reported that they were unable to launch the Sierra Desktop Application (SDA) after upgrading to Sierra 2.0 SP2 and SP3. This might also be the case with Sierra 6.1 if you are upgrading from an older release (Sierra 2.0 SP1 or older). To avoid this problem, you should either launch the SDA using an icon, or use the "noWebStart" method of accessing Sierra. Add "noWebStart" to the URL used to launch the SDA on each affected workstation (Windows or MAC):http://[APP_SERVER_URL]/sierra/desktop/noWebStart
If the workstation launching the SDA is using "noWebStart" for the first time, the client will be downloaded and installed at that time. A workstation will only need to download the client the first time that "noWebStart" is used.
Libraries that installed Sierra in November 2012 or later had the "noWebStart" method of access set as the system default during installation. It is unlikely that these libraries will experience a problem. If you are not sure what setting is in place at your library, contact Customer Support. The easiest way to determine if there will be a problem on an individual workstation is to look at the contents of the Sierra Desktop Application folder. If the iiirunner.exe file is not present, you should reinstall the SDA using the "noWebStart" method mentioned above.
Updating Your System
If you are a Hosted Sierra system or a Combo (single server) Sierra Training system, please schedule the update with Support. Submit the Sierra Upgrade Request form.
For libraries running Sierra 2.0 SP2 or newer, you now have the ability to self upgrade via the Admin App. Please visit the Sierra Self-Upgrade Solution.