281 results found
-
Ability to send checkout receipts
It would be helpful if LX Starter allowed for patrons to receive checkout receipts via email. Sierra currently supports customizable checkout receipt emails using Due Slip print templates, but these are difficult to work with.
57 votes -
Multiple Notice Preferences
Allow patrons to choose one or more notice preferences. A patron would receive the same notice through any and all channels they want, allowing the library to better serve a variety of needs and lifestyles.
28 votes -
Add Patron Type Category Grouping to the New Patron Checkout Limits Table
With the new Patron Checkout Limits table, we have lost the ability to group patron types (ptypes) into a category when configuring checkout limits that also use criteria such as Library Location or Item Location.
Currently, a separate row must be created for every individual ptype, which significantly increases setup and maintenance effort. In environments with many patron types that share the same checkout limits, this results in a large number of duplicate entries.
We would like the ability to define and use Patron Type Categories/Groups within the new Patron Checkout Limits table, similar to the functionality available in previous…
23 votes -
Allow users to freeze a hold even when an available item could be used to fill that hold.
If a library's circulation or OPAC rules allow a customer to place a bib or item hold, the customer should also be able to freeze that hold at any time. This functionality is available in Polaris, but not Sierra.
Currently, customers cannot freeze a bib-level hold if there is an available item that could fill the request. This prevents customers from managing their holds the way they want. In many cases, they do not know an appropriate "Not Needed Before" date, but they do know that they are not ready to receive the item immediately.
Allowing holds to be frozen…
19 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…
17 votes -
Re-Page Item Level Holds
Our library would like to have pages for item-level holds repeat until they are filled. Currently, the only way to achieve this is by checking the "Do Not Clear" checkbox when running the item paging list each day. However, staff have to remember to toggle this setting every time they run the list, and if they forget, all previous pages will be lost and can't be restored the next time they run the list.
We'd like a way to have item pages persist by default.
14 votes -
Days Closed Table - Enter Date Range for extended closures
Make the Days closed table able to have a range of days. When we close a branch for maintenance we have to put in each day, it would be great to be able to put in a location code and then something like 5/1 - 5/25 or comma entries like the loan rule determiner table.
21 votes -
PIN limitations in Sierra: PIN_ALPHA_NUM should accept special characters
PINALPHANUM does not accept special characters.
If Vega Discover continues to be limited by wwwoptions for PIN creation, this option should accept special characters.
PIN Best Practice: The strongest defense combines a long length (12+ characters) with a true random mix of letters, numbers, and symbols.
Length vs. Complexity: Recent security guidelines emphasize that making a password longer (like using a multi-word passphrase) is often more effective than adding a single symbol to a short word. That said, library users do use special characters and want them included in their library PIN.
Adding symbols increases the character set…
13 votes -
Add ability to group itypes into categories in the new patron checkout limit table
With the new patron checkout limit table, we lost the ability to group itypes into a category if we want to use the other limits like library location. We need to be able to either group itypes in the new patron checkout limit table, or use a combination of the old table and the new. We really need the new library location limiter in the new table so that our ptype 30 can only checkout items at our offsite kiosk and no other library, but we now lose the ability to still group our itypes into categories. Our itypes are…
29 votes -
Create Lists: Prevent the hopping or jumping of lists after a sort is applied
Currently, when a staffer goes into Create Lists and sorts the lists using one of the column headers, while scrolling down to locate the appropriate list, Sierra jumps or hops upward thereby losing the staffers place in Create Lists. This idea is to prevent that from happening and to make the default or custom sort in Create Lists stick. This would save staff time and reduce errors as well.
25 votes -
Create expanded RestAPI endpoint for patrons/validate that exposes a limited set of patron fields
We have many vendors who have a need to check data in a few patron record fields as part of their authentication process. Fields such a ptype, home library, the expiration date, etc...are necessary to confirm that a patron is affiliated with the institution subscribing to that vendor's resource and that their card remains in good standing are necessary to provide. However, doing so currently requires providing the patron read permission, which also exposes a variety of additional sensitive data that these vendors should not have access to for their needs (PII, checkouts, fines, reading history, etc.)
The lesser patron…
11 votes -
Update Print Template Assignment Methodology
After spending over an hour adding new print templates to every login for a new library, I am once again reminded of the inefficiency of the current methodology for assigning print templates to logins.
Idea: Print Templates can be assigned like Permissions for Sierra. They would have their own sidebar, and logins could be added to each print template. That way, it only takes a couple of clicks to add print templates in mass to several logins, rather than clicking into the login, then settings, then print templates, then scrolling to find each print template and set the prompt. This…
26 votes -
Provide full Branches table and full Location code list via Sierra REST API
Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.
Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the…
43 votes -
Text/SMS Notice Preference
Please integrate text messaging/SMS as a notice delivery method just like print, phone, and email. Some patrons want texts and no other method. Even if patrons must complete a step outside Sierra, staff should be able to see and choose text as a preference. This would make things more consistent and easy for both patrons and frontline staff.
We had planned to switch to Vega Interact SMS but discovered that it is intrinsically linked to email notices, limiting its ability. We would love to have SMS as a real notice option in Sierra.
13 votes -
Add index selector and pre-search limits to Check Out (Circulation Desk) Function
This idea is expanding on one originally proposed here by Catherine Kelso (https://ideas.iii.com/forums/951745/suggestions/47046682).
It would be helpful to more easily search on patron record indexes besides barcode when you need to (name, record number, e-mail, etc...) and for those sorts of searches it would be helpful to limit the search preemptively as you can in other search functions throughout Sierra. Say you want to search for the "Smith, John" with a teen ptype and a home library of anytown branch.
The current default search of entering a barcode should remain, it should just be simple to toggle to…
9 votes -
Generate Statement of Charges directly within patron record
It would be very helpful to be able to print or email a Statement of Charges directly from a patron record (and have it formatted for 8-1/2 x 11 paper and mail-ready).
Customers want a list of what they have out, and it looks very bad for the library to hand a customer a very, very long receipt when we are trying to save paper across the system.
10 votes -
Track User, Time, and Process for Deleted Records
Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.
Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the…
14 votes -
check in claimed returned workflow - item location should reflect where item was made claimed returned
For libraries with floating collections, the branch where an item is marked Claimed Returned may not be reflected in the item record. This is because none of the three Claimed Returned options update the item's location.
Example
An item is checked out from Location A.
The patron reports returning it to Location B, and staff mark it Claimed Returned at Location B.
The item record still shows Location A.When marking an item Claimed Returned, staff have three options:
1.Add a Claimed Returned note to both the item and patron records.
2.Remove the checkout link between the patron and the…8 votes -
Make Additional PCODEs Available
Libraries are increasingly looking at ways to gather metrics on patrons without identifying them. Data on age, gender, race, or all manner of characteristics might be collected, depending on the library.
I'd like to see Sierra be more accommodating in what it can collect & store on a patron's record, with the introduction of one or more additional PCODEs that can be used to store a significant amount of fixed field codes.
For example, we partner with schools in our service area & offer not only educator cards, but do an upload of student data. Having schools within our service…
10 votes -
Overlay matching should evaluate all repeatable subfields (e.g., every $a in the 019), not just the first occurrence
When a load table's overlay match point targets a repeatable field such as the 019 (OCLC number cross-reference), the load process only compares the first subfield occurrence against Sierra's index. Although Sierra correctly indexes every $a in the 019 individually, the overlay-match routine stops after the first $a. Any additional OCLC numbers stored in the second, third, or subsequent $a subfields are ignored when determining whether an incoming record should overlay an existing one.
As a result, records that should match an existing bib overlay as new duplicates instead, because the matching value lives in a $a other than the…
9 votes
- Don't see your idea?