Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

67 results found

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

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

    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)
  4. Improving universal accessibility features for users/employees with diverse accessibility needs.

    For example, for employees with visual impairments :
    - High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.

    Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.

    Even just the high contrast would help a lot. Additionally, it would be helpful if users…

    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. Our consortium would like an automated way to update the encoding level to help with managing load profiles that use the encoding level priority function. It would be very helpful to add an API endpoint for updating all the MARC Leader fields. The 008 MARC field can only be used for updating some of the Leader fields.

    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)
  6. Currently the only hold parameters one can modify via the API are

    PatronHoldPut {
        pickupLocation (string, optional): the hold's pickup location code,
        freeze (boolean, optional): whether the hold should be frozen (suspended)
    }

    It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters.  There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.

    Having this functionality in an API endpoint would permit a…

    7 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. Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.

    Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is…

    8 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. Each week staff go into Create Lists and repopulate a designated review file with current data from a system-generated list. Two examples of system-generated lists include the OVERDUE ITEMS and PURCHASE ALERTS files. It would be great if our site could schedule Sierra to identify a specific list number and replenish or refresh the contents of it with most current system file's data. This would make the task fully automated. It's important to our system to be able to designate which list or review file number to use for each system-generated file job, however. We are a consortium and our…

    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. Our library wants to provide the patron validate role to our vendors.
    But, we do not want to give the vendors any read or write roles.

    We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.

    Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.

    Why add this feature?
    Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor…

    15 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. I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.

    For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they…

    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. This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or…

    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)
  12. This idea came from a discussion at the IUG2025 Sierra Reporting Forum.

    It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to…

    20 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. Keeping our systems secure with SSL certificates is essential. Certificates need to be renewed and there is a service commitment to handle this process. But there is a better way. SSL providers can be setup to automatically renew and deliver an updated SSL certificate to our systems when their expiration time approaches.

    This idea is for Innovative to support software-only site with setting up an automatic SSL renewal process thereby keeping our systems safe from expiring certificates and making the process worry-free.

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

    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. It would be helpful for us to have access to the history of item and volume records, including details of their creation and any subsequent edits. This would improve our ability to track changes and ensure accountability if any issues come up.

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

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

    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. Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.

    We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.

    Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.

    This…

    19 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. We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.

    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)
  20. Sierra now supports SAML for authenticating staff, but still allows users to authenticate without MFA using the less secure Sierra legacy authentication method. Sierra should allow administrators to require SAML authentication instead of always allowing users to choose SAML or Legacy.

    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)
← Previous 1 3 4
  • Don't see your idea?