Skip to content
Innovative Idea Exchange

ILS - Sierra

Recently Activity

ILS - Polaris Updated

Last In House Use column

Reporting & Analytics UNDER REVIEW

ILS - Polaris Updated

Automatic processing for item record details

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Patron block pop up

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Holds that can't be filled

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Volume-Level Holds for Blank Volume Field

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Live Preview Within Bibliographic Record Sets

Cataloging & Metadata Management UNDER REVIEW

ILS - Polaris Updated

Vendor integration

Customer Relationship & Account Management UNDER REVIEW

Don't see your product?

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

253 results found

  1. Sierra currently removes any leading apostrophe for example from the normalised author fields on bibs. For example, normAuthor over API. Other diacritics such as ʻokina (ʻ) is not removed from normalised fields. Because of this, any systems that use norm fields over API are not alphabetising the author correctly.

    It would be great if Sierra could remove the ʻokina (ʻ) from the normalised author fields. Specifically normAuthor.

    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. It can be useful to check the number of users in each group currently logged in to Sierra. In our case, there is a self-checkout group that should have a specific number of logged-in users throughout the day that requires monitoring.

    The number of users in each group logged in to Sierra over the course of the day is available by SSH (in Admin Corner, "Number of INNOVATIVE users by hour").

    Monitoring this information in an automated way is not straightforward. Admin corner can send an email, but only from an interactive SSH session. It is possible to automate an…

    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)
  3. Hello Everyone,

    We are currently using the GET /v6/bibs/search API to take advantage of the AWS search integration, which has been working well. However, we’ve encountered limitations in filtering the search results by Material Type, Collection, Language, and Location.

    It would be highly beneficial if this API supported additional filtering parameters to narrow down results at the source. Relying on the client or webhook server to apply these filters adds complexity and can introduce delays in presenting results to the end user.

    Thank you.

    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. We would like the ability for authorized/admin level staff to collectively shuffle multiple holds, so those at the bottom of the queue can be selected & moved to the top. Their order at the top wouldn't necessarily matter, as long as the group were all advanced in the queue.

    Use cases: item recalls, where tech services staff have to place dozens of holds on items, all of which wind up at the bottom of the queue & need to be shuffled individually/manually.

    Book club: we had a situation recently where staff at one branch cancelled holds on book club items…

    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)
  5. Column sorting in the Patron Checkout Limits table, such as sorting by itype/location type or ptype, would make it much easier to review. Since you can only append entries and not insert them, additions can result in a table where 1 ptype is in several different places. As it stands now, you have to import a new file each time to ensure the table is structured how you want.

    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. It would be useful to have CAS Apero enhanced to either:

    1. re-ingest the metadata automatically once the validUntil date is reached or

    2. have a setting to ignore the vaildUntil date.

    We are currently implementing OpenAthens which has a daily metadata refresh meaning the validUntil parameter is also changing daily.

    As Sierra cannot currently auto re-ingest metadata or be configured to ignore the validUntil parameter, we are currently hosting an edited metadata file on our web server (with a really long validUntil date) as a work around.

    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)
  7. The Transfer Paged Items function in Sierra will display one of two statuses when the report is run - Eligible or Ineligible. You then check or batch select the requests you want to transfer. But the results might mix eligible items wit ineligible items & there's no way to group them together to make the selection & transfer process easier.

    Adding the ability to sort by the Status column would allow us to select the entire batch of items eligible for transfer much more easily.

    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. Create the ability to extract attached media files in bulk from Sierra.

    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)
  9. Issue Description:
    At our institution, item record numbers in Sierra are either 8 or 9 characters long, including the check digit. We’ve encountered issues during import/export processes where 8-character item record numbers inadvertently match 9-character ones—particularly when the check digit is excluded—leading to data mismatches and processing errors.

    Proposed Solution:
    We suggest padding item record numbers with leading zeroes to standardize their length, which would help prevent unintended matches and improve consistency.

    Current Workaround:
    Our current approach involves separating items into two groups—those with 8-character and those with 9-character item record numbers—then importing them separately and merging the files manually.…

    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. There must be a configuration in Sierra to limit the number of holds can be placed at the bib level. We want to limit the hold count to number of copies in the Bib.

    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)
  11. We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope better indicator (e.g. color) so it would be easier to notice if personal login/permissions is added or not (or if someone has forgotten to remove their personal login/permissions). At this time when you open Sierra using the library login you can see "Sierra" and "local system name" on the upper left corner (in our case Sierra Helmet). When you add personal login your name (user account full name) will display too (in our case…

    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)
  12. 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)
  13. 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)
1 2 … 9 10 11 13 Next →
  • Don't see your idea?