64 results found

1. Move the Leap quotes out of WebAdmin and into SA

   The author quotes in Polaris Leap suddenly became a hot topic because of a Neil Gaiman quote within the list. While making some adjustments, it occurred to me that there are more possibilities for those Leap quotes and that they could be used to convey real information to the staff about things like upcoming Polaris upgrades, library events, and so on. At the very least, changing the quotes in WebAdmin is a bit of a pain because you have to change a quote and an author separately.

   My idea is that the quotes should be added to SA, where they're handled in a table like many other facets of Polaris. Additionally, it'd be nice to be able to have more than six of them and to provide the ability to enable/disable quotes. That way, if a library needed all of the staff to see an announcement in Leap, they could enable that one announcement and disable all the other quotes.

   The author quotes in Polaris Leap suddenly became a hot topic because of a Neil Gaiman quote within the list. While making some adjustments, it occurred to me that there are more possibilities for those Leap quotes and that they could be used to convey real information to the staff about things like upcoming Polaris upgrades, library events, and so on. At the very least, changing the quotes in WebAdmin is a bit of a pain because you have to change a quote and an author separately.

   My idea is that the quotes should be added to SA, where they're… more

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

2. Printing and Exporting Reading History in the Polaris

   We have had several library members ask why there are not capable of printing their reading history from their account in Polaris. It would be great if there was a print button at the top of their reading history. Can this be be added?

   Idea Value
   Very helpful for the elderly. They prefer a hard copy and/or have to wait for a family member to visit to show them their reading history.

   •  

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

3. Change Login Branch in Leap (without signing-out)

   Currently if we need to change the branch we're logged into in Leap we need to sign-out and log back in. This can be disruptive if we have records opening we're working with that would then need to be re-opened. It would be handy if there was a way to do this without signing-out and back in, in a way that would allow records to remain open.

   Admittedly I don't think this would be helpful for the majority of staff, likely more administrative roles that need to perform activity across a range of branches. But it would be a nice option.

   Currently if we need to change the branch we're logged into in Leap we need to sign-out and log back in. This can be disruptive if we have records opening we're working with that would then need to be re-opened. It would be handy if there was a way to do this without signing-out and back in, in a way that would allow records to remain open.

   Admittedly I don't think this would be helpful for the majority of staff, likely more administrative roles that need to perform activity across a range of branches. But it would be a nice… more

   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  ·  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. Comprehensive Audit Trail for System Administration Changes

   Implement a detailed and accessible audit log for all configuration changes made within the Polaris ILS System Administration (SA) and "adjacent" modules.

   Description of the Problem

   The Polaris ILS lacks a granular, searchable audit trail for System Administration changes. This makes it difficult to determine who made a specific change, when it occurred, and what the previous setting was. This ambiguity hinders troubleshooting when a configuration error occurs, complicates training, and reduces accountability.

   Proposed Solution

   A comprehensive, transaction-based audit log that automatically records the following data for every saved change in the SA module:

   Timestamp: The precise date and time of the change.
   User Account: The Polaris username of the staff member who made the change.
   Workstation: The name of the workstation from which the change was initiated.
   Configuration Area: The specific parameter modified (e.g., "Receipts - Fines," "Patron Services - Loan Period").
   Previous Value: A record of the setting's value before the change.
   New Value: The setting's value after the change.

   This log should be presented in a searchable interface, allowing administrators to filter events by date, user, and configuration area.

   Initial Focus for Implementation

   For an initial release, prioritize the audit of settings that can be modified by general staff, not just system administrators. A key area is workstation-specific settings, such as receipt configurations. Because System Administration access is typically restricted to a few users, changes made in more broadly accessible areas are often more frequent and difficult to trace. Focusing development on these staff-level settings first would offer the most immediate value in improving accountability and simplifying troubleshooting.

   Justification

   While the storage and processing constraints of 1997 may have made detailed logging impractical at Polaris's inception, modern server infrastructure can easily handle this function. Implementing this feature would align Polaris with current enterprise software standards where robust auditing is critical for system integrity and security.

   Benefits:

   Rapid Troubleshooting: Quickly identify the source of problems caused by configuration errors.

   Clear Accountability: Create a definitive record of all administrative actions.

   Simplified Reversal: Know the exact previous value to accurately restore a setting.

   Enhanced Security: Provide a crucial tool for security audits and investigations.

   Use Case Example

   If a library's hold pickup notices suddenly aren’t printing for one workstation, an administrator could use the audit tool to filter for recent changes to "Receipts." The log would immediately show which user modified the settings and when, displaying both the old and new settings. The administrator could then use the "Previous Value" information to instantly revert the setting.

   Implement a detailed and accessible audit log for all configuration changes made within the Polaris ILS System Administration (SA) and "adjacent" modules.

   Description of the Problem

   The Polaris ILS lacks a granular, searchable audit trail for System Administration changes. This makes it difficult to determine who made a specific change, when it occurred, and what the previous setting was. This ambiguity hinders troubleshooting when a configuration error occurs, complicates training, and reduces accountability.

   Proposed Solution

   A comprehensive, transaction-based audit log that automatically records the following data for every saved change in the SA module:

   Timestamp: The precise date and time… more

   •  

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

