291 results found
-
Allow Requiring SAML for Sierra Web
Sierra now supports SAML for authenticating staff, but still allows users to authenticate without MFA using the less secure Sierra legacy authentication method. Sierra should allow administrators to require SAML authentication instead of always allowing users to choose SAML or Legacy.
5 votesThe product team will review this idea for consideration for a future release.
-
Allow users to define icode1 in Sierra
Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.
25 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
48 votes -
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Increase Invoice Limit for Downloaded Invoices
The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.
Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.
Not all shipments are dealt with sequentially, which further complicates matters.
14 votes -
add "did you mean" search logic to SDA keyword search
Circulation staff would like to see "did you mean" logic applied to the SDA keyword search. This is the top complaint from circulation staff who search the database to help customers place holds. Staff are used to a Google (or Discovery Catalogue) keyword search that has some flexibility for human error.
17 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
More Granularity in Hold Blocks
Currently, the ability to override a hold block is governed by permission 92.
A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.
One scenario especially has been problematic for as long as I can remember:
A patron finds an item on the shelf & takes it to a service point to check out. It turns out that this item can satisfy a hold placed by another…
7 votesThe product team will review this idea for consideration for a future release.
-
Require authentication to view Sierra API documentation
Enhance cybersecurity by not revealing the api methods through the swagger interface to unauthenticated users. For example, a potential hacker can view the swagger interface which shows all methods and explains how to use them. This is an issue on all api endpoints including the iii sandbox. My idea is to only reveal the swagger methods to authenticated users.
https://sandbox.iii.com/iii/sierra-api/swagger/index.html#!/patrons
6 votesThe product team will review this idea for consideration for a future release.
-
Add a Note Field in the RFID Pad Server Options Table
As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.
An additional free-text field to…
15 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Ability to change password on login page of SDA
Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.
18 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Update "last checkin" field even if item wasn't checked out
Update the "last checkin" field every time an item is checked in. Now, when you check in an item, the "last checkin" field is not updated if the item is not checked out. I don't know of any reason to not update it. When I look at an item record, I want to know the last date that the item was seen; this can be useful in tracking down items that seem to be missing, or coming up with a list of items that might be missing.
10 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Allow libraries to customize return addresses for bills
Our library would like the option to have the return address for bills reflect the address of the patron's home library (as defined in the patron record) rather than the owning location of the item. The current setup (using the owning location of the first item on the bill) means that when patrons check out items sent from another branch to fill a hold, they can receive a bill from a library that they may never have been to. While patrons can visit any of our locations to resolve a bill, we would prefer the bill to reflect their local…
6 votesThe product team will review this idea for consideration for a future release.
-
Ability to "Rebrand" Teleforms in the SDA
To view a customer's recent history of telephone notifications, from their record, staff currently navigate from View - Teleforms. We haven't used Teleforms as a product since 2017, & it's a little confusing to have to explain to staff the connection between this, i-tiva, IPA, Vega Interact, or whatever other products might be in play.
We'd like to see the ability to rename Teleforms to whatever the locally used product might be, or even something generic, like Telephone Notification History.
1 vote -
Release Item Price Field in Sierra Item Record for SIP2
Libraries using SIP2 connections for self-checks cannot have due slips that have "You Saved" information because the Item Price field is not available via SIP2.
While due slips with this information can be used at a staff station with the SDA, as more and more libraries move to self-check, the lack of this field's availability in SIP2 is a barrier.
Use case: a library has a self-check machine that uses SIP2 and wants to include "You Saved" information on their due slips.
12 votes -
Order Status rapid update
Rapid or global update to update all Order Status at once.
10 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Support SFTP for WebPAC file upload
Organizations with restrictive security policies may be unable to use FTP over port 1021 (or any other port) for file transfer to Sierra WebPAC, since FTP is an inherently insecure protocol. For the same reasons, FTP should ideally not be in use at all (even where permitted by the customer's organization) since it entails sending login credentials in cleartext which makes it subject to interception and abuse.[1]
Without FTP, the only alternative is to use Web Master within Sierra Desktop App to upload files to make changes to Live or Staging WebPAC screens.
If Innovative implements Secure File Transfer Protocol…
6 votesThe product team will review this idea for consideration for a future release.
-
Option to exclude frozen holds from total holds queue in catalogue
Libraries should have the option to exclude frozen holds from the total holds queue that appears in any catalogue.
Benefits:
1) Customers will have a better idea of where they are in the hold queue.
We encourage customer-driven hold management, and customers have told us that they want an estimate of when their holds will be filled.
This is especially true when customers place multiple hold on titles within a series.2) Customers will not see inflated hold queues and provide feedback to the Library that they should purchase more copies.
3) Customers could make an education decision on whether…
15 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add fund code used to purchase item to item record
I was asked recently to create a list of items added to the database based on a fund code. I don't believe that I can do that in Create Lists. This is because order records and item records have no common field to link them.
I also cannot use Create Lists to pivot item records to their attached order records or vice versa.
We need to be able to do this because 1 bibliographic records may have items attached that were purchased from different funds. Example. 1 Fiction title may have items purchased from an ARP (automatice release program), and…
20 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?