272 results found
-
Extend data retention of accounting transactions in SierraDNA
The accounting transaction tables in SierraDNA allow you to query information you would normally only have access to via a retained posting register. However, it is hardcoded to only retain information for 2 weeks, which isn't enough time to do anything meaningful with that data.
Ideally I'd like to see data for a full fiscal year but if there needs to be a limit for whatever reason, maybe tie it to the related payment history file.
3 votes -
MARC Tags - Exporting
When exporting MARC tags, export should have all the subfields marked. Now that I try to export say 041, I can´t see if the language code is in a, b or d... And this would be important to know as it is not the same to have say |a fin |h eng and |a fin |a eng.
This is a re-share of an expired idea that seemed to garner some attention its first time around.
1 vote -
Improve item title display on patron-facing devices by adjusting SIP2 parameters
Skip certain MARC subfields when preparing data for SIP2 connection.
Specifically:
When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field…1 vote -
Create an API endpoint that delivers language translations to Vega
We maintain English and Te Reo Māori names for library branches and item locations in the Sierra branches table. Making these available through an API would allow Vega to display the correct names automatically, and provide a consistent bilingual experience. This would also remove the need to manage translations separately in Vega Admin.
3 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…
10 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…
7 votes -
Add ability to query empty review files to the reviewFiles API
This idea is a bit of an addendum to Bob Gaydos' idea to create an endpoint that allows writing to review files (https://ideas.iii.com/forums/951745-ils-sierra/suggestions/50308716).
The current API cannot provide a list of empty files. That information would be incredibly helpful in conjunction with the other idea so that you may programmatically identify an available review file of sufficient size for your needs. Beyond that, it may be useful to use the API to write an alert mechanism for when your system may be running low on available files.
It is possible to explore this information via SQL, but the…
6 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…
8 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…
14 votes -
Add Unique Control Numbers to Predefined Charges Table
Please add a unique, control number (ID) to predefined charges table in Sierra. This control number should be exported in the Fines Paid report. Currently, libraries waste significant administrative hours manually reconciling monthly, quarterly, and annual revenue because edited descriptions break automated data sorting (like Excel Pivot Tables).
The Problem:
To balance monthly revenue, libraries must sum payments by the type of predefined charge (e.g., photocopy charges, replacement cards, damaged books, donations).
Because Sierra lacks a dedicated, un-editable control number for predefined charges, we are forced to hardcode budget codes directly into the text description fields:
• 3323 Library Mug…3 votes -
REST API-compatible Time to Holdshelf/Time to Reshelve
Our library has deprecated the classic WebPAC in favor of a REST API-based custom discovery layer, but the Time to Holdshelf/Time to Reshelve temporary status message we've configured isn't included in the API response. It would reduce frustration for staff and patrons if we could implement a delay before items appear to be on the shelf when patrons check our website or mobile app.
Please add the temporary status to the REST API response.
6 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…
7 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.
8 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 -
Allow Create Lists to sort and export the normalized best author and best title fields
These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported or used for sorting. Best title normalized is particularly helpful for data brought into a spreadsheet as the removal of special characters and diacritics can greatly improving sorts and searching.
These fields are available via SQL, where I make frequent use of them, but for most of our users Create Lists is the only option for extracting data from the system.
6 votes -
New Max Owed amount for renewals only within the patron blocks table
Add a new Max Owed for Renewals within the Patron Blocks table that is separate from the Max Owed dollar amount/threshold. Sometimes patrons accrue more fines when renewing overdue materials via the online catalog or app on their own. Added charges from renewals online may also put them over the set threshold preventing them from renewing additional materials. The only way around the situation is for patrons to work with staff and the staff override the renewal using Sierra. When patrons use the "Renew All" feature in our discovery catalog and encounter the above issue, they are no longer able…
4 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…
6 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.
23 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.
10 votes -
Set a maximum price allowed for the item price field
I'm blatantly copying this idea from a suggestion by Wes Osborn in the Polaris Idea Exchange (https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46833076).
While creating item records, generally while following prompts in an item template, it is easy for staff to scan a value such as a barcode or ISBN into the price field by mistake, resulting in items that can incur bills in the billions of dollars if the issues are not caught. Additionally, it's easy to miss entering a decimal point and still wind up with charges exponentially higher than intended.
This could be mitigated by setting a maximum allow value for…
4 votes
- Don't see your idea?