Sierra 5.6 Release Notes

GET /v6/patrons/holds returns confusing "ready for pickup" status descriptions

Sierra API's hold status descriptions include "bib hold ready for pickup" or "item hold ready for pickup," which are not meaningful to users.  All ready-for-pickup hold statuses will be standardized to "Requested item ready for pickup."

GET /bibs/ includes suppressed items in "copies"

Sierra API includes suppressed items in the "copies" count for the GET /bibs/ endpoint.  This can result in a discrepancy between the apparent item count and the number of attached items actually returned.

Hold attempt on non-holdable item results in incorrect success status

When a client attempts to place an item-level hold on a non-holdable item, the hold is correctly not placed, but Sierra API returns a successful 204 response code.

REST API slow to return results when canFreeze field is requested

The REST API is very slow to return a list of patron holds when canFreeze field is included in the GET request. The same list of patron holds is returned in a timely manner when the canFreeze field is not included in the GET request.

GET /v6/patrons/holds returns confusing "in transit to pickup location" status descriptions

When a hold is in transit to the pickup location, Sierra API's hold status description is "bib, item, or volume in transit to pickup location," which is not meaningful to users.  The in-transit status description will be updated to "Requested item in transit to pickup location."

POST /v6/bibs/ does not set CAT DATE

When POST /v6/bibs/ creates or updates a bib record, Sierra API does not set the record's CAT DATE to the catalogDate provided in the request data.

Apereo CAS login screen for SAML setup does not show on screen width 576-767 pixels

The elements on the CAS Apereo login page disappear when accessing the page on a device with a screen width between 576 and 767 pixels.

Data Exchange displays wrong file name for loading errors

When errors occur in loading a file, Data Exchange displays a warning message "Error trying to load X records due to bad data. Details in (filename)."  The file name cited is not the correct error log for the current load.

Curly braces in optional fields on Collection Agency reports

When diacritic characters exist in the optional variable fields on Collection Agency reports (patron address, for example), the report contains curly-brace codes instead of the correct characters.  Diacritics print correctly in patron name, which is included in hard-coded fields.

Cannot delete bib record with backslash (\) in an indexed field

When a bib record contains a backslash (\) in an indexed field, for example a call number or subject heading, Sierra is unable to delete the record.

Incorrect search results for 箚 {u7B9A}

In the SDA, searching for 箚 {u7B9A} in the title or author index finds no records. Searching for 箚 {u7B9A} as keyword finds records with 札 {u672D} instead.

Coverage load does not create ERM links when resource name contains a hyphen between spaces

If the resource name or id in the resource record contains a hyphen between spaces (" - "), coverage load does not create the ERM link field in the loaded checkin records.

Sierra 5.4 contains a previous fix related to hyphens, SIERRA-33936.

ERM: _today-70y in Coverage Spreadsheet Conversion Rules

In Coverage Spreadsheet Conversion Rules file, _today-70y should calculate the date in the coverage data load by subtracting 70 years from today's date.  Instead, Sierra adds 70 years to today's date.

Keyword searches limited by year do not retrieve results published in that year

When staff perform a keyword search and then use Tools | Limit to enter Publisher Year, materials published in that year range are not found.

Long title or author searches in non-Roman alphabets do not return expected results

Title or author search strings longer than 48 characters in non-Roman alphabets do not return expected results.  The search string must be shortened to 48 characters or fewer in order to return results.

This issue primarily affects non-Roman alphabets such as Greek, Georgian, and Cyrillic.

Session Statistics omit records loaded or overlaid via Data Exchange

When staff load or overlay records in Data Exchange, those created or updated records are not reflected in Session Statistics.

Limit word in French subject is not working

In the SDA,  the limit in subject search didn’t work in French subject (pomme) but worked in English subject (apple) when we searching the location first and then limit to the subject search.

Bibliographic record leader byte 09 defaults to 'blank' (MARC-8) rather than 'a' (Unicode) during record creation