5. Add visual customizations to Leap

   The Polaris Leap login screen consists of two text fields, a button, and a low resolution PNG floating upon an ocean of #CCCCCC. It is, in a word, boring. There are no easy customization options offered that allow a library to give it the look and feel that they want, save for one option that will change the colour of the menu bar. Now, granted, if you have a staff member with some web coding knowledge, they can modify the Leap CSS and replace some images to give things a spruce up. Five lines of code and a fresh image makes the Leap experience much more attractive and distinct for the library. (See attached screenshots.)

   But those are manual, unsupported customizations that will almost certainly need replacement after an upgrade and are likely inaccessible to hosted libraries.

   Please add functionality that, at the very least, allows a library to:

   • Easily add a full screen cover image to the Leap login screen, ideally at the branch level so each branch can have their own look

   • Easily add the library's logo to the Leap login screen

   • Easily add the library's logo to the Leap main screen

   • Change the quotations on the Leap main screen without going through WebAdmin

   Other suggestions are welcome - please comment below! 😃

   The Polaris Leap login screen consists of two text fields, a button, and a low resolution PNG floating upon an ocean of #CCCCCC. It is, in a word, boring. There are no easy customization options offered that allow a library to give it the look and feel that they want, save for one option that will change the colour of the menu bar. Now, granted, if you have a staff member with some web coding knowledge, they can modify the Leap CSS and replace some images to give things a spruce up. Five lines of code and a fresh image… 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

   UNDER REVIEW  ·  2 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. Add the ability to clone an existing branch when creating a new branch

   We would like to be able to copy an existing branch when creating a new branch, since often our additions are branch locations of an existing library that will have almost the same exact settings.

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

7. Hide libraries and branches in Polaris System Administration

   Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.

   Just sitting there and doing nothing.

   I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.

   So add the ability to hide them instead.

   That way, when a library leaves the system, you're not wading through the settings and parameters and profiles and tables of a library that's not there anymore, along with all of the branches that library encompassed. Yes, all the lower level data and information is still in the system, but they're not something the ILS Admin needs to deal with unless they actually need to deal with it.

   Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.

   Just sitting there and doing nothing.

   I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.

   So add the ability to hide them instead.

   That way, when a library leaves the system, you're not wading through the settings and… 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  ·  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. Card renewal to update Last Activity Date

   Currently, staff modifications to patron registration including card renewal do not update the Patron Last Activity Date (LAD). As more libraries move towards long or no expiration periods, LAD becomes even more important for patron database maintenance. We have seen cases in which patrons renew their card without any additional activity resulting in their record being purged during cleanup. Including renewal and/or extending the card expiration period in LAD will better allow libraries to track patron engagement.

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

9. Include an "X"/close button on workform tracker records

   Sometimes I have a lot of records open in the workform tracker, and it's a pain to have to go into each to close it. It would be useful to have a button I could quickly click to close them instead.

   In cases where a record has been modified it should generate a prompt about saving changes, and show you the record again in this case so it's clear what's being saved.

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

