187 results found

1. Create Lists - Saved Searches - Ability to Rename, Show Creator, Last Used

   We repeatedly run up against our limit of saved searches in Create Lists. There are probably saved queries created long ago that no one is using/needs. I was hoping to assign staff to review the queries and put their initials in the saved search name, but when you go to Edit, you can only edit the query, not the query name (like you can a review file). Ideally it would work like the review files themselves, when you can see who last ran the list (initials, date and time). And perhaps apply the "Own" option. This would really help to keep these saved searches under control.

   We repeatedly run up against our limit of saved searches in Create Lists. There are probably saved queries created long ago that no one is using/needs. I was hoping to assign staff to review the queries and put their initials in the saved search name, but when you go to Edit, you can only edit the query, not the query name (like you can a review file). Ideally it would work like the review files themselves, when you can see who last ran the list (initials, date and time). And perhaps apply the "Own" option. This would really help to… more

   49 votes

   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

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

2. Clarify Fines Payment Lock Messaging

   The current wording of the fines payment lock messaging implies the presence of fines, which is not always the case and is misleading. To reduce confusion for staff, please change the message wording to indicate that another station has the record open, therefore the fines function in the patron record is locked. This will indicate to staff the reason why it's locked (another station has it open) and what they can't do while it's locked (access the fines function in the patron record).

   46 votes

   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  ·  9 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

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

   44 votes

   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  ·  4 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

4. Offer the ability to retain a patron's receipt preference at checkout

   At checkout, Circulation Staff must ask patrons at the end of each checkout if they want a printed receipt, email receipt, both, or none, or place a pop-up message on their account. It would be great if there were a way to retain each patron's receipt preference so that upon closing out the patron's record, the preferred receipt would be sent, print, both, or no receipt would be given.

   42 votes

   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

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

