298 results found
-
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:…
37 votesThe product manager will review this idea for possible inclusion in a future release.
-
"Both" Option for Due Slip Delivery
The first request we got after releasing emailed Due Slips was for the option to generate both an email and a print slip. Some people like the physical reminder in the form of a printed slip (that doubles as a bookmark!) and an electronic version that they can use as a reminder or a fallback.
18 votesThe product manager will review this idea for possible inclusion in a future release.
-
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.
-
NCIP Authentication - Add support for optional blocking
We recently started using NCIP authentication for our new ILL service. We learned after implementation that NCIP login is blocked for any of the reasons in the Patron Block Table. This makes sense when the block is for an expired card, or for fees over the threshold. This makes less sense when they have reached their maximum holds in Sierra.
What we're seeing is that patrons cannot log into the system at all when any of the block parameters are true. We would like to be able to enforce certain blocks but not others for account login.
We can increase…
3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Restrict Location Code Edits to Locations in Scope (especially in Rapid Update)
There is currently a setting allowing us to prevent logins from editing records with a location code outside of their current scope. However, users are able to edit records in their scope to have location codes outside of their scope, which then blocks them from being able to edit the records again. This happens accidentally sometimes, and is particularly a problem in Rapid Update. It would be great if item location dropdowns in Rapid Update, and possibly the item record as well, only showed locations in the user's scope in order to prevent this problem. Alternately, the system could prevent…
17 votesThe product manager will review this idea for possible inclusion in a future release.
-
Allow the "remember me" in Sierra Desktop App login screen to remember passwords as well as username (as previous versions of Sierra did)
Previous versions of Sierra (version 5 and below) allowed the saving of usernames and passwords in the Sierra desktop app login screen. Since upgrading to 6 this functionally has been lost.
9 votes -
Granular Permissions on Item Record
We would like to see more specific permissions on items records to allow staff who don't have access to edit entire item records to be able to do basic things like add and delete item messages or change the status of the item.
Frontline staff are discovering outdated item messages or finding that items are missing, and it's inefficient for them to have to contact someone else to change the status of the item, or delete an item message attached to it.
15 votesThe product manager will review this idea for possible inclusion in a future release.
-
Include hourly patron borrowing reports in Decision Center
We use the hourly patron borrowing reports in Web Management Reports to track patron visits at offsite hold lockers. We would like to have this report migrated to Decision Center since this is the tool already in use by our frontline staff.
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Allow Create Lists to export the best title and best author normalized fields
These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported. Best title normalized is particularly helpful for data brought into a spreadsheet as the removal of special characters and diacritics can greatly improving sorts and searching.
These fields are available via SQL, where I make frequent use of them, but for most of our users Create Lists is the only option for extracting data from the system.
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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 -
Allow staff modification of frozen holds
The current "Frozen Holds" function in WebPAC does not allow for patrons to select a date at which they want their holds to be "unfrozen". Staff have the ability to set a "Not Wanted Before" date on behalf of the patron, but there is currently have no way to modify the date of a frozen hold on behalf of a patron in the Sierra Desktop App. SDA should have the option to change that date once frozen by the patron, in the event the patron cannot unfreeze it themselves.
Staff feedback: "We've had a lot of patron confusion around freeze…
21 votesThe product manager will review this idea for possible inclusion in a future release.
-
Be able to create and edit paging list templates with LXStarter rather than Jaspersoft
I'm hoping that the great improvements to patron notices with LXStarter can be considered for staff use, like paging lists.
22 votes -
Current Location variable-length field in item records
Libraries with varied types of media in their collections require more location information associated with items than a shelfmark. We would like to see a Current Location field as standard in the item record. This field must be included in the data libraries for item paging notices as retrievals staff will need this information on retrievals lists/slips.
Idea Value
To record the exact location of items within the buildings, which will facilitate retrieval of less standard items or special collections items that are not easily stored in a standard sequence. Current location data is essential for museums accreditation.8 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.
-
Allow Global Update of Fund Codes
Allow for Global Update of fund codes. I work in an academic library and will often get purchase lists from our liaison librarians for a specific department. The records are brought in and the attached order records are edited in GU with the correct vendor, and selector, etc. It would be a time-saver if I could also update the fund code (which are tied to academic departments) at the same time.
14 votes -
Split the Patron_Name in the Item Paging Slip and Item Paging List data libraries into first name and last name
The element PatronName in the Item Paging Slip & Item Paging List Data library be broken up into Patronfirstname and patronlast_name elements like in the hold/transit slip data libraries.
3 votes -
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.
-
MFT support in data exchange
Prior to Sierra 6.0 and the introduction of MFT, it was possible to use FTP to transfer files though data exchange within Sierra. This is no longer possible as MFT is not supported in data exchange.
Please add support for MFT in data exchange in the same way as support for MFT has been added in scheduler.11 votes -
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.
-
Make the hold status information updatable in API
There is currently no way to update the status of a hold in the API.
It would be very useful to change the status from
"status": {
"code": "0",
"name": "on hold."
},to
"status": {
"code": "i",
"name": "Requested item ready for pickup."
},Enhancement to be integrated into https://ideas.iii.com/forums/951745-ils-sierra/suggestions/47618129-it-s-about-time-to-make-holds-apis-first-class-cit ?
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?