278 results found
-
add location column in Count Use function
Under the count use function, is it possible to add a location column? Currently, we have Title / Barcode / Count / Status. This way, when staff collects used but not checked out items and counts their usage, they can also see - at a glance - if the item belongs to a different floor/location and can separate it on the spot.
This added information will save staff time and minimize the chance of something being misplaced.
4 votes -
Statistics - Saved Queries Should Retain Cross-Tab Selections
Saved Queries in the SDA should function the same as they do in SierraWeb.
In the SDA:
If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.
If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record),…
3 votes -
Add "mark damaged items" workflow to checkin
Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.
All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.
Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like…
9 votes -
/v6/patrons/{id}/holds/requests/form API endpoint should accept item record numbers as parameters in addition to bib record numbers
The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.
As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may…
4 votes -
4 votes
-
Include authorities in the Search/Holds module
It'd be great if authority records and cross references were included under the Search/Holds module and be the same as what staff encounter with the Catalog module. Right now it is different. In our system, staff often use Sierra to place holds with the public on their behalf. It would be great if authorities were available in the Search/Holds module results display so that staff could benefit from the information.
If a staffer did an author search and they had a pen name (Robb, J.D.) then they'd be redirected to see the other author's name (Roberts, Nora).... Or they may…6 votes -
Money Owed Data Point for Billed Notices
Idea: add the money owed fixed field as an option for a data point in the Bills Notice Data Library for print templates.
Value: Some libraries would like to be able to call out to users how much in total they owe on their account, not just the total of the items on that particular bill. Adding this field to the data library would enable them to do so.
3 votes -
Clarify Fines Payment Lock Messaging
The current wording of the fines payment lock messaging implies the presence of fines, which is not always the case and is misleading. To reduce confusion for staff, please change the message wording to indicate that another station has the record open, therefore the fines function in the patron record is locked. This will indicate to staff the reason why it's locked (another station has it open) and what they can't do while it's locked (access the fines function in the patron record).
17 votes -
Add filtering parameters to the GET /v6/bibs/search API
Hello Everyone,
We are currently using the GET /v6/bibs/search API to take advantage of the AWS search integration, which has been working well. However, we’ve encountered limitations in filtering the search results by Material Type, Collection, Language, and Location.
It would be highly beneficial if this API supported additional filtering parameters to narrow down results at the source. Relying on the client or webhook server to apply these filters adds complexity and can introduce delays in presenting results to the end user.
Thank you.
1 vote -
More universal accessibility features
Improving universal accessibility features for users/employees with diverse accessibility needs.
For example, for employees with visual impairments :
- High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.
Even just the high contrast would help a lot. Additionally, it would be helpful if users…
10 votes -
Include the AA (patron identifier) element in the 10 Checkin Response for SIP2
When users return the materials via self-check machines, we want an email receipt to be automatically sent to them. Unfortunately, Sierra does not currently support the AA element in the 10 Checkin Response. Some libraries purchased the Patron API feature to get it to work but if Sierra include the AA element, it will simplify the process.
1 vote -
Add search functionality to scoping rule function
As a consortium, our system has hundreds of location codes. We appreciate the new functionality to add locations to scopes ourselves, but it is cumbersome to scroll through the list of hundreds of branch entries each time to find the code you need to add. It would be helpful if there was search functionality, where you can type in the code, and it brings up the corresponding entry in the branches list for you to select.
6 votes -
Make the "New PINs do not match" message configurable in PIN reset flow
In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.
This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.
Suggested improvement:
Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQ…4 votes -
Add ability to extend the hold Pickup By date to the /v6/patrons/holds/{holdId} API endpoint
Currently the only hold parameters one can modify via the API are
PatronHoldPut {
pickupLocation (string, optional): the hold's pickup location code,
freeze (boolean, optional): whether the hold should be frozen (suspended)
}It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters. There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.
Having this functionality in an API endpoint would permit a…
10 votes -
Insert/Update Location Codes from a CSV file
Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.
Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is…
8 votes -
Add "Volume" as an option in "New Record Templates" in Admin Settings.
For volume records, it would be helpful to have 'volume' listed as an option in Admin - Settings - New Record Templates (see attachment). When adding volume records, it would be helpful to have the desired 'volume' template appear in the same way our item record template appears. Currently we have to always select the volume template we want to use. All the other options are listed and it would be nice to have 'volume' listed as well.
5 votes -
Disable fine lock
Because our library does not use fines, having the "Failed to acquire fines payment lock. If not cleared, fines payments cannot be processed" message is of no utility for us. We'd love multiple users to be able to view a patron record without this message showing up.
7 votes -
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…
18 votes -
Add Character Map to Patron Record Creation/Editing Menu
Despite the constant threats to our funding & the fact that some seem to treat the notion of DEI as offensive, we continue to want our library to be seen as a welcoming & inclusive environment for our patrons.
We would like to be able to extend this to how their name is represented in Sierra & on notices/when seen in the catalog. We currently have a sort of crib sheet for staff to use to insert diacritic characters into patron names as needed, but think it would be helpful if they didn't have to navigate away from Sierra when…
10 votes -
Add "hold status" and "item status" limits to high-demand holds function
The high demand hold report is a powerful tool that sums system items and system holds.
Adding a "hold status" and "item status" pre-search limiters would vastly improve the use of this report
Why add these limits?
There is no Sierra product (including Decision Center) that allows users to deselect frozen holds from “total holds” count.
This report counts "system holds" as any hold with any status (including item holds that will be filled by "in transit" item)
This report counts "system items" as all items (including billed and missing) so there is no way to know how many items…
13 votes
- Don't see your idea?