Skip to content
Innovative Idea Exchange

ILS - Sierra

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

294 results found

  1. Our library has very generous allowances for both checkouts & holds on patron accounts. This can sometimes come into conflict with Sierra's seemingly arbitrary system limits. For example, when these items go unreturned & result in replacement charges, which then cannot be added because of the imposed limits. Like my waist can no longer accommodate 32" pants, Sierra cannot currently accommodate the lending policies taken advantage of by some of our more active borrowers.

    I'm sure there are other examples where these limits can manifest, but attached is an example message recently seen by staff which reads:

    CANNOT ADD FINE…

    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)
  2. For testing purposes, it would be beneficial to be able to make a backup of a patron PIN, assign a new temporary PIN, perform the testing from the patron's perspective, and then restore the original PIN. This way we would not have to inconvenience the patron by asking them to reset their PIN when testing has completed.

    We can retrieve the encrypted PIN with this API GET request:
    https://library-app-server:443/iii/sierra-api/v6/patrons/patron-record-number?fields=varFields
    but the PIN string will be re-encrypted if we attempt to write it back using the patron record PUT request. We would like to have the option of passing a directive…

    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)
  3. When users return the materials via self-check machines, we want an email receipt to be automatically sent to them. Unfortunately, Sierra does not currently support the AA element in the 10 Checkin Response. Some libraries purchased the Patron API feature to get it to work but if Sierra include the AA element, it will simplify the process.

    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. Similar to the keyboard codes (ex. %ENTER%), it would be useful to have a command code for today's date. In item records, we input the current date in a 995 field using a macro but must update our date macro each day. Being able to have a command for the current date would save time and lead to fewer errors when users forget to change the date.

    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)
  5. When using Manage Holds, information about any recalls that have been issued for items on hold is not displayed.

    This information can be found by consulting the item record (right click, "Edit item", then open the item) and checking for a "Recall Date" value, but it would be very helpful for us if this information could be included directly in the Manage Holds results. For example, the "Hold Status" column could include indication of recalls to provide a fuller picture of the situation at a glance.

    This idea could be incorporated in work on the following related suggestion:
    https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48633872-improve-standardize-information-available-when-vie

    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)
  6. Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.

    The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.

    As-is, the "Selected Databases" dialog can be dragged wider by the…

    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)
  7. 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)
  8. 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)
  9. An option for Sierra to notify the library of new ILL requests via email rather than a staff member manually checking the new requests function.

    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)
  10. There is currently no way to update the status of a hold in the API.

    It would be very useful to change the status from

    "status": {
    "code": "0",
    "name": "on hold."
    },

    to

    "status": {
    "code": "i",
    "name": "Requested item ready for pickup."
    },

    Enhancement to be integrated into https://ideas.iii.com/forums/951745-ils-sierra/suggestions/47618129-it-s-about-time-to-make-holds-apis-first-class-cit ?

    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)
  11. We'd like the ability to be able to attach a volume record from the Serial Checkin module. This would save time and make the serials module more useful.

    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)
  12. We would like to have a collection summary report based on item records with a count by item type and location. If possible, adding a limiter for circulation status, for example on shelf or checked out.

    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. In the SDA OR Sierra Web, the Sierra 2-tier login workflow allows administrators to set a "time-out" setting to the 2nd tier (personalized) login. This setting determines if the session will time out or close after a specific amount of time.

    This is an excellent workflow except that there is no setting to manage 1st tier inactivity. This means at the end of the day we have many Sierra licenses that remain open and the Library must manually force close the desktop applications using the "restart a process" in Admin Corner.

    Please configure context logins so that Libraries can determine…

    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)
  14. The Innovative_Footer token for webopac does not have any CSS styles or identifiers associated with it so that it can be controlled through stylesheets. The footer is inappropriately placed on our website due to this lack of control.

    Propose adding identifiers to the underlying HTML code so that it can be styled properly. Replace its <span> tag with a <div> tag might be appropriate.

    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)
  15. Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.

    Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a…

    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. Sierra supports Z39.50 but not SRU. Remote search and import/overlay of records from SRU-only sources seems to be increasingly important. We have begun to encounter potential partners who are no longer able to offer Z39.50 access because their systems only support SRU; likewise, we would like to be able to offer SRU ourselves to maximize interoperability.

    GPL-licensed software is available to add SRU support to Z39.50-capable systems such as Sierra (for example, CQL-Java, yazproxy and metaproxy):

    https://www.loc.gov/standards/sru/
    https://www.indexdata.com/resources/software/cql-java/
    https://www.indexdata.com/resources/software/yazproxy/
    https://www.indexdata.com/resources/software/metaproxy/

    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)
  17. With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.

    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)
  18. 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 faster way to change the user. At this time you must first remove previous user (Admin - Clear Permissions) and then add new user (Admin - Set Permissions). Staff suggested one function that would both Clear previous and Set new Permissions. E.g. Set Permission could remove the old user and then ask the new user. We set up macros for both functions so staff can use them instead of drop-down menu. However, I suppose…

    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)
  19. Currently Sierra permission 109, update uncataloged records, is tied to whether or not the bib record has a CDATE (no catalog date) field. It would be great if permission 109 could be customized by a library to be controlled by another option outside of just the presence of the CDATE field. For example, we use field 31 to control the level of cataloging of a record (including full MARC) and to suppress the bib. It would be helpful if we could tie the codes from that field to this permission. It's worth mentioning that permission 109 and the presence of…

    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)
  20. This is two fold. First, we would like to be able to set a default printer option determined by the staff users workflow (circulation workflow/function would default to "email to patron", and cataloging function would default to local printer, etc). So staff log in and select their function area and the system uses a specific printer default accordingly.

    Secondly, we would like to have the "Send to email address" printer option changed somewhat. When selected, it would have a drop down of emails available to send to. These would be set up by the system admin. It would reduce the…

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