Settings and activity
106 results found
-
17 votes
Wes Osborn
supported this idea
·
-
26 votesWes Osborn
shared this idea
·
-
25 votes
An error occurred while saving the comment -
10 votesWes Osborn
supported this idea
·
-
13 votes
An error occurred while saving the comment Wes Osborn
commented
Change /PolarisAdmin (Web Admin) so that leading and trailing spaces are automatically trimmed from the Username and External ID fields upon entry.
Problem Statement
Currently, if administrators accidentally enter a username or external ID with a leading or trailing space, it is saved as entered. This creates login and authentication issues for end users, since the system considers the space a part of the credential. This can be difficult to troubleshoot and frustrating for both administrators and end users.This is especially likely to happen when copying/pasting from certain user management platforms.
Proposed Enhancement
Automatically strip any leading or trailing whitespace from the Username and External ID fields when values are entered or saved. For example:
• [ ]johndoe → johndoe
• [ ]johndoe[ ] → johndoe
• johndoe[ ] → johndoeBenefits
• Prevents login issues caused by accidental extra spaces.
• Reduces support tickets and troubleshooting steps for staff.
• Ensures greater data consistency across accounts.Wes Osborn
shared this idea
·
An error occurred while saving the comment Wes Osborn
commented
We would like to enhance /PolarisAdmin (Web Admin) so that leading and trailing spaces are automatically trimmed from the Username and External ID fields upon entry.
Problem Statement
Currently, if administrators accidentally enter a username or external ID with a leading or trailing space, it is saved as entered. This creates login and authentication issues for end users, since the system considers the space a part of the credential. This can be difficult to troubleshoot and frustrating for both administrators and end users.This is especially likely to happen when copying/pasting from certain user management platforms.
Proposed Enhancement
Automatically strip any leading or trailing whitespace from the Username and External ID fields when values are entered or saved. For example:
• [ ]johndoe → johndoe
• [ ]johndoe[ ] → johndoe
• johndoe[ ] → johndoeBenefits
• Prevents login issues caused by accidental extra spaces.
• Reduces support tickets and troubleshooting steps for staff.
• Ensures greater data consistency across accounts. -
12 votes
An error occurred while saving the comment Wes Osborn
commented
I like this idea. I'm sure there is enough room to include the control numbers below the current icons.
Wes Osborn
supported this idea
·
-
79 votes
An error occurred while saving the comment Wes Osborn
commented
Given that we don't use pronouns on any notices, the upcoming Patron Alert feature might help for this: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/1056-patron-alert-note-
Though that field would not be patron updatable, which I would assume would be the preference for most people.
-
18 votes
An error occurred while saving the comment Wes Osborn
commented
Specifically the issue here in leap seems to be looking for SOME sort of delimiter. So, 614.837.8533 will match 614-837-8533 but 6148378533 will NOT match either of those.
Wes Osborn
shared this idea
·
-
6 votesWes Osborn
shared this idea
·
-
46 votes
An error occurred while saving the comment Wes Osborn
commented
This is a critical blocker. If it is not possible to use the Polaris patron id, then as a workaround, there should at least be some sort of transfer or migration service that could be run at least on an account by account basis to merge the old lists into the new account.
Wes Osborn
supported this idea
·
-
42 votes
An error occurred while saving the comment Wes Osborn
commented
This would be super helpful. I'm also adding in the keyword "audit" to make this easier for myself to find in the future :)
Wes Osborn
supported this idea
·
-
25 votesWes Osborn
shared this idea
·
-
17 votes
An error occurred while saving the comment Wes Osborn
commented
Although I know this would be more steps than happen today, I think that it is not an unusual flow for most accounts that people establish these days and would ultimately benefit both the patron with being assured they can get their notices and the library for having a better reputation for sending notices and lower costs (SMS/texts) for making sure those notices get through.
Wes Osborn
shared this idea
·
-
12 votesWes Osborn
supported this idea
·
An error occurred while saving the comment Wes Osborn
commented
This seems to be a common issue across various parts of the Leap framework that could lead to data loss (see: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/49250999-leap-doesn-t-save-or-prompt-to-save-notes-when-you ). Leap should be looking for these types of instances, this is common browser behavior: https://stackoverflow.com/a/7317311
-
14 votes
An error occurred while saving the comment Wes Osborn
commented
It would be SUPER to be able to get a better handle on who is authenticating.
Or, we'd also be fine with recording the API key used in the transaction database when a patron validates. Since those would be required, we'd always have access to the information.
Wes Osborn
shared this idea
·
-
5 votes
An error occurred while saving the comment Wes Osborn
commented
In discussions with Innovative, part of this comes down to the question of do you want to allow certain functions to be "overrideable". I would argue for cataloging records, we do not want to allow any overrides, but others might feel differently and should chime in via the comments with their ideas.
An error occurred while saving the comment Wes Osborn
commented
Most staff do not understand it when the override dialog pops up and they end up putting in their own account information again or opening up a ticket.
Wes Osborn
shared this idea
·
-
24 votes
An error occurred while saving the comment Wes Osborn
commented
I might quibble a bit with the "Deny" option, but I really like the idea in General and it might pair well with: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/50192763-putting-hindered-holds-more-prominent-so-all-holds
Sometimes it seems like hold processing is the only thing we can get staff to consistently process.
All this is to ultimately benefit the patron by moving requests and items more quickly through the system.
Wes Osborn
supported this idea
·
-
7 votesWes Osborn
shared this idea
·
-
30 votesWes Osborn
supported this idea
·
-
14 votes
An error occurred while saving the comment Wes Osborn
commented
What specifically are you attempting to do with the comparison? Get a list of records from one that isn't in the other or vice-versa? It might be better to do some searches to provide you with the results that you're looking for.
For the original poster, in case you are primarily looking to use this with Outreach patrons, this is a feature of the ORS module: https://documentation.iii.com/polaris/7.8/Default.htm#PolarisStaffHelp/Patron_Services/PPoutreach/Check_out_items_from_the_pick_list.htm
It would be nice to see this expanded to other record types if a library wanted.