Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

28 results found

  1. Display the date that an item's status was last updated and make this field available in a SQL view.

    Idea Value
    We'd like to be able to create reports that show how long an item has been in a certain status so we can take appropriate action (such as deleting long-missing items). Currently, we can only see the last date the record was updated, but the record may have been updated in some other way after the status was changed.

    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

  2. At the end of the year/before we open on January 2nd, we have to manually zero out the YTDCIRC and replace the LYRCIRC with YTDCIRC. Besides being time-consuming if you have a lot of records, this process also then changes the last updated date of the item record, which makes that date less helpful, especially for missing, lost, etc items. This should be done automatically, and it should not change the last updated date of the item record.

    85 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

  3. When you create (a) new item(s) while cataloging -- or create any records actually! -- the pop-up that guides you to enter the data step-by-step should have a back button. Currently, if you make a mistake and click Next you either have to cancel and start over or keep going and fix the mistake on each item record individually after saved/completed. It can be quite tedious when you are adding multiple items at once.

    Idea Value

    Save time! What would just take a few clicks/seconds to fix can sometimes mean a lot more time, especially if you Cancel and have…

    56 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

  4. Often times when items are moving from one call number to another, holds are placed on the items that are checked out in order to capture these items when they are returned so that any cataloging work can be done.

    The idea is to have an option to have some way that multiple item level holds can be placed on one bib record at the same time.

    Idea Value
    The value of this idea is staff time. By having to place individual holds on each item, this can take a long time when there are multiple copies of an item…

    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

  5. In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

    Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

    Idea Value
    This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

    As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..."…

    17 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

  6. Even if III isn't able to provide a full-fledged editing interface for Load Profiles, add a mode in which we can view Load Profiles and Put PC to back them up. That's so much easier than having to setup FTP to the site, which our IT prohibited when I first gave up on it. This should apply to both m2btabs and m2bmaps.

    Idea Value
    Make it possible to backup load profiles on PC, which would enable much easier documentation of the variety of load tables and maps, and the load profile menu.

    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

  7. The patron record payment lock time should be reduced or have the ability to be overridden. Four hours is an excessive amount of time for a record to be locked. If a patron record is open for more than, say, 15 minutes (or even 5 minutes), the other session is probably not in the midst of making a payment.

    Idea Value
    Patron record locks are unexpected and embarrassing for staff that encounter them when the patron is in front of them wanting to pay or have a fine, fee, or other charge paid or waived. The patron is confused and…

    37 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

  8. The Load Tables are a critical point for any data management of a library. While many functions and features have been migrated from character-based system access to web access or within the SDA, this feature has not changed. Programming with what seems like a unix-based editor reminds me of the "dark ages" of programming.

    Idea Value
    Many times the syntactical error or omission of a line in my load table editing sessions happen because of the UNIX-like environment where editing takes place. Increased modernization of the editor would streamline the process.

    33 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

2 Next →
  • Don't see your idea?