10. Service Name Logging in PatronValidate API

    This proposal outlines an extension to the Patron Validation API to include an optional serviceName parameter. When provided, this value will be recorded in the Integrated Library System (ILS) transaction log, allowing us to track which service initiates each patron validation request.

    Currently, the ILS transaction log records patron validations without capturing which service initiated the request. This lack of context makes it difficult to analyze traffic from third-party services (e.g., OverDrive, Hoopla) or internal applications, troubleshoot validation spikes, and make informed decisions about service contracts and resource allocation.

    The proposed solution is to modify the Patron Validation API to accept an optional serviceName parameter. If the serviceName is included, the API will pass it to the ILS for logging. If omitted, the validation will proceed as normal to ensure full backward compatibility with existing integrations.

    Benefits
    Enhanced Analytics: Generate reports on service usage to inform vendor negotiations and collection development.
    Improved Troubleshooting: Quickly identify the source of performance issues or high traffic to reduce resolution time.

    Data-Driven Decisions: Use service usage patterns to guide technology investments and integrations.

    Backward Compatibility: The optional parameter ensures existing applications continue to function without modification.

    This proposal outlines an extension to the Patron Validation API to include an optional serviceName parameter. When provided, this value will be recorded in the Integrated Library System (ILS) transaction log, allowing us to track which service initiates each patron validation request.

    Currently, the ILS transaction log records patron validations without capturing which service initiated the request. This lack of context makes it difficult to analyze traffic from third-party services (e.g., OverDrive, Hoopla) or internal applications, troubleshoot validation spikes, and make informed decisions about service contracts and resource allocation.

    The proposed solution is to modify the Patron Validation API to… more

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

11. A way to customize pop up notices

    Various popups appear in Polaris via the client or Leap. Some are pretty clear in what the reminder or error message is about and some popups are not.

    I am requesting a way to customize the text and title (Leap only has this visible) to make it more clear for our staff to understand either the popup reminder or the popup error with a little more explanation.

    Example for Popup Reminder: Via the client we have a popup reminder about "reminder notices option is email. Do you want to continue?". This occurs when we leave the email field blank per patron request. This has become second nature for our staff to always say yes to bypass this field. Along with this, the client also has a yellow warning symbol. In Leap, the popup reminder appears with the same text as the client but with a title now as well, "Valid email address not found". Leap does not have any symbols to make it clear if the popup is a reminder or an error.

    Note: We did find out a workaround which was to check the "exclude from notices and reminders almost overdues/auto-renew" to bypass the popup reminder. This just isn't the most ideal.

    Example for Popup Error: Via the client, if the notification option of email address is selected for example but then staff accidentally leaves the email address field blank, the popup error message appears as "Notification option is email. Please enter an email address." The client has a red circle with an x symbol within it to indicate the error. In Leap, the popup error appears with the same text as the client but now has a title "Missing Contact Information". Leap does not have any symbols to make it clear if it is a popup reminder or popup error.

    Various popups appear in Polaris via the client or Leap. Some are pretty clear in what the reminder or error message is about and some popups are not.

    I am requesting a way to customize the text and title (Leap only has this visible) to make it more clear for our staff to understand either the popup reminder or the popup error with a little more explanation.

    Example for Popup Reminder: Via the client we have a popup reminder about "reminder notices option is email. Do you want to continue?". This occurs when we leave the email field blank per… more

    •  

    •  

    •  

    •  

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

12. Hoopla integration with Polaris

    The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.

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

13. Create a Back End Updating Feature

    A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.

    So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the patch installed, and I said yes, please do that.

    But step back and you see the problem. This was a known issue. And there was a patch. So... why not just patch the system? I think there needs to be some kind of updating feature for ILS admins where we can see a list of available patches for known issues with our build of Polaris. And then, if we're seeing those issues, or we can recreate them, we should be able to install the patch from that updating system. This would be something like Windows Update or Discover in KDE. Applications of patches should be left to the discretion of the local ILS admin team, but at least they'd know there were issues and solutions are available for them.

    A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.

    So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the… more

    17 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

14. Move Leap timeout setting to SA

    We would like to be able to adjust the timeout in Leap after inactivity ourselves. Currently, we have to contact support to do this after each upgrade, since it resets itself. If the setting was in SA, we could reset it ourselves after each upgrade.

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

