Sierra 6.2 Release Notes

Sierra 6.2 went into general release on June 11, 2024.   We released a Sierra 6.2 Maintenance Release on August 5, 2024. 

This maintenance update version of Sierra 6.2 will display in the Help | About section of the SDA as Software Release: Sierra 6.2.0_12.  The version of Sierra 6.2 released on June 11 will display in the Help | About section of the SDA as Software Release: Sierra 6.2.0_8. 

Any library, running Sierra 6.1 or older, that preps for update to Sierra 6.2 after August 5, 2024, noon PDT will receive version Sierra 6.2.0_12.  Libraries running Sierra 6.2.0_8 that want the fixes included in Sierra 6.2.0_12 can update to that version by choosing to update (again) to Sierra 6.2.

For further information about what fixes are included in Sierra 6.2.0_12, see Resolved Issues in Sierra 6.2.

A new SMS feature is also included in 6.2.0_12 which is listed in the feature list below.

Batch cancel order records

Libraries want the ability to batch cancel orders to simplify workflows when mistakes are made or at the end of the fiscal period.

A new Batch Cancel Orders function has been added to the Acquisitions Workflows in Sierra.

• A new permission – 147 (Batch cancel orders) – has been added and must be enabled to use this feature. 
• The permission works in combination with permissions 148 (Claim/cancel orders) and 79 (Cancel upon vendor notification).
• A staff member will need permission 178 to post the transactions to complete the cancellation process.
• Batch cancellation works from a review file of the orders to be cancelled. Sierra ignores whether the orders in the review file are "claimable" or not. 
• The feature can be used with both monographic and serial orders.
• Orders can be cancelled with or without cancellation letters to vendors.
• A summary screen is displayed to show the status of the orders being cancelled.
• The cancellations must be posted to update the encumbrances and order balances.

Place holds on multiple item or volume records on one bib with a single action

Library staff members can select multiple item (i) records or multiple volume (j) records on a bibliographic record and place holds all at once.

• A library staff member must have permission 45 (Holds Management) to use this feature.
• The same patron, pickup location, limit to location, not wanted before date, not wanted after date, and hold note will be used for all holds placed with the same action.
• If an override is required to place a hold, the override shall allow all the holds to be placed.
  • If multiple override conditions exist, the staff user will need to override each condition separately.
  • Once overridden, the staff user will not need to override the same condition for additional holds.
• A pop-up screen will confirm the number of holds placed for the user and list any errors in placing holds.

None

Scope maintenance

Library staff members now have the ability to administer location-based scopes through a new Scoping Rules function in the Sierra client.

Using this function, users will be able to:

• view a list of scoping rules defined on their system
• view the list of location(s) assigned to a location-based scoping rule
• edit the list of location(s) assigned to a location-based scoping rule

To maintain scope rules, users must have permission 13 (Maintain scopemenu/Scope authorities).

One scoping rule can be edited at a time. Once the changes are saved, the scope will be reindexed automatically. 

The state of the scope while changes are being made can be monitored through the history tab.

BCODE-based scope rules can only be updated by Innovative staff.

Manage macros in the Admin App

This enhancement provides separate fields in the Admin App to define macros for the SDA and Sierra Web. When the library upgrades to Sierra 6.2+, existing macros are saved in the SDA fields. The Sierra Web macro fields are empty except for the RESERVED fields. Macros can be updated through either the Admin App or the Sierra client.

"Verify Heading" in Item Records

"Verify Heading" functionality has been re-enabled for use with item records. This allows library staff to use it on non-headings fields in item records to verify the uniqueness of call numbers, running numbers, and similar fields. "Verify Heading" can be accessed from the Tools menu or by using the Ctrl-G shortcut keys.

Logout button on Web Management Reports

When staff users log in to Web Management Reports using their SAML credentials, a new logout button / link appears in the user interface to give the user an option to logout when they are done. Staff who login to Web Management Reports using their Sierra login can logout of the user interface simply by closing Web Management Reports.

None

None

"MARC" option in authorities APIs

In the Sierra API for authority records, an API user can specify "marc" in the fields to return, and the response will include all MARC data for the record. This feature works with the following API endpoints:

• GET /v6/authorities/
• GET /v6/authorities/{id}

None

Patron validation lockout message in Sierra API

A new patron validation message indicates when a patron has been locked out after five unsuccessful attempts to login. The lockout expires after one minute.

Sierra SMS

This enhancement allows libraries to send SMS notices to patrons for overdue notices, hold pickup notices, and hold cancellation notices. SMS notices require that the library subscribe to the Sierra SMS service and patrons must opt-in to receive SMS messages.

This is a new Sierra SMS service, separate from the existing SMS Alerts. The SMS Alerts product is unchanged.

This enhancement is available in the Sierra 6.2 maintenance release (6.2.0_12).

The Sierra SMS service requires a separate subscription. Contact your account manager for more information. Separate fees will apply.

Libraries using the Sierra SMS service with Sierra 6.2 must also be sending supported SMS notice types through LX Starter.

Java heap setting for the SDA

MacOS Sonoma

The SDA has been certified to run on MacOS Sonoma.

PostgreSQL 15

The Sierra database software was upgraded to PostgreSQL 15.

Minimum OS server requirements

Version 7 is no longer supported in Sierra 6.2. 

Your servers will need to be on Oracle Linux 8 or RHEL 8 prior to your Sierra 6.2 upgrade