254 results found

1. 2038 issue

   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.

   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

   6 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
   PLANNED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This will be implemented in Sierra in 2027.

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

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

   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

   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.

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

   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

   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

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

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

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

7. Introduce a 'Cancel' Button in the 'Item Already Paid for' Pop-Up Warning

   This is a resubmission of a recently expired idea from Nicole T.:

   In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding further, returning the user to the search results list. The "CANCEL" option prevents inadvertent payments on the wrong order records, reducing errors in fund allocation and duplicate payments. It improves the user experience for all staff members, especially those new to invoicing, by providing a clear option to cancel erroneous actions. Staff members could correct their mistakes immediately, reducing the likelihood of paying for items on the wrong record. It saves time and effort that would otherwise be spent rectifying mistakes, such as reversing payments. Enhances overall efficiency in invoicing, contributing to smoother operations in a multi-branch library environment with numerous fund codes and multiple copies of items.

   This is a resubmission of a recently expired idea from Nicole T.:

   In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding… 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

   9 comments  ·  Acquisitions, Serials & Inventory 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

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

   •  

   •  

   •  

   •  

   •  

   •  

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

9. Create RestAPI with a Patron Validate role that updates the “last circ activity date” in patron record 

   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 content.
   We want to give our eVendors as little read/write permissions as possible.

   Thank you.

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

   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
   PLANNED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   Selected for the Sierra 6.7 release by MEEP enhancement process

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

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

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

12. More universal accessibility features

    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 could personalize their accessibility settings through their individual initials, without affecting the default settings for all users using the same login.

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

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

14. Automatic SSL Certificate Renewal

    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.

    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

    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
    PLANNED  ·  AdminMike Dicus (Product Manager, Innovative) responded

    Selected for the Sierra 6.7 release by MEEP enhancement process

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

16. Create a GET API endpoint for circulation transactions

    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 have access to tables that should remain secured.

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

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

17. Generate Statement of Charges directly within patron record

    It would be very helpful to be able to print or email a Statement of Charges directly from a patron record (and have it formatted for 8-1/2 x 11 paper and mail-ready).

    Customers want a list of what they have out, and it looks very bad for the library to hand a customer a very, very long receipt when we are trying to save paper across the system.

    25 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

18. Add "mark damaged items" workflow to checkin

    Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.

    All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.

    Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like to see it (button beside the backdate option)

    Possible Mark Damaged Item behaviour within check-in function:
    1) Staff would select the "mark damaged items" button before they check-in the damaged item. It would not "stick" and apply to the next item.
    2) Item is checked in
    2) The "mark damaged items" pop-up would appear
    3) Staff would choose one of the following options: mark damaged, mark damaged and add charge, mark damaged and add bill, or cancel.
    4) A permission could be added to select this option at check-in so that it is optional for libraries.

    Thank you,
    Elizabeth

    Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.

    All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.

    Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like… more

    •  

    25 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

19. Batch Check-In Should Not Update Circactive Date

    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 may apply to other batch, administrative tasks that are completed by the library and not the actual patron.

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

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

20. Add Patron Type Category Grouping to the New Patron Checkout Limits Table

    With the new Patron Checkout Limits table, we have lost the ability to group patron types (ptypes) into a category when configuring checkout limits that also use criteria such as Library Location or Item Location.

    Currently, a separate row must be created for every individual ptype, which significantly increases setup and maintenance effort. In environments with many patron types that share the same checkout limits, this results in a large number of duplicate entries.

    We would like the ability to define and use Patron Type Categories/Groups within the new Patron Checkout Limits table, similar to the functionality available in previous configurations. This would allow a single checkout limit rule to apply to multiple patron types without requiring separate records for each one.

    Example:
    As shown in the attached screenshot, the same limit of 2 items must be entered repeatedly for multiple patron types (001, 002, 003, etc.) for Item Type 049. If these patron types could be grouped into a category, a single rule could be created and maintained instead of multiple identical entries.

    Benefits:

    • Reduces configuration complexity and data entry.
    • Simplifies ongoing maintenance.
    • Minimizes the risk of inconsistencies between patron types that should share the same limits.
    • Makes the new Patron Checkout Limits table more scalable for libraries with many patron types.

    This enhancement would restore flexibility that was available previously while improving usability of the new checkout limits configuration.

    With the new Patron Checkout Limits table, we have lost the ability to group patron types (ptypes) into a category when configuring checkout limits that also use criteria such as Library Location or Item Location.

    Currently, a separate row must be created for every individual ptype, which significantly increases setup and maintenance effort. In environments with many patron types that share the same checkout limits, this results in a large number of duplicate entries.

    We would like the ability to define and use Patron Type Categories/Groups within the new Patron Checkout Limits table, similar to the functionality available in previous… more

    •  

    24 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