Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

318 results found

  1. I currently have a need for a Locations Served group which can accommodate 1,245 location codes. The limit imposed by Admin Corner is 1,000 location codes, and per case #08077395, Support asserts that Sierra will not support more than 1,000 location codes per Locations Served (so it's not simply a limit of the Admin Corner interface).

    Increasing this limit will potentially lead to a modest increase in memory consumption by any and all circulation processes which hold these Locations Served tables in memory, but do we really need to be concerned about Kilobytes of RAM in 2025? Other Sierra configuration…

    3 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. The Invoice Summary that is sent after posting invoices only lists the voucher number. Our Finance department has to go through the Invoice Register and match the invoice number to the voucher number to know what invoices should be paid. This is very time consuming, and susceptible to human error. Please consider adding the invoice number to the Invoice Summary.

    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 to see a date/time stamp on the "Restart a process/terminal" display in the Admin Corner and be able to sort by it. We sometimes run out of licenses because staff don't sign out of their SDA sessions at the end of their shifts, and we have to contact Innovative and request that connections older than the current day be closed. It would be helpful to be able to do this ourselves. Currently, we can preemptively reset all connections early in the morning before staff arrive, but if a problem arises during the day we don't want to cause…

    8 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. Currently the Record History report for Bib Records in Sierra contains a list of record changes, the login that made a change, and when it was changed.

    However, if the change to a bib record was attempted with a login without the required permissions, Sierra will ask for a login with elevated permissions and allow the user make a change once logged in. In this case, the Record history will record the first login (without required permissions), instead of the elevated login needed to make the change.

    Problem: Record History report for Bib Records Record History report for Bib Records…

    6 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. I recently wanted to run a search for all records that matched certain criteria and did not have an 856 field. However, Create Lists does not currently have a "lacks field" option. It would be very helpful to be able to search for records that do not have certain fields.

    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)
  6. Sierra queues the hold for paging at the time the hold is placed, based on the data the hold was placed with. If the hold is modified after that (by changing the Not Wanted Before date), those changes don't update the paging queue, and Sierra will continue to page as if the hold had not been modified.

    10 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'd like to be able to limit access to the Login Names & Parameters section of the Admin Corner (especially the Limit Network Access tables) via permissions. Certain functions, such as load tables, require certain staff members to have access to the Admin app, but having the login names and parameters unrestricted leaves an unnecessary hole in security. There are other functions in Admin Corner that require separate permissions and prompt users to enter their credentials, but not this one.

    8 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. I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.

    For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they…

    5 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. Each week staff go into Create Lists and repopulate a designated review file with current data from a system-generated list. Two examples of system-generated lists include the OVERDUE ITEMS and PURCHASE ALERTS files. It would be great if our site could schedule Sierra to identify a specific list number and replenish or refresh the contents of it with most current system file's data. This would make the task fully automated. It's important to our system to be able to designate which list or review file number to use for each system-generated file job, however. We are a consortium and our…

    2 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. For some fragile items that we don't want to put in transit (e.g. telescopes, vinyl records), we want to be able to limit check-ins to the owning location. We can communicate these limits to patrons on our website and through signage or labels, but we'd like there to be an option within Sierra to generate a pop-up (with an option to override) so staff are alerted to tell the patron they have to bring the item back to another location.

    7 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. One of our branches uses shielded RFID pads, and the software could hook in to their previous ILS and context switch the current RFID action (tag on, tag off, no change) depending on the active function screen by overlaying a screen over the ILS to track the toggling.

    Can support for this functionality be offered for Sierra? I assume it would involve working with the RFID vendors to get it up and running.

    The current workaround is to use Sierra macros to trigger the RFID function change, but this is reliant on staff remembering to press the keys which may…

    2 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. Libraries have the option to use "Check-in: Do not fulfill holds". This checks in the item without without fulfilling any holds that are in the hold queue for that item. This item will never appear on a Title or Item paging list unless the item is checked in AGAIN. To be eligible to appear on a Title or Item paging list the item must be checked in a second time.

    We need an option to release that restriction. The hold should be unfulfilled only during that specific check-in.

    Reasons for this:

    1) Our transportation system may be stopped due to…

    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)
  13. When users return the materials via self-check machines, we want an email receipt to be automatically sent to them. Unfortunately, Sierra does not currently support the AA element in the 10 Checkin Response. Some libraries purchased the Patron API feature to get it to work but if Sierra include the AA element, it will simplify the process.

    3 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. With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.

    1 vote

    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. Currently, the notices for Current Checked Out Items allows for daily or weekly scheduling, but it would be handy to have the ability to set this at a longer time frame such as monthly, quarterly or by semester as most of our materials check out for much longer periods of time (16 weeks or longer generally), and some users find the weekly reminders tedious.

    Either the option to set the automated notices to a longer time period, or the ability for patrons to choose a longer reminder period (opt in to weekly, monthly, etc notice) would be very helpful.

    5 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. In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.

    As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2)…

    28 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. I had first suggested this over a decade ago when at another library that was struggling how to balance its combination of branch & research library users & the sort of requests they might make. While no longer there, I still see it as a potentially useful means for staff to develop their request processes & create limits within limits.

    What I'd like to see is the ability to not only set a hold threshold, but as is the case for the Max Items A-D allowed as applied to checkouts, allow a similar breakdown for holds.

    Optimally, this would allow…

    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)
  18. Passkeys are both easier for people to use and safer than using passwords and PINs. Passkeys allows users to sign in to their account using the same mechanism they use to unlock their device - fingerprint, face recognition, etc. There are a couple of good introductions to the benefits of Passkeys over traditional username/password credentials here:
    https://fidoalliance.org/passkeys/
    https://developers.google.com/identity/passkeys

    8 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. Sierra patron records should include a patron pronouns field, so that library staff can record customers' stated preferred pronouns and use the correct language in conversations and communications with customers. The field should be able to display in the Brief patron display. This step would help to support inclusion, wellbeing, and belonging in libraries.

    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)
  20. Can we get some new skins to choose from for the SDA/Sierra Web?

    There are currently two: Half Dome & Glacier Point.

    We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.

    Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?

    22 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?