Sierra uses Unicode for character encoding. When creating new bibliographic records, Sierra automatically populates byte 9 of the leader, CHAR ENC, with the value of 'blank' which means MARC-8 rather than 'a' which means Unicode.

Compact Browse: Search results display incorrectly for some titles; showing the indexed entry and not the diacritics

When performing a title search, some results display as the indexed line (the internal codes used for indexing)

Loading non-sorting characters in UNIMARC UTF-8

When loading records in UNIMARC UTF-8, Sierra loads non-sorting characters incorrectly (apostrophes and "@", for example).

Branch Addresses truncates email address for non-English logins

When staff open the Branch Addresses table using a non-English login, Sierra displays only the last 23 characters of the E-mail Source field.

Cannot send hold cancellation notices

When preparing hold cancellation notices, if the job is limited to a Locations Served or location code, and the cancellation notices queue includes a bib hold, Sierra gives an error "The server is not responding" and closes.  Auto notices also will fail to send the notice job.

Fails to register barcode scanner's carriage return in Search/Holds box after another index is searched

Search/Holds and Catalog search function are not registering the barcode scanner's carriage return (confirmed the scanner uses CR) on random scans, but particularly when the user switches between searching a different index (e.g., title, author, etc.) and the barcode index. As a result, the search is not automatically performed immediately upon scan; the user must initiate the search manually instead. Note: This barcode scanning issue is not replicated in other Circulation functions (e.g., Check-out and Check-in).

Time to Holdshelf does not delay pickup notices for ILL

When Time to Holdshelf is configured to delay pickup notices for an ILL location, Sierra does not delay pickup notices for ILL virtual items with that location.

With context user, on-the-fly permissions not reset after leaving mode

When a user without permission to enter a mode attempts to move to that mode, Sierra prompts for additional permissions.  When Sierra has been launched with a context user, providing those permissions sets the new permissions permanently for the session, and they are not cleared until the user clears them manually (Admin | Clear Permissions).  This behavior has been reported or reproduced with multiple modes requiring standard or optional permissions.

On-the-fly permission for tabs in Check Out (Circulation Desk) allows repeated access

If a user without permission to view patron tabs in Check Out (Circulation Desk) attempts to view a tab and permissions are entered on-the-fly, the un-permissioned user can view the same type of tab again without supplying permissions.

That is, if a user without permission attempts to access the Checked-Out Items tab and enters on-the-fly permissions, that un-permissioned user can close the patron, open another, click on the Checked-Out Items tab, Cancel the permissions popup, and stay in the Checked-Out Items tab and view any information there.

Manage Holds: different date format when printing or exporting

In Manage Holds, dates display on-screen in the system's configured date format (e.g. "2021-12-22") but appear incorrectly in long format when the report is printed or exported ("Wed Dec 22 09:14:44 CST 2021").

Unable to extend pickup date when pickup locations are limited to the Hold Pickup Locations table

When a staff user has "Limit pickup locations to those in the Hold Pickup Locations Table" enabled, that user is unable to extend hold pickup dates for holds whose pickup location is not first in its entry in the Hold Pickup Locations table.  Sierra displays a message that the item is "already on the holdshelf or in transit."

Note: At libraries with Title Priority Paging, pickup location limiting is automatically enabled and cannot be disabled.

Holds clear from holdshelf one day early after pickup date modified in Manage Holds

After staff modify hold pickup dates in Manage Holds, the Clear Holdshelf report clears the hold on the pickup date rather than on the day after the pickup date.  (For example, if the modified pickup date is Feb 17, the item should not appear on the Clear Holdshelf report until Feb 18 but appears on Feb 17.)

Notice History records "0" for bills via email with Print Templates

When a library formats Bill notices with Print Templates, Notice History records an entry with "0" count for any bills sent via email.

Some bills not sent, at libraries with options grouped "Minimum charge for fines notice"

