276 results found

1. Make printer option defaults available by workflow, and have "send to email address" send only to staff email addresses

   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 chance of staff accidentally sending private patron information to the wrong person for example. Reduced chance to typos causing the emailed information to go outside of our staff or the intended patron.

   It's not a super common issue, but we have had patron date dues sent to the wrong person because staff chose the Send to Email Address option and entered the wrong address.

   We want staff to have access to send to email address in order to notify coworkers of a problem, but want to limit the chance of private information being send to the wrong patron.

   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… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   The product team will review this idea for consideration for a future release.

2. Change order of information entered in new patron records to make Unique ID the first entry, thereby catching duplicates right away.
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.

3. Treat transferred holds in the same way as newly placed holds e.g. recall on loan copies when a hold is transferred to them
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.

4. Translate item status and OPAC message codes in Summary View

   Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration & APIs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Provide full Branches table and full Location code list via Sierra REST API

   Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

   Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the Branches table. Fiona (BiblioCommons) also confirmed the current Branches API is insufficient and has requested III improve it to return a full representation of the Branches table.

   Current behavior

   When calling:

   GET /v6/branches/?fields=%2C

   We receive only two branch entries and an API response showing:

   "total": 2 (implying only two branch records exist), even though our environment contains many more branch/location entries in the Branches table.

   The response includes a locations array, but only for locations linked to Branch Address table entries.

   Example (truncated):

   {
   "total": 2,
   "start": 0,
   "entries": [
   {
   "id": 1,
   "name": "Poudre River Public Library District",
   "locations": [
   { "code": "adult", "name": "Adult" },
   { "code": "afic", "name": "Adult - Fiction" },
   ...
   ]
   },
   {
   "id": 2,
   "name": "Interlibrary Loan"
   }
   ]
   }

   Desired behavior

   Provide a REST API mechanism to retrieve a complete, authoritative list of:

   All Branches table entries (not only Branch Address table entries that have names populated), and/or

   All location codes as defined in the Branches table, including their display names/labels and other relevant metadata used by integrations.

   Why this matters (impact and use cases)

   This enhancement would significantly improve Sierra interoperability with third-party vendor products and local applications by enabling real-time retrieval of location configuration data.

   Primary use case: Discovery layers

   BiblioCore, Aspen Discovery, and Vega Discover (and similar products) need accurate location codes and labels to support:

   facets and scoping

   branch/location-based availability display

   collection/location grouping rules

   pickup location logic

   suppression or “hidden” locations behavior where applicable

   Right now, when a library:

   adds a new location code,

   renames a location display label,

   retires/deprecates a location,

   …they typically must manually communicate those changes to the discovery vendor (often via spreadsheets/emails/tickets). That adds delay, introduces errors, and makes “near real-time” configuration synchronization impossible.

   Secondary use cases (beyond discovery)

   internal analytics/reporting tools that want to label circulation/hold data by location

   AMH/bin mapping, routing, or sorting optimization tooling

   self-check, RFID, or third-party circulation peripheral integrations

   custom staff apps and dashboards that need the live location dictionary for validation and display

   Proposed solution options

   Any one of these would solve the problem. More than one would be even better.

   Option A: Enhance /v6/branches to represent the full Branches table

   Return all branch/location records stored in the Branches table, not just those tied to Branch Address entries with names.

   Add a way to request “Branch Address fields” separately (since Branch Address and Branches table are distinct concepts in practice).

   Option B: Add a dedicated endpoint for locations

   For example:

   GET /v6/locations

   GET /v6/branches/locations

   Option C: Provide an “includeAll” style flag
   If III wants to preserve current default behavior, add something like:

   GET /v6/branches?includeAll=true

   GET /v6/branches?source=branchesTable vs source=branchAddressTable

   Improving access to the Branches table / locations dictionary via REST API would be a major interoperability win for Sierra. The main theme is discovery layer integration (BiblioCore, Aspen Discovery, Vega Discover), but the same capability would benefit many other integrations and local applications that need accurate, real-time location metadata.

   Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

   Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Auto- Update library card expiration dates

   When a new library card is created in a month, Sierra auto-populates the expiration date for the card as next month +3 years, but this has to be manually adjusted every month by the Circ supervisor. It would be nice if Sierra could automatically set the expiration date for library cards created every month.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Circulation, Access Services & Fulfillment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Restart a Range of Sessions/Processes in Admin App

   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 box next to listed sessions to restart several at once, but it's much easier to say, "Restart everything from line 30-142."

   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… more

   •  

   •  

   •  

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Introduce padding to item record numbers

   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. This method is time-consuming and error-prone, requiring careful validation to ensure accuracy.

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

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Acquisitions, Serials & Inventory Management  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Sierra API : add /users/groups/ endpoint to "GET number of users by group"

   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 SSH session with a script, but this is complicated. Right now, I have to manually login to Admin Corner and enter an obscure sequence of keystrokes to get this information and even then the data is only aggregated once per hour. Only staff with Admin Corner access are able to perform this monitoring, which takes time away from other duties.

   Enhancing the /users API to add a new endpoint (e.g., GET /users/groups/{group}) which returns the number of users by group would make monitoring user groups much easier. Indeed, it could make user groups more useful broadly speaking.

   In our case, polling such an API periodically would empower us to act when there are too few (or too many!) self-checkout users logged in. The same concept would apply to other user groups that merit monitoring for operational reasons.

   Alternatively, a built-in Sierra feature that sends a notification when the number of logged-in users per group is greater or less than arbitrarily defined values would be helpful for my specific use case.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Limit the number of holds to the total count of copies in that Bib

    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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Login indicator

    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 Sierra Helmet Firstname Lastname) but staff says it's not distinctive enough. Maybe the color of the text or the color of the upper bar could change when the personal login is added/removed.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add "last status update" to low & high circulation weeding report results

    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 rotation workflows do not have a checkin or checkout date to help staff weed or request items from other branches.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Reporting & Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.

13. New function to scan items into Sierra to change an Item status to "in transit"

    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 have ergonomic desks and scanners that are best suited to scanning large numbers of items.

    • If the functionality was distinct from check-in we could manage who gets access to this functionality via permissions and workflows.

    • We do not wish to implement an API web-based solution that is not integrated with Sierra. With over 300 staff, an API work-around would not suit us.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.

14. Delete and modify identity providers during SAML configuration

    It is better to provide the option to delete the identity providers and modify the name of the identity provider by the administrator during SAML configuration.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.

15. Customise Encore 'Did you mean' offerings to prevent offensive suggestions

    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 suppress any suggestions which are deemed inappropriate for our clientele.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.

16. homebound rating

    Part of the homebound module is to add ratings to checked in items for the patron.
    The rating data for the Homebound module is not kept in the Sierra SQL database, but rather in a separate log which is used to create the Homebound Patron Report so it cannot be accessed through Sierra Direct SQL Access. It would be nice if the ratings were more accessible in the SQL tables. Thanks.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Customer Relationship & Account Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating