Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

251 results found

  1. Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.

    We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.

    Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.

    This…

    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. Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.

    We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.

    Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.

    This…

    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)
  3. A "last status update" column in the low & high circulation weeding report results would help identify items for weeding or stock rotation.

    Why would this field help us weed or identify items for stock rotation?
    This item field identifies the last date an item changed their status. Many libraries change an item's status to "in transit" when they move an item from one branch to another. To that end, this field could help identify items that have either newly been received to a branch, or have sat on the shelf for some time.

    Items moving around systems with stock…

    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)
  4. When an item lacks an ISBN in the 020 field (DVDs and CDs only generally have UPCs in the 024 field) the cover image is very much hit or miss. Syndetics has been contacted, however, it appears that Sierra needs to "pass the UPC code” in order for this to work. This addition would be helpful.

    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)
  5. Intergrating Sierra with IMMS, Sierra does not show the placement information from IMMS on item records. In particular, when the items are stored in chaotic placements such as hold shelves. This means that looking for an item on a hold shelf or other chaotic type location in Sierra, the user has to copy the barcode from Sierra to IMMS to pin point it's known location.

    With further integration, it would be great to see placement information in Sierra to assist staff with helping customers find items on hold shelves in particular.

    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. Problem:
    In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:

    • Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.
    • Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.

    • Recommendation:
      Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra…

    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. Our branches select which items should be sent to another library for stock rotation. Before items are sent to another branch, staff change the item statuses to "in transit". For various reasons, the branch staff cannot use Mobile Worklist to batch change these items to "in transit". The staff use Circa, but would prefer a Sierra integrated solution.

    Why integrate this solution in Sierra:

    • Circa is aging out. We cannot limit Circa permissions to only change Item status to "in transit".

    • We want to use the "item status update date" to track when items last moved to a branch.

    • We…

    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)
  8. 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…

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

    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)
  10. 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…

    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)
  11. In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.

    Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of…

    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)
  12. Make it an option to also include the item cost in the overdue notice as well (incentive to return!).

    In our date due slips (JasperSoft) we include the cost of each item and a total cost to show what the patron saved by using the library vs. buying.

    51 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. Persistent Column Resizing in Summary Tab:

    Currently, users can resize columns in the Summary Tab (Orders, Items, and Holdings) during a session. However, these adjustments are not retained after the session ends, requiring users to reapply their preferred column sizes each time they log in.

    I propose an enhancement to allow users to permanently save column resizing preferences across sessions. This feature would greatly improve usability and efficiency by enabling a more customized and consistent interface tailored to individual workflows.

    This enhancement would benefit users who frequently manage data within the Summary Tab by reducing repetitive actions and ensuring a…

    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)
  14. Do you want all of your patrons to receive due slips by email, every time they check out an item?

    Express Lane can be configured to automatically print a due slip, or allow patrons to choose between some combination of print or email due slips with an option to decline, but cannot be configured to automatically send an email due slip with no option to decline.

    In our special library, it is desirable to always send email due slips with no option to decline. We want our patrons, who are all employees, to receive this documentation for every loan for…

    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)
  15. In Sierra, on Windows 11, when you click "Tile Vertically" so you can see multiple records at the same time, it makes the windows too long, so that the bottom of the windows get hidden behind the taskbar if it is locked. It does not do this if you maximize a record window, or if you use snap. It only seems to be the "Tile Vertically" function.

    We use this function a lot to compare records for deduplication, and it is really annoying to have to manually resize windows so you can see the whole thing.

    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. When matching on an ISBN for record loading, it should be possible to limit the match to the first 13 (or 10) digits. There are often extraneous data in 020 subfield |a. There are now other subfields where that is supposed to go, but it frequently ends up in |a anyway, and then your record loading won't match.

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

    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)
  18. Improve diacritic searching in Sierra to include Semitic languages, especially Arabic! We have a fair number of Arabic books in out collections, and a large Arabic community, but Sierra support for Arabic characters does not seem complete. We often find that Arabic letters in Sierra is replaced by a white square, which seems to mean that the character is not supported. The names appear fine in Vega but the non supported letters do not seem to be indexed in the search results. This is an important language for members of our community and support for it is important in our…

    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)
  19. Add the ability to suppress subfield 1 in the 1xx field so it will not show in Sierra. This way it can be unsuppressed when the library starts using linked data.

    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)
  20. Our catalogers would like the option when choosing a field and selecting "Move to Bottom of Group" that it could go to the bottom of the list of numbered tags it is part of instead of the field name of tags. An example is moving a 5xx field to the bottom of a list of other 5xx fields, and not to the bottom of the record if there is an 852 (also a note) field.

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