266 results found
-
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.
26 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:…
25 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.
25 votesThis enhancement is planned for Sierra 6.6.
-
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…
25 votesThe product team will review this idea for consideration for a future release.
-
Allow Pickup Location Changes After Hold Is Activated (with Optional Patron Notification)
In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.
We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.
-Why This Is Needed:
Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is…
24 votes -
New Skins for Sierra
Can we get some new skins to choose from for the SDA/Sierra Web?
There are currently two: Half Dome & Glacier Point.
We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.
Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?
24 votesThe product team will review this idea for consideration for a future release.
-
Staff activity log
We occasionally have issues with staff abusing their ability to waive fines or deleting items inappropriately or accessing patron accounts outside of acceptable library operations. We would like to have a way to view these actions within a log file associated with each Sierra login (or filterable by login) so that these activities could be periodically audited by managerial staff and retroactively be reviewed when inappropriate system activities are believed to have taken place.
24 votes -
Allow users to define icode1 in Sierra
Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.
24 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Improve patron address parser to better map data to the patron_record_address table
Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.
For one common example in our system…
23 votes -
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…
23 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.
23 votes -
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.
23 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…
22 votesThe product team will review this idea for consideration for a future release.
-
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…
21 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.
21 votesThe product team will review this idea for consideration for a future release.
-
Introduce a "CANCEL" Button in the "ITEM ALREADY PAID FOR" Warning Popup
In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding further, returning the user to the search results list. The "CANCEL" option…
21 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Batch/Copy Option for Patron Record Creation
Someone at CHPL is suffering from Polaris envy & suggested Sierra offer a comparable record to copy/duplicate patron records. They're hoping for a way to speed up the record creation process for families of 5 or 6 that visit the library together & all need to register for cards, which is apparently not an uncommon scenario. The ability to quickly replicate certain fields (address, home library, maybe phone, e-mail, etc.) from one record for x more should facilitate that.
21 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Save title and author info in reading history after title is deleted
Customers want to know what titles they've checked out even if the library no longer has it. It would be ideal if Sierra (and subsequent discovery layers can pull the info) could save the title and author in the record metadata so that even if the bib record is deleted, the customer can see it.
21 votes -
Improved loan rules & loan rule determiner documentation
The current documentation on loan rules, loan rule determiner, and float determiner table is very limited, and training on these important functions do not exist within Innovative's training & learning center. More comprehensive documentation with examples would help libraries better manage loan rules, and perhaps simplify how libraries' existing rules are setup.
20 votesThe product team will review this idea for consideration for a future release.
-
Add fund code used to purchase item to item record
I was asked recently to create a list of items added to the database based on a fund code. I don't believe that I can do that in Create Lists. This is because order records and item records have no common field to link them.
I also cannot use Create Lists to pivot item records to their attached order records or vice versa.
We need to be able to do this because 1 bibliographic records may have items attached that were purchased from different funds. Example. 1 Fiction title may have items purchased from an ARP (automatice release program), and…
20 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?