Skip to content
Innovative Idea Exchange

ILS - Sierra

Recently Activity

ILS - Polaris Updated

Last In House Use column

Reporting & Analytics UNDER REVIEW

ILS - Polaris Updated

Automatic processing for item record details

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Patron block pop up

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Holds that can't be filled

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Volume-Level Holds for Blank Volume Field

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Live Preview Within Bibliographic Record Sets

Cataloging & Metadata Management UNDER REVIEW

ILS - Polaris Updated

Vendor integration

Customer Relationship & Account Management UNDER REVIEW

Don't see your product?

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

253 results found

  1. Sierra libraries cannot freeze a hold in Vega Discover (and likely other third-party catalogues) if an available item could fill that hold. Innovative has confirmed that this limitation is caused by Sierra, and that Sierra's hold-freezing behavior must be changed before Vega Discover can support this functionality.

    Currently, customers cannot freeze a bib-level hold if there is an available item that could fill the request. This prevents customers from managing their holds the way they want. In many cases, they do not know an appropriate "Not Needed Before" date, but they do know that they are not ready to receive…

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Allow Scheduler to send a file of records to an email address. At the moment it will only ftp a set of records, which is fine for some purposes but not for others.

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We'd like the ability to customise the display of Sierra popup messages, specifically we'd like the ability to increase the font size for key information (for example, the pickup location or destination) so it stands out more clearly. We would also like the option to hide the call number, as it is not used by our library.

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Now that the inventory date updates in checkin in Sierra Desktop, it would be great if it would also update in checkin in Mobile Worklists. Currently it only updates when using Sierra Desktop. It would be very helpful to be able to use MW in the stacks to do inventory.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported or used for sorting. 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.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The elements that print on a checkin receipt currently are fixed and include unique identifiers (patron name and barcode) that some of our libraries would like to not have printed out. These receipts should be customizable like many others in Sierra, not necessarily allow for print templates (though I wouldn't object to that) but at least a customization ability similar to what's available for the default (non-templated) due slips.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. We would like “replacement” changed to a term that reflects the actual item status. Currently, “replacement” is used for both long-overdue and damaged items that have been billed. To determine whether a billed item is damaged or simply overdue, staff must open the item record and check for a damage note.

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. With the new Patron Checkout Limits table, we have lost the ability to group patron types (ptypes) into a category when configuring checkout limits that also use criteria such as Library Location or Item Location.

    Currently, a separate row must be created for every individual ptype, which significantly increases setup and maintenance effort. In environments with many patron types that share the same checkout limits, this results in a large number of duplicate entries.

    We would like the ability to define and use Patron Type Categories/Groups within the new Patron Checkout Limits table, similar to the functionality available in previous…

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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…

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. At my library, the installation of RFID equipment & the entry of the required IPs in Sierra are handled by two different departments. Typically, I'll see a ticket that a new PC/RFID pad has been added & receive a request that the IP be added to Sierra.

    In addition to the RFID Pad Server Settings table in Sierra, we maintain a separate spreadsheet of assigned IPs, machine names & information on when & whom the request came from to add or replace them.

    While adding & replacing more than 20 IPs this morning, it dawned on me that this process,…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. When a Sierra SDA login is 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.

    However, when the staffer changes that setting 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 review view summary option out so it may be set…

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Our library would like to have pages for item-level holds repeat until they are filled. Currently, the only way to achieve this is by checking the "Do Not Clear" checkbox when running the item paging list each day. However, staff have to remember to toggle this setting every time they run the list, and if they forget, all previous pages will be lost and can't be restored the next time they run the list.

    We'd like a way to have item pages persist by default.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. This is a resubmission of a recently expired idea. I’ve added insights from other users shared in comments on the original post.

    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 have the Notice History feature, which shows the number of items for which notices are sent. I feel like 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.

    Beyond metrics, this would aid…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. The new feature in 6.7 to print spine labels from a review file is fantastic, but it lacks access to the prepend blank labels feature that you have access to when printing from a label queue. Many of our libraries utilize sheet labels instead of continuous feed printers for spine labels and thus tend to rely on this capability. We would love to see it added to the new feature in order to bring it into parity with the traditional label printing method.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Please add the ability to report on patron record renewals. We currently use the Created Date field to track the number of new library cards issued. However, there is no reliable way to determine how many patron records have been renewed. While the Last Updated date changes whenever a patron record is modified, it is triggered by many different types of updates, making it impossible to distinguish renewals from routine record maintenance.

    Having the ability to track patron renewals would provide valuable statistics for monthly reporting to our Board of Control and Parish (County for the rest of you...) administration.…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. We have many vendors who have a need to check data in a few patron record fields as part of their authentication process. Fields such a ptype, home library, the expiration date, etc...are necessary to confirm that a patron is affiliated with the institution subscribing to that vendor's resource and that their card remains in good standing are necessary to provide. However, doing so currently requires providing the patron read permission, which also exposes a variety of additional sensitive data that these vendors should not have access to for their needs (PII, checkouts, fines, reading history, etc.)

    The lesser patron…

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. This is a resubmission of just-expired idea from Cecelia.

    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.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. PINALPHANUM does not accept special characters.

    If Vega Discover continues to be limited by wwwoptions for PIN creation, this option should accept special characters.

    PIN Best Practice: The strongest defense combines a long length (12+ characters) with a true random mix of letters, numbers, and symbols.

    Length vs. Complexity: Recent security guidelines emphasize that making a password longer (like using a multi-word passphrase) is often more effective than adding a single symbol to a short word. That said, library users do use special characters and want them included in their library PIN.

    Adding symbols increases the character set…

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. We'd like the ability to attach a volume record directly from the Serials Check-in module. Currently, because this functionality is not available within Serials Check-in, staff must rely on workarounds and switch to other functions to complete the task. Adding this capability would streamline workflows, save time, and make the Serials module more efficient and useful.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Make the Days closed table able to have a range of days. When we close a branch for maintenance we have to put in each day, it would be great to be able to put in a location code and then something like 5/1 - 5/25 or comma entries like the loan rule determiner table.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?