259 results found
-
Include Individual Item Costs in Overdue Notices
Make it an option to also include the item cost in the overdue notice as well (incentive to return!).
In our date due slips (JasperSoft) we include the cost of each item and a total cost to show what the patron saved by using the library vs. buying.
54 votes -
Create Lists - Saved Searches - Ability to Rename, Show Creator, Last Used
We repeatedly run up against our limit of saved searches in Create Lists. There are probably saved queries created long ago that no one is using/needs. I was hoping to assign staff to review the queries and put their initials in the saved search name, but when you go to Edit, you can only edit the query, not the query name (like you can a review file). Ideally it would work like the review files themselves, when you can see who last ran the list (initials, date and time). And perhaps apply the "Own" option. This would really help to…
26 votes -
Allow holds on bibs when holdable items are on order
We have a non-holdable lucky day collection whose items are on the same bib as our regular, holdable copies of those titles. Sierra allows patrons to place holds on titles that are on order, but sometimes the non-holdable copies are the first to arrive -- at which point, Sierra sees that all items on the record are non-holdable, and stops allowing holds until the first holdable copies come in.
Innovative recommended splitting nonholdable items onto a separate bib record, which seems liable to clutter up the catalog; moreover, some of these items are likely to be moved into our regular…
19 votes -
2038 issue
We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.
18 votes -
Add ability to suppress a subfield in the 1xx
Add the ability to suppress subfield 1 in the 1xx field so it will not show in Sierra. This way it can be unsuppressed when the library starts using linked data.
13 votes -
Offer the ability to retain a patron's receipt preference at checkout
At checkout, Circulation Staff must ask patrons at the end of each checkout if they want a printed receipt, email receipt, both, or none, or place a pop-up message on their account. It would be great if there were a way to retain each patron's receipt preference so that upon closing out the patron's record, the preferred receipt would be sent, print, both, or no receipt would be given.
17 votes -
Lock Commands in Rapid Update
When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands…
10 votes -
Make OpenAPI definition document (previously known as Swagger specification) available for Sierra's APIs
There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.
The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.
For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.jsonBenefits of an OpenAPI Definition Document:
…* Standardization: Provides a consistent format28 votes -
Time to Holdshelf Delay Period Not Reflected in SDA Holds Status
The Time to Holdshelf feature in Sierra is useful in keeping patrons from showing up too early to pick up their holds. As seen in the attachment "Discovery Layer View" – which in our case happens to be BiblioCore – the availability status correctly reflects that the recently checked-in item "Easter Mice!" is not ready for pickup because the item is en route to the pickup location (which in this case is a set of freestanding pickup lockers in a remote area of the county).
However, the holds status as displayed in the SDA incorrectly reports the item as being…
20 votes -
Improve/Standardize Information Available When Viewing Holds
Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).
Right now, it is not consistent how holds information is displayed.
If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with…
28 votes -
System Option to Disable Transit Slip Printing by Default
In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.
Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of…
11 votes -
Add Invoice Number to Invoice Summary
The Invoice Summary that is sent after posting invoices only lists the voucher number. Our Finance department has to go through the Invoice Register and match the invoice number to the voucher number to know what invoices should be paid. This is very time consuming, and susceptible to human error. Please consider adding the invoice number to the Invoice Summary.
14 votes -
Paging Queue should recognize changes to the Not Wanted Before Date in Hold record
Sierra queues the hold for paging at the time the hold is placed, based on the data the hold was placed with. If the hold is modified after that (by changing the Not Wanted Before date), those changes don't update the paging queue, and Sierra will continue to page as if the hold had not been modified.
8 votes -
Batch Check-In Should Not Update Circactive Date
Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.
We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.
Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.
This…
7 votes -
Hold Pickup Reminder/Courtesy Notice
Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.
Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want…
20 votes -
Provide indicator/warning when an order record has already been sent to a vendor
In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.
As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2)…
26 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Make it possible to search for records lacking a MARC field in Create Lists
I recently wanted to run a search for all records that matched certain criteria and did not have an 856 field. However, Create Lists does not currently have a "lacks field" option. It would be very helpful to be able to search for records that do not have certain fields.
17 votes -
Add "max number of overdue items" column to patron block table
Many libraries have eliminated fines and they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based on a Library determined number of overdue items. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.
Idea Value: This new setting would provide an incentive for Customers to return their items.
Idea Value: We don't want to restrict the number of items a Customer can sign out, but want to restrict borrowing after a specific number of overdues.
Idea Value:…
3 votes -
Add an Option to restrict Bibliographic Records within the Sierra System ( specific permission)
Problem:
In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:- Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.
Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.
Recommendation:
Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra…
5 votes -
Fix "Tile Vertically" so the bottom of the records don't get hidden behind the taskbar on Windows 11.
In Sierra, on Windows 11, when you click "Tile Vertically" so you can see multiple records at the same time, it makes the windows too long, so that the bottom of the windows get hidden behind the taskbar if it is locked. It does not do this if you maximize a record window, or if you use snap. It only seems to be the "Tile Vertically" function.
We use this function a lot to compare records for deduplication, and it is really annoying to have to manually resize windows so you can see the whole thing.
8 votes
- Don't see your idea?