When the Circulation Option "Fines/Bills: Minimum charge for fines notice to print" is options grouped, so that different branches have lower or higher minimums, some bills may not be printed for the branches with the lower settings, depending on the order in which notices are sent.

Patron names with diacritics not sorted in indexed alphabetical order in Clear Holdshelf

Patron names with diacritics are not sorted alphabetically in indexed order in the Clear Holdshelf function. The system sorts a-z but doesn't include diacritics with in that search (e.g. á is not listed after a as expected, instead it appears after z).

Interface issues in Notices with Manual or Save Parameters setting

If Sierra is configured for "Manual" or "Save Parameters" notices settings, Sierra does not correctly display Notices mode and becomes unresponsive.

The issue can be avoided by asking Innovative to enable the Auto Notices feature.  (No notice jobs will run automatically unless specifically configured.)

Manage Holds: Location area labels cut off with 14+ font size

When a Sierra staff login is configured with font size 14 or larger, the text of area labels "Pickup Location:" and "Item Location:" is cut off at the bottom.

Arabic titles are truncated in patron information tab title columns

Arabic titles are truncated in patron information tab title columns e.g. Check Out tab, Holds tab etc.
https://documentation.iii.com/sierrahelp/Content/sril/sril_disp_patrontabs.html

Chinese language PTYPE field cut short in SDA and Sierra Web

When Patron Type has Chinese text and the total number of characters is greater than 11 then it will be truncated in the Bib-Level Holds and Item-Level Holds tabs.

Item_Auto_Renewal_Status does not translate "RENEWED"

On courtesy notices where an item was auto renewed, the Item_Auto_Renewal_Status field always prints "RENEWED" in English even when the notice's language is not English.

No record written to Fines Paid when a billed item is renewed and the bill automatically adjusts to zero

When staff renew a billed item, and the automatically adjusted charge is zero, no entry is written to Fines Paid.  Sierra should record the removed replacement charge to Fines Paid with a payment status of "no payment," to indicate that the item had previously been billed but that the bill has been automatically adjusted.  (If the charge adjusts to an amount other than zero, Sierra does write correctly to Fines Paid.)

Bibs with expanded Material Type do not appear in High Demand Holds

Bib records with 2- or 3-character Material Type codes do not appear in the High Demand Holds report.

Cannot sort Collection Agency table by Total Item Cost or Barcode

In Collection Agency mode, clicking on the Total Item Cost header does not sort the table.  A triangle appears as if the column is sorted, but the order of rows does not change.  The Barcode column also does not reorder rows and does not display the triangle in the header.

Call number indexed using normalization rule 22 cannot be searched in Create Lists if there is a space directly before and after decimal

A call number field with a space before and after the decimal is not searchable in Create Lists, when it's indexed with a normalization rule 22.

Unable to input Turkish character İ in Create Lists

Users are unable to input the Turkish character İ (unicode u0130) in Create Lists.  This also prevents searching for the character.

EPQ with multiple terms and stored record type different from that of searched field

A Create Lists search fails when applying multiple terms to one field (e.g. LOCATION equal to x or equal to y) in the Enhanced query editor and storing a record type that is different from the record type of the searched field.

Example: storing item records, BIBLIOGRAPHIC LOCATION equal to main or equal to south

The issue affects some fields but not others.  For example, bib fields LOCATION, PUBLISH YEAR, TITLE, and CALL # are affected, but not LANGUAGE, COUNTRY, or MAT TYPE.

Exporting either patron telephone field tag outputs both

In Create Lists, if staff select either TELEPHONE (t) or TELEPHONE2 (p) field for export from patron records, Sierra includes both fields in the exported file.

Item note (x) 32 characters or longer stops INN-Reach

If a patron with INN-Reach transactions to process has a checked-out item with a note (x) field that is 32 characters or longer, INN-Reach transaction processing stops.  Shortening the note field allows transaction processing to resume.

