293 results found
-
Sorting Search/Holds Queries
Staff would like to see the ability to sort results retrieved from queries performed in Sierra's Search/Holds mode.
Say for example they do a keyword search for Star Wars at our Forest Park branch. 124 items are found. The results are displayed alphabetically by default. But if the staff member wants to quickly sort by DVDs, they can't even click on the Format column heading, as it exists currently.
While they can run multiple limits to narrow down the results by format, language, shelving location, publication date, etc., they might just as equally be inclined to SORT the entire list…
7 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
It's about time to make Holds APIs first-class citizens
Idea Description
It would be far nicer to have the ability to work with hold data directly--in contrast to having to retrieve hold data via the patron APIs. For example: currently, in order to (reasonably) find the "pickupByDate" values for holds with status "(Bib, Volume, Item) hold ready for pickup" you would have to use a combination of the Sierra SQL feature (to first find all the patron record numbers possessing such a hold) and then filter all the holds for the list of patrons (from the previous step) having the "pickupByDate" key in the response object. Once you have the holds,…13 votes -
Allow patron to set thaw date of frozen holds
Allow patrons to set a thaw date when freezing holds. Patrons often forget they froze holds and the hold lingers until it expires. Also, make this information available in the API for third party vendors, such as discovery layers.
26 votesThe product manager will review this idea for possible inclusion in a future release.
-
Increase minimum server account password length to 15 characters to meet PCI requirements
The automated tool employed by Clarivate support to update iii and iii-root passwords every 30 days has an 8 character limit, which falls short of PCI requirements (15 characters). The Sierra application server, which hosts the web page connecting to PayPal is in scope for PCI, and therefore login credentials that can edit that web page need passwords of 15 characters or more.
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
20 votes -
Allow self-check out of virtual items using Sierra API
Update the Sierra API to allow self-check out of virtual items. We use Bibliocommons app and our customers cannot use the self-checkout feature to check out INN-Reach items.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Customising pop ups
It would be nice to have more control over Sierra pop ups. Like if you are checking in a large amount of items it is really annoying to click ok every time the item is set in transit - you most likely already know these items are going in transit!
Also when creating a library card it would be good to be able to set a pop up "are you sure you wish to save a library card without (for ex) PIN code"? Sometimes you don't need that, but that is really rare.
7 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add a shortcut to print out patron barcode
When staff opens a patron's record, add a shortcut feature that allows them to print out patron barcodes. This will really help when someone comes in and don't have their library card with them, so wants to get their barcode information
7 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Re-page for item if pickup location has changed
Currently once an item is placed on hold, if the patron changes the pickup location after the item has already been paged for, the item will not be paged for again. With Title Priority Paging and “Prioritizing Hold Fulfillment at the Pickup Location” settings in place, this means a patron could be waiting much longer (depending on the “Pageslips: Number of hours before page can be transferred”) for their hold, even though they have fixed their mistake and reselected their intended pickup location. Additionally, even if the old pickup location pulls the item, they won’t be able to fulfill the…
16 votes -
Add the ability to require fixed-length fields, not just variable length fields
We require certain information to create a library card, however Sierra does not enforce this requirement at the system level. Since it isn't mandatory, some data simply never gets captured and creates more work on the backend.
Beyond that, having certain information in the record would allow us to build a better understanding of our usership so that we can make better decisions as an organization.
I especially would love the ability to require any and all of the fixed-length fields; especially patron category, birthdate, home library, and notice preference.
16 votes -
Include zero results for selected locations in all reports in Decision Center
Currently Decision Center only returns data for a location parameter if there was activity for the selected time period and does not return a zero placeholder for locations without activity. This creates extra work for staff when working with the resulting Excel files. They can't easily reference the cells in Excel consistently.
14 votes -
Sorting Searches in Patron Indexes
When creating a new customer record from scratch, or when updating & finalizing those submitted through our online application, we have staff perform some checks to prevent duplicate records.
They'll begin by searching the Name index to make sure that there's no pre-existing record for the same name. Then as backup, they'll try searching by birth date or phone number.
However, when you search by birth date or phone number, the results do not come back in alphabetical order, making things a bit harder than they should be for frontline staff. See example image where the search for the DOB…
6 votesThis idea will be reviewed by the product management team for possible inclusion in a future 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.
-
give libraries the option to exclude ratings from Homebound circulation workflows
Our homebound customers love the Sierra reading history functionality, but tell us that they do not want the Library to give them a checkout receipt that includes an option to rate the title. They also tell us that they do not want their personal information on the receipt (and the library cannot edit the Homebound receipt template).
Additionally, circulation staff workflows are hindered because if a stack of homebound items are returned, they have to use the keyboard / mouse to move past the checkin rating prompts.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Edit Username in Admin App
Once a user is created in the admin app, you are not able to update the username. You may update the password, permissions, etc., but not the username itself.
All of our clerk-level positions are part-time, so there is a lot of turnover. Each time an employee leaves, his/her account must be deleted and a new one created for the replacement. When the new account is created, you then must import all of the permissions, options, locations served, etc., of a comparable employee for the same location.
Ideally, we would simply be able to edit the username and password and…
64 votes -
Penalty points for patrons who reserve books and then don't pick them up at the library
Currently, on Sierra it is possible to block patrons based on overdue penalty points (OD PENALTY) when they check in or renew overdue items. This is done with the patron fixed field OD PENALTY. The system calculates the penalty points that have to be added to the patron record and when a patron exceeds the maximum number of penalty points allowed by the library, the patron is blocked. More info at https://documentation.iii.com/sierrahelp/Default.htm#sgcir/sgcir_fine_penaltypoints.html
THis feature is very useful. Wouldn't it be a good idea to be able to apply a similar strategy for patrons that request a hold on a bib/item…
9 votesThis idea is planned for Sierra 6.5.
-
Enable API update of patron records to blank out expiry date
Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.
The patron API cannot do this - blank values are rejected as invalid JSON e.g.
{"expirationDate": " - - "}
{"expirationDate": ""}
{"expirationDate": "--"}
{"expirationDate": "null"}All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.
Enhance the API to accept a blank value in expiry date.
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Eliminate the two-tiered (context) logins that identify branch locations and personalized user
Several years ago we adopted context logins. We have established that a 1 tier login will not work for us.
CURRENT STATE : Our Regional Library consists of 39 branches in almost as many cities. To distinguish the branch of our Sierra users we currently use a two-tiered login. This login process allows us to continue to use generic branch accounts while meeting our obligations to protect customer information. The two-tiered login allows us to collect branch-specific data and apply unique user settings, options, and settings.
The drawback is that our staff must login twice and it may pose an…
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Customize default item view based on function
It is currently an option to be able to set the default view of an item record across Sierra. However, it would be nice to be able to have a different default view set for the different functions in Sierra.
For example:
When in the Circulation function - I'd prefer the default view to be Hold.
When in the Cataloging function - I'd prefer the default view to be Item.
When in the Acquisitions function - I'd prefer the default view to be Order.I understand that I could just have multiple windows open and set the default view differently…
21 votesThe product manager will review this idea for possible inclusion in a future release.
-
Separate summary view property for each of the search functions
When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.
If you opt to change that setting however from the record view properties menu (say to change this to view all) it can impact all 4 search functions. It would be better to split this menu out, so that the setting for each…
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?