15. Leap Login Setting: Set Default Branch to Workstation's Assigned Branch

    Requested Change:
    We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection. We would like it to default to the workstation's branch.

    Desktop Client:
    When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.

    Leap:
    When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.

    Why:
    At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location. Nearly 100% of the time, these computers will be signing into Leap using the branch where the computer is installed, independent of the staff user's default assigned branch.

    We have staff who work at multiple branches and have noticed they accidentally sign into their staff user's default branch, even when they are working at a different location.

    Solution idea:
    Add a LEAP setting that will allow organizations to select which default branch is presented at login (workstation vs. user). In our case, we would want a global setting for LEAP workstations that always defaults to the workstation's branch. But some organizations might want a user-specific or workstation-specific setting that would override the global setting. There could be unique use cases where a user travels with a laptop and you might want to force a manual selection each time for that particular user or workstation (no default).

    Requested Change:
    We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection. We would like it to default to the workstation's branch.

    Desktop Client:
    When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.

    Leap:
    When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.

    Why:
    At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location.… more

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

16. PII Management Options

    Although there are current options for purging patron IDs from circ transactions, and deleting account transactions, there are some gaps with removing PII (personally identifiable information) we'd like to see addressed.

    We'd like the option to purge patron IDs from non-circ transactions (incl. patron account history and record history). We'd also like the option to manage patron details on any other tables where history may be maintained after a patron record is deleted (e.g. Notification History, DeletedPatrons, DeletedPatronAccounts, kwmssg, and offline and InnReach process tables). It would also be ideal to have a plan for removing any CNV tables (from migrating to Polaris, or additional work by Clarivate staff) after a set period of time, as these may linger with patron data, and without oversight.

    We'd like patron data limited in log files where it is included (e.g. SIP, PAPI, IIS). Lastly, as there can be considerable patron data in SimplyReports exports, we'd like to see options to purge reports files after a certain period of time (the settings exist on the Application Defaults page, but don't work).

    Although there are current options for purging patron IDs from circ transactions, and deleting account transactions, there are some gaps with removing PII (personally identifiable information) we'd like to see addressed.

    We'd like the option to purge patron IDs from non-circ transactions (incl. patron account history and record history). We'd also like the option to manage patron details on any other tables where history may be maintained after a patron record is deleted (e.g. Notification History, DeletedPatrons, DeletedPatronAccounts, kwmssg, and offline and InnReach process tables). It would also be ideal to have a plan for removing any CNV tables (from… more

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

17. Add "You Saved" Text to PAPI Checkout

    When items are checked out through SIP2, Polaris includes the "You just saved __ by using the library" text in the response. However, this information is not available when using the ItemCheckout method through PAPI.

    As we start moving vendors away from SIP2 and towards PAPI, we'd like to replicate the functionality of SIP2.

    Thanks

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

18. Polaris transactions will "run out" of space due to being an "int" data type

    The Polaris Transactions database TransactionID is an int data type. This 2,147,483,647 means the biggest number supported by the database. In our busy system, we're about halfway through the available TransactionIDs as we're about to reach 1 billion. This field should be moved up to a bigint data type. Otherwise inserting new data will fail.

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

19. Include Hold Bulk Change in Background Processing

    Polaris 8.1 introduced Bulk Changs within the Request Manager. However, when a bulk change is made, the only verification the user receives is a message that tells the user how many holds were changed. It would be beneficial (and would follow Polaris' bulk change practices) to include the results in the Background Processing function.

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

20. Create custom circulation statuses

    To be able to create customized circulation statuses that work for our system versus using the only given statuses. For example, the ability to create various Withdrawn - Leased, Condition, Relevancy. This would then offer additional feedback for staff when stats are ran to determine why materials were withdrawn versus they were.

    13 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

    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  ·  AdminSamantha Quell (Admin, Innovative) responded

    For the withdrawn example, does this really require custom circulation statuses? Or just a way to indicate/query the reason an item was withdrawn?

    
    

    The reason Polaris has traditional restricted circulation statuses is because of our automated processes around certain statuses. Using the withdrawn example, our automatic Lost/Missing to Withdrawn processing would not know about custom statuses or which one to use.

    
    

    If we reworked this enhancement as needing to be able to track/report on withdrawn reasons, we could plan for that within the automated processes.