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. Please integrate text messaging/SMS as a notice delivery method just like print, phone, and email. Some patrons want texts and no other method. Even if patrons must complete a step outside Sierra, staff should be able to see and choose text as a preference. This would make things more consistent and easy for both patrons and frontline staff.

    We had planned to switch to Vega Interact SMS but discovered that it is intrinsically linked to email notices, limiting its ability. We would love to have SMS as a real notice option in Sierra.

    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)
  2. Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.

    Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the…

    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)
  3. Create Lists allows staff to create review files of invoices, but a number of useful fields from the invoice cannot be exported from the system. Notably the subtotalamt, shippingamt and totaltaxamt fields, which can all be accessed via both SQL and the RestAPI, are missing from the export options.

    We would like to see these added so that fuller invoice data could be exported into something like Excel for further accounts reporting and tracking.

    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)
  4. Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.

    Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,…

    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)
  5. It would be nice if there was a setting in the Receiving function to limit your search to only items available to be received. We search by PO and have to wade through loads of items already received and billed. This was available years and years ago on the old Horizon system.

    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)
  6. 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)
  7. Libraries are increasingly looking at ways to gather metrics on patrons without identifying them. Data on age, gender, race, or all manner of characteristics might be collected, depending on the library.

    I'd like to see Sierra be more accommodating in what it can collect & store on a patron's record, with the introduction of one or more additional PCODEs that can be used to store a significant amount of fixed field codes.

    For example, we partner with schools in our service area & offer not only educator cards, but do an upload of student data. Having schools within our service…

    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)
  8. Many libraries offer mail delivery services for patrons who are unable to visit in person. Currently, when items become available, these patrons receive a standard "ready for pickup" notification, even though their materials will be mailed to them. This creates unnecessary confusion and may lead patrons to believe they need to come to the library.

    Providing the option to customize or opt out of specific notifications, such as "Ready for Pickup" alerts for patrons enrolled in mail delivery, would greatly improve clarity and enhance the user experience.

    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)
  9. I was hoping to see the login used to receive the items listed in the Item Record History. If possible, it would be great to see both the user and the process.

    Event | user | PROCESS
    Created | user | MANUAL
    Created | user | RECEIVING
    Updated | user | GLOBAL UPDATE
    Updated | user | MANUAL

    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)
  10. We are interested in being able to tap into the Days closed table programmatically but it is inaccessible to both the APIs and SQL, and doesn't even have a native export feature (though you can copy and paste it easily enough).

    Creating a SQL View for it seems the most straightforward solution, just provide access to the existing table, along with row numbers to preserve the ordering.

    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)
  11. Data Exchange should determine if a file being loaded is in UTF-8 or MARC-8 format before loading. If it is MARC-8, it should be converted to UTF-8 before loading.

    I want to be clear that I'm not talking about using the MARC bit that supposedly identifies if the character set is UTF-8. That cannot be trusted. I want a system like the character detect feature in MarcEdit, that will actually look at the characters in the incoming records and determine what character set they really are.

    There are still a lot of MARC-8 records out there, and it is not…

    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)
  12. Currently, only when you cancel a hold from either the Hold tab or the Hold queue do you get the option to generate a hold cancellation notice. When a defunct hold is cleared from the holdshelf (clear expired holds), we would like to see a prompt to send a hold cancellation notice(s), just as we do when cancelling holds outside of the clear holdshelf process. All those that get cleared could use the same “drop hold” message in the text of circulation notices (explaining your hold has been cancelled because it’s expired/hold pickup by date has passed). These would be…

    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)
  13. It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:

    1. Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
    2. Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
    3. Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates…
    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)
  14. Currently, Sierra does not provide built-in functionality for processing or tracking refunds. While the system records partial payments that result in credits (displayed as negative fines) and waivers applied by staff (visible in Fines Paid), there is no equivalent workflow or tracking for refunds.
    We request the addition of a refund tracking feature within the patron record, ensuring that staff can see when a refund has been issued. Specifically, we propose:
    A clear refund indicator in the patron record.
    A display of refund amounts including payment method in the Fines tab, similar to how fines and waivers are shown.
    An…

    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)
  15. In a consortial setting we have some libraries that would like to avoid showing last patron data for a item in an attempt to avoid retaining data that could be used to breach a patron's privacy.

    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)
  16. When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands…

    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)
  17. 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)
  18. 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)
  19. 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)
  20. 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)
  • Don't see your idea?