Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

265 results found

  1. The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".

    Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.

    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)
  2. Our patrons are curious about their loan history. They would like to sort it by author or title in addition to the checkout date. We have told them to export it. But exporting the checkout history loses the checkout date! Could more sorting possibilities be added to the catalogue and checkout date added when exporting?

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

    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)
  4. Customers want to know what titles they've checked out even if the library no longer has it. It would be ideal if Sierra (and subsequent discovery layers can pull the info) could save the title and author in the record metadata so that even if the bib record is deleted, the customer can see it.

    21 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. Currently once an item is placed on hold, if the patron changes the pickup location after the item has already been paged for, the item will not be paged for again. With Title Priority Paging and “Prioritizing Hold Fulfillment at the Pickup Location” settings in place, this means a patron could be waiting much longer (depending on the “Pageslips: Number of hours before page can be transferred”) for their hold, even though they have fixed their mistake and reselected their intended pickup location. Additionally, even if the old pickup location pulls the item, they won’t be able to fulfill the…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Update the Sierra API to allow self-check out of virtual items. We use Bibliocommons app and our customers cannot use the self-checkout feature to check out INN-Reach items.

    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. Currently, on Sierra it is possible to block patrons based on overdue penalty points (OD PENALTY) when they check in or renew overdue items. This is done with the patron fixed field OD PENALTY. The system calculates the penalty points that have to be added to the patron record and when a patron exceeds the maximum number of penalty points allowed by the library, the patron is blocked. More info at https://documentation.iii.com/sierrahelp/Default.htm#sgcir/sgcir_fine_penaltypoints.html

    THis feature is very useful. Wouldn't it be a good idea to be able to apply a similar strategy for patrons that request a hold on a bib/item…

    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)
  8. We require certain information to create a library card, however Sierra does not enforce this requirement at the system level. Since it isn't mandatory, some data simply never gets captured and creates more work on the backend.

    Beyond that, having certain information in the record would allow us to build a better understanding of our usership so that we can make better decisions as an organization.

    I especially would love the ability to require any and all of the fixed-length fields; especially patron category, birthdate, home library, and notice preference.

    16 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. Currently Decision Center only returns data for a location parameter if there was activity for the selected time period and does not return a zero placeholder for locations without activity. This creates extra work for staff when working with the resulting Excel files. They can't easily reference the cells in Excel consistently.

    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)
  10. When creating a new customer record from scratch, or when updating & finalizing those submitted through our online application, we have staff perform some checks to prevent duplicate records.

    They'll begin by searching the Name index to make sure that there's no pre-existing record for the same name. Then as backup, they'll try searching by birth date or phone number.

    However, when you search by birth date or phone number, the results do not come back in alphabetical order, making things a bit harder than they should be for frontline staff. See example image where the search for the DOB…

    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. When exporting MARC tags, export should have all the subfields marked. Now that I try to export say 041, I can´t see if the language code is in a, b or d... And this would be important to know as it is not the same to have say |a fin |h eng and |a fin |a eng.

    13 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. At present, we can only see the full name field in get patron endpoints. For some systems that connect via api, it would be highly beneficial to have other fields available relating to patron information. For example, separated first and last names.

    This is due the some systems relying on the information it can read from Sierra and not process further to define a first name.

    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)
  13. Our homebound customers love the Sierra reading history functionality, but tell us that they do not want the Library to give them a checkout receipt that includes an option to rate the title. They also tell us that they do not want their personal information on the receipt (and the library cannot edit the Homebound receipt template).

    Additionally, circulation staff workflows are hindered because if a stack of homebound items are returned, they have to use the keyboard / mouse to move past the checkin rating prompts.

    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)
  14. Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.

    The patron API cannot do this - blank values are rejected as invalid JSON e.g.

    {"expirationDate": " - - "}
    {"expirationDate": ""}
    {"expirationDate": "--"}
    {"expirationDate": "null"}

    All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.

    Enhance the API to accept a blank value in expiry date.

    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)
  15. We can’t use this button because we don’t use print templates for our bills.
    We would prefer them to look pretty with Print Templates instead of the plain text we currently have. To avoid staff confusion, it would be great if this we had the ability to disable/grey out this button.

    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)
  16. https://ideas.iii.com/forums/951745-ils-sierra/suggestions/46670854-sierra-5-5-direct-view-public-display-to-disco is closed/says it's already supported, but the part for being configured to more than one display option is not addressed. We would like to be able to have more than one option to display - Vega, Classic, Encore and even III Mobile if possible - so we can see how all iterations look right from the SDA. So in the menu it would be View | Public Display | array of choices

    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)
  17. We frequently have the unfortunate situation where staff accidentally delete their paging list from the list of Notices. Ideally, we'd prefer that frontline staff be able to prepare, print, & fulfill their paging lists but not be able to delete them.

    Separating authorizations to create/edit/delete these lists from the preparation & printing would save support staff a great deal of time spent recreating these lists & remove some of the potential for frustration & confusion among frontline staff.

    45 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. There are two things we would like to see in the Mark Damaged Items process. First we need a separate notice text for damaged items. We are trying to differentiate between lost and damaged and having to use the same notice text is problematic. Second, we'd like the status after the bill is paid to be Damaged & Paid (just like Lost & Paid) instead of just Damaged, as staff can't tell if this is an initial damaged status or one that has been paid for. These are handled differently and being able to create a list, for example, of…

    45 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: create a new status that references a scheduled booking for an item.

    Value: Currently, Sierra does not change the status of an item that has a scheduled booking. When using the API to reflect the status of an item on a catalog, the item will show as status - (On Shelf) even though the item is not available because it has a scheduled booking for that time. This makes it seem as if the item can be scheduled for a specific time when it is already booked. When an item has a booking, changing the status to "Booked" when…

    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)
  20. We see the Sierra 6.0 Release Notes features new Accessibility improvements in the SDA. It is unclear if this includes a high contrast display option which staff recommend to support use of the software by many different types of staff.

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