244 results found
-
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.
-
Create a Review File endpoint
Idea Description
This idea is based in part on one submitted back in 2019 by Andy Helck. Create an endpoint that will provide the list of records included in a specified review file from Create Lists. I essentially envision this as the API version of the bool_set SQL table.Idea Value
This would provide outside systems the means of retrieving lists of titles that staff maintain within create lists and can provide a means for services to access data without having to work out how to create Json queries.11 votesThis idea has been accepted for inclusion in Sierra 6.3.
-
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.
7 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
15 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.
13 votes -
View Public Display - Allow for Multiple Choices
https://ideas.iii.com/forums/951745-ils-sierra/suggestions/46670854-sierra-5-5-direct-view-public-display-to-disco is closed/says it's already supported, but the part for being configured to more than one display option is not addressed. We would like to be able to have more than one option to display - Vega, Classic, Encore and even III Mobile if possible - so we can see how all iterations look right from the SDA. So in the menu it would be View | Public Display | array of choices
15 votes -
Improving loan history
Our patrons are curious about their loan history. They would like to sort it by author or title in addition to the checkout date. We have told them to export it. But exporting the checkout history loses the checkout date! Could more sorting possibilities be added to the catalogue and checkout date added when exporting?
6 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 will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
4 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
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.
-
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.
-
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.
-
Protect local-only MARC fields that have a specific subfield coding
There are instances where its appropriate to put in a MARC field in the bibliographic record that only pertains to your local institution and you wouldn't want that field erased if the record was overlaid. If that MARC field was designated a local-note, using a $5 then that field would be "protected".
8 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…
20 votesThe product manager will review this idea 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…
58 votes -
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.
3 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.
4 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.
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Save Query As - Alphabetical by Query
When using Create Lists and using Retrieve Saved Query, you are able to sort the list in ascending order. When you go to Save As a query, it goes in and there doesn't appear to be any sort of order (in the past I swear it went in the order it was added/saved). So if you have to tweak your query and need to Save As again, good luck finding it, esp. when you have 100+ saved queries. Ideally you could sort the list of queries, like you can when you initially retrieve them.
2 votes
- Don't see your idea?