96 results found
-
2 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Exclude specific patron types from getting notices
Being in an academic library, we have certain patron types which function differently than other types. This applies particularly to the differences between a student patron type and a faculty patron type. It would be helpful for us to have the ability to exclude certain patron types from getting certain kinds of notices.
12 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Charge type on fines tab needs to specify if it is a damaged item
Would love to see the word "replacement" changed to a word that gets at the actual status. Currently the charge type of "replacement" is used for a long overdue item that has been billed or a damaged item that has been billed. To find out if the item that has been billed is damaged or just hasn't been returned you have to go into the item record to see if a damaged note has been added.
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Allow for Diacritics in E-mail Receipts
We've been exploring new ways that our library, as an institution, can meet the evolving interests of DEI efforts. One very small but meaningful way we thought we might do this is to allow for the inclusion of diacritic characters in customer names in Sierra.
Their inclusion appears as desired on the customer record when created/displayed in Sierra (images dia1 - dia2).
They do not appear to impede searching for the customer by name - the search just ignores them (images dia3 - dia4).
They appear as desired in the name display in the Classic Catalog (image dia5).
They appear…
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Notify the library staff of new ILL requests via email
An option for Sierra to notify the library of new ILL requests via email rather than a staff member manually checking the new requests function.
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Make Third Party API Transactions More Apparent for Sierra Customers
Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.
The idea won the "Let's Connect Sierra API Challenge."
With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.
My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long…
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
2 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
-
Returning items not in hand
We were wondering if a “Return Item” button could be put alongside “Renew” “Claimed Returned” when in the Checked Out Items screen, so that you can return an item not in hand etc.
Simply select the item already issued to a member, and hit 'Return'.5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Location Code 0 Displays as None in Checkout Location Field
With the recent changes that allow the label to display in the item record, staff now see the descriptive name of the statistical group in the checkout location. However, 0 displays as None and does not honor what is in the Statistical Group Maintenance table. We have ours labeled for Web Renewals and would like this display to honor what is in the table as opposed to saying 0 None.
5 votes -
Make Selecting 'All' Genuinely Purposeful
As I'd done in similar scenarios countless times before, yesterday, I was in the process of modifying the activeholds on my account in Sierra to change them to a newly created pickup location.
There were several that needed changing, so I selected 'All.' However, rather than make a batch change of the half dozen or so that needed updating, Sierra cycles you through each item individually, forcing multiple arguably unnecessary clicks, when the expected & more intuitive outcome in this scenario would be to indicate the desired change once & see it changed for all selected records.
9 votes -
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…
12 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.
15 votes -
SIP2 support for NCIP check in
Currently when NCIP items are returned via a sorter, SIP2 is not able to check them in. This results confusion for staff and patrons, as when staff check in the item it traps the hold once again. Currently, the only solution is to re-check out every item returned through a sorter to the patron, and then re-check it in via SDA, which adds to overall workload.
5 votes -
Limit Ability to Clear Expired Holds & Holdshelf
So as we've seen repeatedly despite training & periodic reminders to exercise caution, the putrid corpse of liberty can really do a number on the Clear Holdshelf Report. We see disturbingly frequent scenarios where someone at one of our locations is not careful & winds up wiping out the holdshelf report for all 40 other branches. While we're fortunate to have someone here who has created a sort of recovery tool, we'd like to see the potential for such chaos somehow eliminated.
16 votes -
Allow staff to toggle between printing and not printing a date due slip
When checking out a patron within Sierra, it would be best if the staffer could easily toggle between offering a paper date due slip, an email slip or no slip. This functionality seems to have gone away.
10 votes -
check in claimed returned (item location should reflect where item was made claimed returned)
For libraries with floating collections, the location where an item was made "claimed returned" may not reflected in the item record. This is because the 3 options staff have when an item is "claimed returned" does not change the location of the item.
Essentially the problem:
An item is “checked out” at location A.
The item is “claimed returned” at location B.
The item location remains as location A.Staff have 3 choices when they make an item claimed returned:
· 1. Places a claimed returned note in both the item and patron records
· 2. (Optional) Removes the check-out…
4 votes -
Remove duplicate items on paging list
Duplicate instances of a single item frequently appear on Bib Paging Lists resulting in confusion and either wasted paper (up to 7 pages were printed for a single item once) or wasted time deleting those lines before printing. There is no need for the paging list to alert us to multiple holds for any item, especially if we can't physically fulfill those holds.
33 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
9 votes -
Generate Statement of Charges directly within patron record
It would be very helpful to be able to print a Statement of Charges directly from a patron record (and have it formatted for 8-1/2 x 11 paper and mail-ready).
For context, we are a 138-library consortium, all notices are Auto Notices, and we do not run Statement of Charges for the consortium. Yes, you can run a statement for 1 patron in the Notices function, but this requires consortium staff intervention since that permission is locked down to consortium staff. It would be much simpler for our member libraries to be able to print such a statement on an…
15 votes
- Don't see your idea?