Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

294 results found

  1. I know its shocking when the subject of pop-ups in Sierra comes up that anyone would want "MORE!," but our Acquisitions staff would like to see a warning of fund spending over limit at invoicing in addition to ordering.

    Their rationale is that shipping & Mylar costs usually cannot be pre-determined. Once posting happens, the fund goes negative. Since there is no going back, like when you're about to go down the chute at the end of Splash Mountain, there should be a warning.

    8 votes
    How important is this to you?
  2. The automated tool employed by Clarivate support to update iii and iii-root passwords every 30 days has an 8 character limit, which falls short of PCI requirements (15 characters). The Sierra application server, which hosts the web page connecting to PayPal is in scope for PCI, and therefore login credentials that can edit that web page need passwords of 15 characters or more.

    8 votes
    How important is this to you?
  3. It would be nice to have more control over Sierra pop ups. Like if you are checking in a large amount of items it is really annoying to click ok every time the item is set in transit - you most likely already know these items are going in transit!

    Also when creating a library card it would be good to be able to set a pop up "are you sure you wish to save a library card without (for ex) PIN code"? Sometimes you don't need that, but that is really rare.

    8 votes
    How important is this to you?
  4. When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.

    If you opt to change that setting however from the record view properties menu (say to change this to view all) it can impact all 4 search functions. It would be better to split this menu out, so that the setting for each…

    8 votes
    How important is this to you?
  5. Libraries with varied types of media in their collections require more location information associated with items than a shelfmark. We would like to see a Current Location field as standard in the item record. This field must be included in the data libraries for item paging notices as retrievals staff will need this information on retrievals lists/slips.

    Idea Value
    To record the exact location of items within the buildings, which will facilitate retrieval of less standard items or special collections items that are not easily stored in a standard sequence. Current location data is essential for museums accreditation.

    8 votes
    How important is this to you?
  6. We use the hourly patron borrowing reports in Web Management Reports to track patron visits at offsite hold lockers. We would like to have this report migrated to Decision Center since this is the tool already in use by our frontline staff.

    8 votes
    How important is this to you?
  7. I am wondering if Sierra can be adapted to automatically insert name, date of birth and address using an id scanner, such as those used at grocery stores when verifying a person's age. This would save staff the time of manually entering this information into the appropriate fields. It would also allow less typos and/or other mistakes when inputting the information. Of course, having the manual option would still be necessary.

    8 votes
    How important is this to you?
  8. Data in the hold_removed table is being deleted before the 60-day retention period is up in situations where staff clear the hold shelf, and an entry in the hold_removed table is indicated to be "picked up". This is unexpected and not helpful in the task of gathering more data related to holds.

    I propose the following changes...

    1. Retention Period: Entries are being removed from the hold_removed table before the default 60-day retention period is up. I propose that data should remain in this table, as it represents the lifecycle of a hold and the recorded event that removed an active…

    8 votes
    How important is this to you?
  9. Currently patrons can opt in and out of Reading History our public catalog (Bibliocore) but we get many requests from patrons who want to manage that reading history by removing items from Reading History but the RESTAPI doesn't allow users to do that, they have to log into their accounts on WebPac in order to manage the titles in that history. We would like to see full Reading History management currently available in WebPac added to the RESTAPI.

    8 votes
    How important is this to you?
  10. Customers still want staff to place bib level holds for them at the circulation desk. In checkout it is fantastic that staff can search the catalogue to place holds, but they often don't want to view every bibliographic record before placing the hold.

    Customers asking for assistance at the circulation desk often have complex needs. They are looking to place holds on a number of titles within a series or they found the Discovery Catalogues did not meet their needs.

    It would save staff a lot of time at the circulation desk if they could place holds on the titles…

    8 votes
    How important is this to you?
  11. In order to make webpac can link to the LC Name Authority File,
    it is needed to separate the link of MARC 100, 110, 600, 610, 700, 710.

    For example : https://cylis.lib.cycu.edu.tw/record=b3104334
    Separate the AUTHOR name link
    "Hull, John, 1946- author. http://id.loc.gov/authorities/names/n88011278"
    to "Hull, John, 1946- author." and "http://id.loc.gov/authorities/names/n88011278" .

    And then patrons can click the url "http://id.loc.gov/authorities/names/n88011278" to see the LC Name Authority File.

    8 votes
    How important is this to you?
  12. The Notice Type data field in the Text of Circulation Notices table is a mere 20 characters long. As we've had to create a number of new notices for temporary changes in operating hours, policies, etc., due to COVID, we'd like to make the description a bit more descriptive than 20 characters allows.

    Also, because you cannot delete any of the old/test notice types, you already have to use up some of the characters to note that it's old/test/not used.

    This runs along the same lines as Loan rules: increase the limit beyond 20 characters to loan rule names. This…

    8 votes
    How important is this to you?
  13. We would like to see more granulated permissions for user administration, especially with assigned permissions, settings, options, workflows, etc.

    We would like the ability to assign a particular group of user accounts (e.g., circ student employees) to a specific admin (e.g., head of circulation) without assigning ALL system administration. It would be helpful for troubleshooting and having this department be able to assign macros, specific permissions, and print settings to different accounts.

    Ideally, this "group admin" would have the ability to edit settings on accounts for options, settings, and workflows. It would be great if they could clone and create…

    7 votes
    How important is this to you?
  14. It would be helpful to have the ability to prevent a hold from being canceled based on its pickup location.

    We have holds pickup lockers installed in three locations and are finding that if the lockers contain an item which has since had its hold canceled, the lockers will send a CheckIn SIP transaction to Sierra for that item, resulting in the item being [logically] used to fulfill someone else's hold [while physically still housed in a locker]. For popular new releases, this is happening more frequently than one might imagine. The ability to disallow the cancellation of holds at…

    7 votes
    How important is this to you?
  15. Because our library does not use fines, having the "Failed to acquire fines payment lock. If not cleared, fines payments cannot be processed" message is of no utility for us. We'd love multiple users to be able to view a patron record without this message showing up.

    7 votes
    How important is this to you?
  16. It would be nice if there was a setting in the Receiving function to limit your search to only items available to be received. We search by PO and have to wade through loads of items already received and billed. This was available years and years ago on the old Horizon system.

    7 votes
    How important is this to you?
  17. 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…

    7 votes
    How important is this to you?
  18. 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.

    7 votes
    How important is this to you?
  19. 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
    How important is this to you?
  20. 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.

    7 votes
    How important is this to you?
  • Don't see your idea?