Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

241 results found

  1. Support team told us Sierra isn't designed to supply hold request date for cancellation notices. Please consider add it. thanks

    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)
  2. Freezing (for patrons) and NNB (for staff) should be combined to one unified functionality so that frozen holds could be managed by patrons (WebPAC/Encore/Vega and third-party solutions using REST) AND by staff (Sierra Circulation). There are a few related ideas (and I commented them) but I think the main problem is that the function is not the same for patrons and staff. So I'd probably like first to remove NNB and replace it with just freeze/unfreeze on Sierra side too. (After that think about the additional options such as thaw date and freeze even if items available.)

    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)
  3. In mobile worklists the count use feature does not currently use the stat group associated with the login and defaults to stat group 0. Innovative can configure mobile worklists to use a different stat group, but it's a system wide setting so currently in a multi-location system there is not a way to accurately measure daily usage stats across different locations.

    The system should be updated so that the login's stat group is recorded to the circulation transaction table, as it is currently capable of doing with checkouts and check in transactions performed through mobile worklists. This will allow for…

    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)
  4. When a tickler has invalid data in the "Date (YYYYMMDD)" field, Sierra's nightly tickler process will fail and any ticklers on order records not already processed will not be sent. This failure will keep happening every night until the problem is discovered.

    For example, dates entered with dashes separating the elements ("YYYY-MM-DD") or with additional characters following the date ("YYYYMMDD - Note text here") will cause this kind of failure.

    In the absence of an easy way to search for invalid data in the tickler date field (e.g., Create Lists), it would be very desirable for Sierra to validate user…

    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)
  5. 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.

    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)
  6. We're currently dealing with a known issue in Sierra 6.2, where volume holds aren't being added to paging lists. Having discovered it on our end fairly recently, we've asked staff to continue running their paging lists for other items, but use the Manage Holds function to find & fill volume requests.

    The problem is that the current search retrieves such a high number of items. And while the search results display counts of the title number of holds, & the total number of bib, volume, & item level holds, you cannot currently limit them & make the Manage Holds report…

    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)
  7. We repeatedly run up against our limit of saved searches in Create Lists. There are probably saved queries created long ago that no one is using/needs. I was hoping to assign staff to review the queries and put their initials in the saved search name, but when you go to Edit, you can only edit the query, not the query name (like you can a review file). Ideally it would work like the review files themselves, when you can see who last ran the list (initials, date and time). And perhaps apply the "Own" option. This would really help to…

    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. We are looking at maximizing the potential for RFID as it relates to inventory & using Mobile Worklists to do so. I know that the scanning of individual tags to update the inventory date was introduced in 11/23 for MW 4.6, but this would mean having the capacity to scan tagged items in batch determined by the capacity of the tag reader with a wand or device like the one pictured, & have their inventory dates updated directly, rather than having the scans stored to an SD card & then uploaded/updated via Rapid Update.

    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)
  9. 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.

    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)
  10. Technical Services Staff and Circulation Staff often ask for the ability to toggle between tabs in Check Out. We need to reduce repetitive keyboard strokes at checkout and this workflow requires staff to continually reach for the mouse during a circulation transaction.

    For example: There is no way to move from the patron check out screen to the patron holds screen without using the mouse to select the corresponding tab.

    The Check Out options (check out, checked, out items, holds, fines, check in, linked patrons, bookings etc) could be hardcoded to the drop down menu options so that Administrators could…

    4 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. Circa is a web application running on the main Sierra's webserver and is available from anywhere that https is available, yet it still only supports legacy Sierra only staff accounts and not SSO via SAML. Changing all staff login functions to require SSO and disabling legacy Sierra only account support is an important step towards Sierra being a secure ILS at the enterprise level. Not supporting SSO creates extra burden on staff by requiring another password, removing the ability to enforce strong authentication, and adds extra account support costs for a busy and non-technical team.

    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)
  12. 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.

    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)
  13. Sometimes the CAS login to Sierra fails. Either the page is inaccessible, or we see an LSE-OA-Error-2 from our use of OpenAthens authentication to Sierra. The only solution available is to us is to reboot the Sierra application server. This is inconvenient since staff have to log out of their activities.

    It would be useful if there was an option in the Restart a Terminal section of Sierra to restart the CAS service. This would hopefully clear up the error and not require a server reboot.

    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)
  14. When using Manage Holds, information about any recalls that have been issued for items on hold is not displayed.

    This information can be found by consulting the item record (right click, "Edit item", then open the item) and checking for a "Recall Date" value, but it would be very helpful for us if this information could be included directly in the Manage Holds results. For example, the "Hold Status" column could include indication of recalls to provide a fuller picture of the situation at a glance.

    This idea could be incorporated in work on the following related suggestion:
    https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48633872-improve-standardize-information-available-when-vie

    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)
  15. Sierra does not preserve any applied sorts after a "Notices Job" Edit dialog is closed. Instead, jobs are re-sorted by job number. This makes it difficult to keep track of which jobs have been reviewed, and generally contributes to unnecessary frustration in the Notices function.

    This improvement is related to "Arrange Saved Notice jobs" suggested by Kathy Setter, but instead of applying a custom arrangement I am asking for persistence on a short-term basis:
    https://ideas.iii.com/forums/951745-ils-sierra/suggestions/46677958-arrange-saved-notice-jobs

    Rationale:
    When making changes to multiple notice jobs at once, it is often necessary to sort notice jobs (e.g., by template, location, or "auto") to…

    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)
  16. The Time to Holdshelf feature in Sierra is useful in keeping patrons from showing up too early to pick up their holds. As seen in the attachment "Discovery Layer View" – which in our case happens to be BiblioCore – the availability status correctly reflects that the recently checked-in item "Easter Mice!" is not ready for pickup because the item is en route to the pickup location (which in this case is a set of freestanding pickup lockers in a remote area of the county).

    However, the holds status as displayed in the SDA incorrectly reports the item as being…

    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)
  17. Currently, authentication using the NCIP protocol does not update the CIRCACTIVE attribute in the patron account. We use this protocol to authenticate to a statewide ILL service and we'd like to know when cards are being used in this union catalog and not just our own.

    We use CIRCACTIVE to determine which cards are being used and which ones aren't. This is useful for statistical purposes, but is also linked to our patron database purge 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)
  18. As a default suppressed records are not included in the harvest stream. This becomes an issue when a harvested record later becomes suppressed in Sierra as the harvester does not know to remove it from its listings as its omission from the stream does not allow for identification of its suppressed state. I would recommend that the option to include suppressed records should be configurable as a harvest stream level, giving the library the ability to configure the inclusion/exclusion dependent on their business rules.

    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)
  19. I just learned that Scheduler Output MARC records can't send an FTP password that includes the characters [{}"/

    It will let me save a task with such a password and spend months trying to figure out what's wrong. If it can't deal with a particular password, it should give an error saying what's wrong with the password.

    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)
  20. We currently have staff at a number of branches testing Mobile Worklists. More than one location has requested the ability for users to increase font sizes for displayed characters in title paging lists & elsewhere throughout the app. Hopefully this could be tied to their login, so settings are not constantly in need of a reset between users of shared devices.

    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)
← Previous 1 3 4 5 12 13
  • Don't see your idea?