Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

6 results found

  1. In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.

    This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.

    Suggested improvement:
    Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQ

    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. Organizations with restrictive security policies may be unable to use FTP over port 1021 (or any other port) for file transfer to Sierra WebPAC, since FTP is an inherently insecure protocol. For the same reasons, FTP should ideally not be in use at all (even where permitted by the customer's organization) since it entails sending login credentials in cleartext which makes it subject to interception and abuse.[1]

    Without FTP, the only alternative is to use Web Master within Sierra Desktop App to upload files to make changes to Live or Staging WebPAC screens.

    If Innovative implements Secure File Transfer Protocol…

    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)
  3. A lot of alt tags appear empty by default and other accessibility issues seem to be outstanding. These two are examples that cannot be corrected by admins.

    Add relevant tags to improve the accessibility of the search results page briefcit.html. The search box form has no labels that can be read by screenreaders:

    Element Location: #searcharg

    <input type="text" name="searcharg" id="searcharg" size="30" onchange="return searchtoolSubmitAction()" maxlength="75" value="[search term]">

    The search history select element has no accessible name:

    Element Location: .navigationRow[align="center"]:nth-child(5) > form > select[name="HISTORY"][onchange="onSelectChange(this, '')"]

    <select name="HISTORY" onchange="onSelectChange(this, '')">

    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)
  4. We implemented Patron SAML and uses a patron variable field to be the matchpoint. This field contains the patron's email address. Our IdP accepts dots, dash and underscores in patrons' email address. Due to Sierra indexing rules where symbols (including dots, dash and underscores) will be dropped, different patrons with the same letters in their email address but have different symbols in different positions won't be able to authenticate through Patron SAML.
    e.g. Patron A's email = abc.def@test.com, Patron B's email = abc_dec@test.com . Both will fail authentication as Sierra will use abcdef@test.com and return both patron records.

    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)
  5. Libraries should have the option to exclude frozen holds from the total holds queue that appears in any catalogue.

    Benefits:

    1) Customers will have a better idea of where they are in the hold queue.
    We encourage customer-driven hold management, and customers have told us that they want an estimate of when their holds will be filled.
    This is especially true when customers place multiple hold on titles within a series.

    2) Customers will not see inflated hold queues and provide feedback to the Library that they should purchase more copies.

    3) Customers could make an education decision on whether…

    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)
  6. We've had a couple of instances where the Encore 'Did you mean?' suggestions have offered up inappropriate alternatives to the search that was performed.

    The first example was that it suggested 'sex manuals' when a search for 'car manuals' was performed.

    The second example was that it suggested 'American poets' when a search for 'African poets' was performed, to which our client took offense at.

    We would like to see some functionality added to Encore that would allow us to customise what suggestions display and what do not display for the 'did you mean' algorithm. This would allow us to…

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