OCLC ILL Request Transfer: Q3 fields not transferred to OCLC

When acquiring an ILL request via OCLC, the data entered in "Q3" fields should be transferred to OCLC in the "Publisher" field.

OCLC ILL Request Transfer: patron fields not transferred to OCLC

When acquiring an ILL request via OCLC, the patron's PTYPE and address should be transferred.

Note: If the patron record contains both a physical address and an email address, OCLC will display only the physical address.  This is an issue on the OCLC side, and they have not indicated a timeframe for a fix.

Archiving checkin cards does not remove the card from the current checkin record

Archiving checkin cards should create a new checkin record, move the full checkin card to the newly-created record, and create a new, empty checkin card on the original checkin record.  The new checkin record is being created with the correct cards/boxes, but the cards/boxes are not removed from the original checkin record.

Checkin Item Info, Volume Subfield (MARC 876 $3) doesn't display in SDA

On checkin/holdings records, ITEM INFO volume subfield (MARC 876 $3) does not display in Record Summary in Sierra Desktop Application.

Printing claim using print template where enumeration or chronology is blank results in null value for unrelated columns

When enumeration or chronology data is not filled in for a serial issue that has been claimed, printing the claim using a print template will populate the following columns as "null": Issue, Note, Claim.

Sierra Web: Coverage Edit "Unable to connect to database server" with SDA in secure tunnel

When the SSL tunnel for SDA connectivity is enabled, Coverage Edit gives an "Unable to connect to database server" error in Sierra Web.

Sierra Web inaccessible with White Screen Problem

Seemingly at random Sierra Web will freeze up for the users currently in the system and any users who attempt to navigate to the Sierra Web page and click on the Connect to Sierra Service button will be greeted with the following error: White screen problem. Render doesn't finished, html code is empty: try to increase invoke and wait timeout

Create Lists: Cannot view Saved Searches in Sierra Web when default view is Enhanced

When "Set view to Classic" is unchecked, making Enhanced the default view for Create Lists queries, the Saved Searches tab is blank in Sierra Web.

SIERRA-35611

Cannot set patron EXP DATE to blank in Sierra Web Rapid Update

When attempting to Rapid Update patron EXP DATE to a blank value in Sierra Web, EXP DATE fields are instead set to 2030-08-02.  Rapid Update in the SDA correctly blanks EXP DATE.

Unable to access video/ebook content in O'Reilly database

Patrons are unable to access video or e-book content in O'Reilly database through WAM. 

Libraries with IPA cannot access Pathfinder Pro or WebBridge LR in the Admin App 

Libraries with Innovative Phone Alerts are unable to access the Pathfinder Pro or WebBridge LR areas in the Admin Application.

Clear Search History does not clear the last search

When a patron uses Clear Search History, the most recent search remains in the search history drop-down menu

WebPAC pinreset form susceptible to host header injection

An attacker can bruteforce Sierra's pinreset fields, tamper with the POST request for password reset and send mass email to all Sierra users with a link to a malicious site.

Search limited to Words in Author/Title/Subject fails to return results for Chinese characters

When Chinese characters are used for an author, title, or subject search, limiting to words in one of those fields (e.g. words in author or subject for a title search) fails to return results

Keyword indexing incorrect or out-of-date

When a bib record's fixed fields change, the record's indexing is not always updated to reflect the new data, resulting in incorrect keyword search results.  This is most frequently reported with suppression and location fields.

Patron can overpay via web ecommerce if fines are reduced while the patron is paying

If a patron starts to pay their fines through WebPAC or Encore, and the patron's fines are reduced (e.g. by manual adjustment or by returning a billed item) before the payment is finished, the patron will pay the original amount, even though the patron now owes less.  Fines Paid will only reflect the fines that remained on the patron's record at the moment the payment was finalized.

Record browse for a title index search does not sort by call number

In WebPAC if a user searches the title index, selects a title, and changes the sort to Call Number, the order of results in the record browse display does not change.