178 results found
-
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.
17 votes -
Add eReceipts as an option in LX Starter.
The only option for eReceipts is plain text. It would be a fantastic feature to customers to be able to build a nice HTML email for them.
5 votes -
notice scheduling
Currently, the notices for Current Checked Out Items allows for daily or weekly scheduling, but it would be handy to have the ability to set this at a longer time frame such as monthly, quarterly or by semester as most of our materials check out for much longer periods of time (16 weeks or longer generally), and some users find the weekly reminders tedious.
Either the option to set the automated notices to a longer time period, or the ability for patrons to choose a longer reminder period (opt in to weekly, monthly, etc notice) would be very helpful.
4 votes -
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.
4 votes -
Disable Reprint bills button In Sierra
We can’t use this button because we don’t use print templates for our bills.
We would prefer them to look pretty with Print Templates instead of the plain text we currently have. To avoid staff confusion, it would be great if this we had the ability to disable/grey out this button.3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Expand to different order statuses for the Sierra REST API
The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".
Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.
5 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Update "last checkin" field even if item wasn't checked out
Update the "last checkin" field every time an item is checked in. Now, when you check in an item, the "last checkin" field is not updated if the item is not checked out. I don't know of any reason to not update it. When I look at an item record, I want to know the last date that the item was seen; this can be useful in tracking down items that seem to be missing, or coming up with a list of items that might be missing.
8 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Order Status rapid update
Rapid or global update to update all Order Status at once.
7 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
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.
-
Reading History via API
At this time it is apparently possible to retrieve the patrons Reading History via REST API sorted by date (oldest first or newest first). The most requested API enhancement request for us is to be able to retrieve the patrons Reading History via REST API sorted by Title. Another enhancement request is to be able to retrieve the patrons Reading History via REST API sorted by Author. This would be useful since users may have hundreds of items in the reading history.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
10 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
NCIP Authentication - Add support for optional blocking
We recently started using NCIP authentication for our new ILL service. We learned after implementation that NCIP login is blocked for any of the reasons in the Patron Block Table. This makes sense when the block is for an expired card, or for fees over the threshold. This makes less sense when they have reached their maximum holds in Sierra.
What we're seeing is that patrons cannot log into the system at all when any of the block parameters are true. We would like to be able to enforce certain blocks but not others for account login.
We can increase…
4 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
More name fields in get patron API
At present, we can only see the full name field in get patron endpoints. For some systems that connect via api, it would be highly beneficial to have other fields available relating to patron information. For example, separated first and last names.
This is due the some systems relying on the information it can read from Sierra and not process further to define a first name.
4 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
New Linked Patron logic : Link a patron record to a second patron with no reciprocal link.
Why is it important to link patrons?
- Without linked patron functionality someone that is authorized to pick up a hold on another account is complicated. This is manually done by staff using patron notes, and the authorized patron signs out the book leaving the original hold on the other patron record.
- Parents visiting the library with children would like to jump to the record of each child rather than using the child’s cards.
Current privacy and circulation workflow issues:
- Someone could link to the child record without authorization. If a patron is sharing their circulation details with someone, they should…
7 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
AI Clean Up Functionality - Sierra
I understand that III is planning to incorporate AI functionality into the Vega platform (newsletter text, website content, etc...). I think it would be really useful to have AI data cleanup functionality developed for Sierra.
I'm not sure exactly what this would look like but here are some potential ways this could improve catalog metadata:
- catalog record cleanup (bad codes, incorrect codes, codes inconsistent with local practices for similar records, etc...)
- patron record cleanup (bad codes, codes inconsistent with similar-type accounts, etc...)
- automatic tagging of demographic (we use one of the patron codes to indicate reciprocal library…9 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Allow SIP2 AF field to offer alerting patrons to pending expiration.
That way other devices such as self checks can show that warning to the patron in the case of them checking out items and having the due date shortened to their expiration date instead of the full borrowing period for the item. If they were alerted they could contact staff to update their account and any item due dates that were shortened to their prior expiration date.
7 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Ability to update inventory date from "checkin no patron" function
We are needing a way to update the inventory date field when an item is checked-in using the "checkin no patron" function.
When an item that is already in "-" available status, and you check-in the item, there is no field in the item record that records the date of this transaction. We are wanting a checkbox on the screen in that function that when checked, will update the item inventory date so that we can then see the last time that item was scanned.
This will help us with our inventory projects, as we do a full scan of…27 votes -
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Sierra should send an email notification when Offline Files are Uploaded
As the system administrator overseeing a 54-member library consortium, managing Offline File Processing is a routine responsibility. However, we often encounter delays in processing files because libraries don't consistently notify us when they upload offline files. This results in files remaining unprocessed until the next library contacts us, potentially causing unnecessary checkout delays. If we process the files too many days after uploading, additional errors may occur, making it challenging to track items adequately.
An email notification for Offline File Processing would ensure timely handling of uploaded files. We could proactively monitor file uploads, swiftly process them, and promptly address…
18 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
- Don't see your idea?