116 results found
-
2 votes
This 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…
17 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 -
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.
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…
5 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.
43 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
14 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…
16 votes -
Choose Priority between Item-level holds queue and bib-level holds queue
More control over choosing priority between the item-level holds queue and the bibliographic-level holds manually so that the Processing department can pull back specific items on popular, high-volume holds with more ease.
3 votes -
Postpone/freeze a hold after it's Ready for Pickup
Postpone/freeze a hold after it's Ready for Pickup
Similar to Overdrive's redeliver option. Allow a patron to postpone/redeliver their hold one time if it comes in unexpectedly or at a time when they cannot come to pick it up.14 votesThe product manager will review this idea for possible inclusion in a future release.
-
Mark damaged items improvements
There are two things we would like to see in the Mark Damaged Items process. First we need a separate notice text for damaged items. We are trying to differentiate between lost and damaged and having to use the same notice text is problematic. Second, we'd like the status after the bill is paid to be Damaged & Paid (just like Lost & Paid) instead of just Damaged, as staff can't tell if this is an initial damaged status or one that has been paid for. These are handled differently and being able to create a list, for example, of…
45 votes -
Remove patrons from hold queue when they check out non-holdable copy
Problem: Many patrons have holds on titles in Quick Pick or Lucky Day collections. When they "get lucky" and check out one of these non-holdable copies their original hold remains in the queue and the patron often neglects to cancel their hold.
Impact: Fulfilling these unnecessary holds wastes time for staff and patrons and delays trigging other patrons' holds as the item sits on the holdshelf until the expiration date. Collection budgets are also negatively impacted as these unnecessary holds can skew the item-to-holds ratio for high-demand items that selectors use to determine how many additional copies to purchase.
Solution:…
42 votesThe product manager will review this idea for possible inclusion in a future release.
-
Add permission to prevent user deletion of notice jobs
We frequently have the unfortunate situation where staff accidentally delete their paging list from the list of Notices. Ideally, we'd prefer that frontline staff be able to prepare, print, & fulfill their paging lists but not be able to delete them.
Separating authorizations to create/edit/delete these lists from the preparation & printing would save support staff a great deal of time spent recreating these lists & remove some of the potential for frustration & confusion among frontline staff.
46 votesThis enhancement is planned for Sierra 6.6.
- Don't see your idea?