265 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 votesThe product team will review this idea for consideration for a future release.
-
Create a different template for repeat bills
Add the ability to create a template specifically for repeated bills. This would allow us to send a different message for a reminder bill than what we sent in the original bill. This is would be similar to how we are able to create different templates for 1st, 2nd, 3rd etc Overdue Notices.
18 votes -
Create a GET API endpoint for circulation transactions
This idea came from a discussion at the IUG2025 Sierra Reporting Forum.
It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to…
12 votesThe product team will review this idea for consideration for a future release.
-
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…
17 votesThe product team will review this idea for consideration for a future release.
-
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…
31 votesThe product team will review this idea for consideration for a future release.
-
Add a Stat Group When Creating a Patron API Key for Vendors
This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or…
8 votesThe product team will review this idea for consideration for a future release.
-
Ability to view history for item and volume records.
It would be helpful for us to have access to the history of item and volume records, including details of their creation and any subsequent edits. This would improve our ability to track changes and ensure accountability if any issues come up.
13 votesThe product team will review this idea for consideration for a future release.
-
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…
22 votesThe product team will review this idea for consideration for a future release.
-
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:…
12 votesThe product team will review this idea for consideration for a future release.
-
Include perioidical issue information in overdue notices
We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?
11 votesThe product team will review this idea for consideration for a future release.
-
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.
20 votesThe product team will review this idea for consideration for a future release.
-
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.
14 votesThe product team will review this idea for consideration for a future release.
-
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…
13 votesThe product team will review this idea for consideration for a future release.
-
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.
20 votesThe product team will review this idea for consideration for a future release.
-
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…
24 votesThe product team will review this idea for consideration for a future release.
-
Automatic SSL Certificate Renewal
Keeping our systems secure with SSL certificates is essential. Certificates need to be renewed and there is a service commitment to handle this process. But there is a better way. SSL providers can be setup to automatically renew and deliver an updated SSL certificate to our systems when their expiration time approaches.
This idea is for Innovative to support software-only site with setting up an automatic SSL renewal process thereby keeping our systems safe from expiring certificates and making the process worry-free.
8 votesThe product team will review this idea for consideration for a future release.
-
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…
13 votesThe product team will review this idea for consideration for a future release.
-
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 format30 votesThe product team will review this idea for consideration for a future release.
-
Passing the UPC Code
When an item lacks an ISBN in the 020 field (DVDs and CDs only generally have UPCs in the 024 field) the cover image is very much hit or miss. Syndetics has been contacted, however, it appears that Sierra needs to "pass the UPC code” in order for this to work. This addition would be helpful.
9 votesThe product team will review this idea for consideration for a future release.
-
Send To - Delete Records
Sierra 6.3 saw the introduction of a feature that allows users to select a file in Create Lists mode & then, from the Tools - Send To menu, direct that file to either Global or Rapid Update, eliminating the need to navigate to those functions & then find & select that file.
I would like to see the same introduced, but for the Delete Records function.
Doing so would similarly streamline the workflow when doing record purges in Sierra.
7 votesThis enhancement is planned for Sierra 6.5.
- Don't see your idea?