Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

41 results found

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

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

    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)
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. 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.

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

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

    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)
  11. The Item Code 1 field was going to solve all my statistical issues. I thought it had 5 characters and each character could be 0-9 which meant I could assign a meaning to each character. For example, the first character indicates agency (1 for CPL, 2 for ADL, 3 for BKM) and the second character indicates audience (1 for adult, 2 for young adult, 3 for juvenile, 4 for other) and the third character, format, etc. HOWEVER it turns out that the largest number this field can hold is 32767 which is weirdly random and very limiting when you want…

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

    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. Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.

    The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.

    As-is, the "Selected Databases" dialog can be dragged wider by the…

    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. I understand that III is planning to incorporate AI functionality into the Vega platform (newsletter text, website content, etc...). I think it would be really useful to have AI data cleanup functionality developed for Sierra.

    I'm not sure exactly what this would look like but here are some potential ways this could improve catalog metadata:
    - catalog record cleanup (bad codes, incorrect codes, codes inconsistent with local practices for similar records, etc...)
    - patron record cleanup (bad codes, codes inconsistent with similar-type accounts, etc...)
    - automatic tagging of demographic (we use one of the patron codes to indicate reciprocal library…

    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. In Headings Reports, it would be useful to send only selected listings to a printer or to export as a new review file. Currently if you try to select only a few of the total shown, it will print or export the entire report, not the selected listings.

    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)
  16. Searches of Innovative databases that contain authority records using Z39.50 search do not return authority records.

    The ability to search for an authority records would contribute to the quality of the database and make it easier to generate linked data.

    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)
  17. There are instances where its appropriate to put in a MARC field in the bibliographic record that only pertains to your local institution and you wouldn't want that field erased if the record was overlaid. If that MARC field was designated a local-note, using a $5 then that field would be "protected".

    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)
  18. Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.

    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)
  19. Idea Description
    If system generated review files could appear in Global Update/Rapid Update Review File dropdown list without even downloading them to Create Lists first that would save so much time.

    It's a normal part of my daily workflow to upload records using Mobile Worklists or Data Exchange, copy them into Create Lists and manipulate the file in Global or Rapid Update. 

    Idea Value
    With the file appearing in the dropdown list in Global/Rapid update, the file can be manipulated as usual AND users wouldn't have to remember to empty the Review File (which was only created so it could…

    32 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. Idea Description

    Create tools for managing the hidden review files that are created by the system or record loading.  Being able to see the list of hidden review names, record numbers, dates, would be great for system housekeeping.  Being able to bulk delete the review files many of which are from record loading would be even better!

    Idea Value

    This idea would go a long way to helping system administrators clean up the review file section of the system.  The currently method of having to copy them is clunky at best.  Deleting them one at a time is even clunkier and…

    34 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
  • Don't see your idea?