5. Recycling Bin Feature for Clear Expired Holds & Holdshelf & Notices

   We will periodically have situations, as we did this morning, where staff move to print their holdshelf report & for one reason or another (today's was some manner of technical issues with their printer), the content of the report is lost.

   We can sometimes salvage this data from the back end by looking for holds cleared on the day by the login responsible, but it would be much easier if there were some sort of Recycling Bin style feature, where "cleared" files like the holdshelf report or paging lists were stored until the user logs out, giving them another chance to print them without the need to reach out to central support.

   We will periodically have situations, as we did this morning, where staff move to print their holdshelf report & for one reason or another (today's was some manner of technical issues with their printer), the content of the report is lost.

   We can sometimes salvage this data from the back end by looking for holds cleared on the day by the login responsible, but it would be much easier if there were some sort of Recycling Bin style feature, where "cleared" files like the holdshelf report or paging lists were stored until the user logs out, giving them another chance… more

   •  

   40 votes

   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  ·  4 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

6. Hold Pickup Reminder/Courtesy Notice

   Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.

   Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want the item or aren't able to pick it up in time, they can inform the library. Then the item can move on its way and space can be created for other holds without the item lingering until the pickup by date. It also enhances the patron's experience because it prompts patrons again about their holds, which they may have forgotten about since receiving the first notice.

   Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.

   Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want… more

   40 votes

   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

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

7. Allow holds on bibs when holdable items are on order

   We have a non-holdable lucky day collection whose items are on the same bib as our regular, holdable copies of those titles. Sierra allows patrons to place holds on titles that are on order, but sometimes the non-holdable copies are the first to arrive -- at which point, Sierra sees that all items on the record are non-holdable, and stops allowing holds until the first holdable copies come in.

   Innovative recommended splitting nonholdable items onto a separate bib record, which seems liable to clutter up the catalog; moreover, some of these items are likely to be moved into our regular holdable collection when the initial demand dies down.

   We'd like there to be a way for Sierra to allow holds when there are outstanding orders attached to a bib record, especially when those orders are for holdable copies. Ideally, it would be great if the system could identify whether on-order items were holdable or not. Barring that, perhaps there could be a system option for libraries to choose whether to allow holds if open orders exist, even if all items are currently nonholdable.

   We have a non-holdable lucky day collection whose items are on the same bib as our regular, holdable copies of those titles. Sierra allows patrons to place holds on titles that are on order, but sometimes the non-holdable copies are the first to arrive -- at which point, Sierra sees that all items on the record are non-holdable, and stops allowing holds until the first holdable copies come in.

   Innovative recommended splitting nonholdable items onto a separate bib record, which seems liable to clutter up the catalog; moreover, some of these items are likely to be moved into our regular… more

   39 votes

   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

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

8. Allow Pickup Location Changes After Hold Is Activated (with Optional Patron Notification)

   In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.

   We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.

   -Why This Is Needed:

   • Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is no way to reroute the hold without canceling and re-placing it.

   • MeL/INN-Reach and delivery systems: Multi-library consortia and shared systems occasionally fulfill to the wrong location. Currently, Sierra does not allow staff to correct this once the hold is trapped.

   • Staff training errors: If the wrong login or fulfillment location is used during check-in, the item is committed to the incorrect pickup point. While enabling "Priority Paging: Refuse Item Hold" can prevent premature activation, this feature introduces the risk of accidentally canceling INN-Reach holds, which can disrupt patron access and increase staff workload.

   • Patron requests: Patrons sometimes ask to change their pickup location after the hold is already activated. Staff have no way to update the system to reflect this without canceling and re-initiating the hold manually.

   -Proposed Enhancement:

   • Allow staff with appropriate permissions to change the pickup location of a trapped hold, up until the item is either checked out or expired.

   • Log the change in the item or hold history to provide a record for auditing and accountability.

   -Optional but Strongly Recommended:

   • Add an optional "Pickup Location Changed" notice that can be sent to patrons automatically when a change is made. This would help notify them that their item is ready at a different location.

   -Benefits:

   • Reduces the need for manual workarounds and improves the patron experience

   • Provides flexibility in time-sensitive workflows

   • Supports accurate hold management in cases of staff error or patron changes

   • Saves staff time by eliminating the need to cancel and recreate holds or contact individual patrons.

   In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.

   We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.

   -Why This Is Needed:

   • Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is… more

   38 votes

   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

   4 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

9. Add ability to group itypes into categories in the new patron checkout limit table

   With the new patron checkout limit table, we lost the ability to group itypes into a category if we want to use the other limits like library location. We need to be able to either group itypes in the new patron checkout limit table, or use a combination of the old table and the new. We really need the new library location limiter in the new table so that our ptype 30 can only checkout items at our offsite kiosk and no other library, but we now lose the ability to still group our itypes into categories. Our itypes are very granular, so we rely on the categories to reduce the allowed checkout for say "Movies". "Movies" consists of the itypes for adult fiction dvd, adult non-fiction dvd, adult fiction bluray, adult non-fiction bluray, and so forth with other audience levels for about 7 itypes in that category. Now, each itype has a total, which goes way over the currently allowed 20 per customer. Each itype would need to allow 20 checkouts in the new table, which vastly expands the amount allowed per customer.

   With the new patron checkout limit table, we lost the ability to group itypes into a category if we want to use the other limits like library location. We need to be able to either group itypes in the new patron checkout limit table, or use a combination of the old table and the new. We really need the new library location limiter in the new table so that our ptype 30 can only checkout items at our offsite kiosk and no other library, but we now lose the ability to still group our itypes into categories. Our itypes are… more

   31 votes

   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  ·  7 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

10. Multiple Notice Preferences

    Allow patrons to choose one or more notice preferences. A patron would receive the same notice through any and all channels they want, allowing the library to better serve a variety of needs and lifestyles.

    30 votes

    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  ·  3 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. Add "permanent location" field in item record and function to change to it

    We have shelves for new materials, and item location codes for these ("new mysteries," "new fiction," "new DVDs," and lots more). Moving items from the new shelves to the regular shelves is a chore, both in handling materials and in knowing (and selecting) what location to change them to. It would be great if you could just get into a function in Sierra that would change the current item location (the "new" one in my example) to the permanent item location (a new field that would be added with this idea, which would catalogers would populate when the item was cataloged). Then, in this function, anyone could just scan a stack of items, one after the other, without having to look up what the "not-new" location was or choose it or anything. A "permanent location" field could be used in other ways, maybe for displays.

    We have shelves for new materials, and item location codes for these ("new mysteries," "new fiction," "new DVDs," and lots more). Moving items from the new shelves to the regular shelves is a chore, both in handling materials and in knowing (and selecting) what location to change them to. It would be great if you could just get into a function in Sierra that would change the current item location (the "new" one in my example) to the permanent item location (a new field that would be added with this idea, which would catalogers would populate when the item was… more

    30 votes

    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  ·  4 comments  ·  Cataloging & Metadata 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

12. Improve patron address parser to better map data to the patron_record_address table

    Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.

    For one common example in our system if an extended zip code is entered in any format other than #####-#### (say using a space instead of the hyphen, or just including a space before or after the hyphen for that matter) then the city/region/postal_code fields will all be lumped together in the city field, leaving the region and postal_code as NULL. Similar issues can occur if extra lines are used to separate out these elements in the client.

    This leads to issues with searching patron records in create lists, and can lead to quite difficult query needs in SQL (not to mention an enormous amount of confusion for any third party vendors that are expected to work with query results).

    The parser should be improved to at least account for some of these more common data entry scenarios.

    Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.

    For one common example in our system… more

    29 votes

    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  ·  5 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

13. Add "max number of overdue items" column to patron block table

    Many libraries have eliminated fines and they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based on a Library determined number of overdue items. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.

    Idea Value: This new setting would provide an incentive for Customers to return their items.

    Idea Value: We don't want to restrict the number of items a Customer can sign out, but want to restrict borrowing after a specific number of overdues.

    Idea Value: Some libraries do not charge overdues but do charge a billing fee. Blocking the number of overdues a patron may have can prevent large, unexpected billing fees for those that have signed out more titles than they have kept track of.

    Idea Value: We don't want to manage this manually. We shouldn't put staff in the position of evaluating whether a patron should be blocked.

    Idea Value: Self checks would also automatically block patrons from checkout (and Customers could be redirected to Staff for more information).

    Some Libraries do not want to set up "overdue penalty points".

    Many libraries have eliminated fines and they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based on a Library determined number of overdue items. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.

    Idea Value: This new setting would provide an incentive for Customers to return their items.

    Idea Value: We don't want to restrict the number of items a Customer can sign out, but want to restrict borrowing after a specific number of overdues.

    Idea Value:… more

    29 votes

    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

    5 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. Show item status at check-in

    When checking in an item over Sierra, it would be helpful to have an extra column added for item status. e.g. Available, In Transit or On Holdshelf. This would add more transparency when processing items (especially if we are interrupted mid-scan), allow for double checking items are placed in the right pile, and help with training new staff who may want to have more visibility around the different journeys an item can take once returned. Added bonus: If it can show the additional sorting groups available in IMMS, this will assist staff even more.

    28 votes

    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

15. Improve the labels for LDR, 006, 007 and 008 in Create Lists

    Currently in Create Lists it is very difficult to specify criteria for special fields like the leader, 006, 007 and 008. Many of these have the exact same label, like Audience, which appears four different times. Each of them is for audience as it appears in different versions of the 008 for different record types. Then it appears four more times in the 006.

    It would be helpful if each of these different audience codes were labeled in Create Lists, such as "Audience for Books," and "Audience for Music," etc. This would make it much easier to use this function. As it is you have to search in the manual to figure out which one is which.

    I would like to see these extra labels on all the repeated code names like FormItem and Index.

    Currently in Create Lists it is very difficult to specify criteria for special fields like the leader, 006, 007 and 008. Many of these have the exact same label, like Audience, which appears four different times. Each of them is for audience as it appears in different versions of the 008 for different record types. Then it appears four more times in the 006.

    It would be helpful if each of these different audience codes were labeled in Create Lists, such as "Audience for Books," and "Audience for Music," etc. This would make it much easier to use this function.… more

    27 votes

    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  ·  Cataloging & Metadata 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

16. Restart a Range of Terminals

    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

    •  

    •  

    •  

    •  

    •  

    •  

    27 votes

    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  ·  3 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

17. Add the ability to create a review file from items in Global Update.

    Sometimes I'm working in Global Update and am using the toggle feature or the limit tool. I then want to work with just those records. I don't want to remove the others from the review file, but rather copy the records I want to look at into a new review file so that I can work with them there.

    27 votes

    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

    3 comments  ·  Cataloging & Metadata 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
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

18. Add a Stat Group When Creating a Patron API Key for Vendors

    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 inflated statistics, which is particularly problematic when the library intends to track circulation usage via the API but cannot do so effectively.

    To expand tracking capabilities, it would also be beneficial to explore the feasibility of retroactively assigning a Stat Group to existing API keys. The implementation of this feature could leverage the workflow used for SIP2 license logins as a model for designing the Stat Group selection process when creating new API keys. Additionally, hold requests currently store the stat group within the body of the request rather than in the URL. Understanding this distinction may help in designing the stat group functionality for API keys in a way that aligns with existing data structures and workflows.

    The implementation of this proposal would provide several benefits. It would enable staff to categorize API keys by vendor, allowing more precise tracking and facilitating data collection and reporting using existing tools such as Web Management Reports and Decision Center. It would also improve visibility into vendor-specific API key usage, supporting data-driven decision-making and reducing reliance on stat group 0 as a catch-all category, ultimately leading to more accurate circulation statistics.

    This enhancement would streamline reporting efforts and provide better insights into vendor-specific API key usage, ultimately improving resource management and decision-making processes.

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

    27 votes

    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

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

19. Create Lists: Prevent the hopping or jumping of lists after a sort is applied

    Currently, when a staffer goes into Create Lists and sorts the lists using one of the column headers, while scrolling down to locate the appropriate list, Sierra jumps or hops upward thereby losing the staffers place in Create Lists. This idea is to prevent that from happening and to make the default or custom sort in Create Lists stick. This would save staff time and reduce errors as well.

    26 votes

    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  ·  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

20. Update Print Template Assignment Methodology

    After spending over an hour adding new print templates to every login for a new library, I am once again reminded of the inefficiency of the current methodology for assigning print templates to logins.

    Idea: Print Templates can be assigned like Permissions for Sierra. They would have their own sidebar, and logins could be added to each print template. That way, it only takes a couple of clicks to add print templates in mass to several logins, rather than clicking into the login, then settings, then print templates, then scrolling to find each print template and set the prompt. This is especially tedious in a consortium, where there are tens of print templates per category.

    Value: make administration of print templates easier and quicker for system administrators.

    After spending over an hour adding new print templates to every login for a new library, I am once again reminded of the inefficiency of the current methodology for assigning print templates to logins.

    Idea: Print Templates can be assigned like Permissions for Sierra. They would have their own sidebar, and logins could be added to each print template. That way, it only takes a couple of clicks to add print templates in mass to several logins, rather than clicking into the login, then settings, then print templates, then scrolling to find each print template and set the prompt. This… more

    26 votes

    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  ·  4 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