Settings and activity
100 results found
-
8 votes
Emma Olmstead-Rumsey shared this idea ·
-
14 votes
An error occurred while saving the comment Emma Olmstead-Rumsey supported this idea ·
-
21 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
This would be very helpful! We have patrons who use the card mainly for accessing computers/devices. The access management software isn't sophisticated enough to pass anything back to Polaris, so someone could renew their card, hop on a computer that day, and then visit every day for the next month for a computer session and it wouldn't be reflected in Polaris at all.
Emma Olmstead-Rumsey supported this idea ·
-
6 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
Yes, please! Since there are such a variety of devices, browsers, and settings, it's challenging to talk a patron through clearing their cache. And that only helps the small fraction of patrons who contact us--most patrons just continue to see the outdated information and we never even know.
Emma Olmstead-Rumsey supported this idea ·
-
9 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
We actually already do this. We program DL-capable scanners, though. We've been working with Bayscan and it's been pretty easy.
-
14 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
This would be very valuable for addressing patrons correctly. I'm sure the customers that use titles would like the ability to include them. We use a UDF in our library for parent/guardian name on children's accounts, and it would be nice to address the notice to the parent/guardian when something was present in that field and the notice is going to the parent's email address, not the child's.
We'd also like the ability to include preferred name in notices instead of legal name (we use a clunky swapped setup in our instance of Polaris to keep the legal name fields mandatory, so the "name" fields that are merge tags are legal names for us, not preferred names).
Emma Olmstead-Rumsey supported this idea ·
-
17 votes
We will consider this idea for possible future development. Thank you!
Emma Olmstead-Rumsey supported this idea ·
-
31 votes
We will consider this idea for possible future development. Thank you!
Emma Olmstead-Rumsey supported this idea ·
-
13 votes
Emma Olmstead-Rumsey supported this idea ·
-
17 votes
Emma Olmstead-Rumsey supported this idea ·
-
31 votes
Emma Olmstead-Rumsey supported this idea ·
-
13 votes
Emma Olmstead-Rumsey supported this idea ·
-
37 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
We have a large branch that has a drive-thru window far away from our interior holds pickup area. Because you can't have multiple pickup locations at one branch, we actually created a second branch called "drive thru" so that patrons can indicate where they want their holds to go. Staff at this location are constantly switching back and forth between their branch's regular login and the 'drive thru branch.' This would save them a lot of time!
Emma Olmstead-Rumsey supported this idea ·
-
41 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
This would be a great enhancement! My team reviews errors in new patron registrations, and the number one error we see is incorrect expiration date because the registration was for a patron type other than the 'default' and the staff member forgot to update the date.
Emma Olmstead-Rumsey supported this idea ·
-
18 votes
Emma Olmstead-Rumsey supported this idea ·
-
26 votes
Emma Olmstead-Rumsey supported this idea ·
-
11 votes
An error occurred while saving the comment Emma Olmstead-Rumsey commented
If implemented, please make this a setting in SA that can be turned on or off! We use Claims Returned as a 'you don't need to worry about this anymore' status for patrons and it would cause us a lot of problems if Claimed items began to automatically revert to Lost.
-
31 votes
Emma Olmstead-Rumsey supported this idea ·
-
49 votes
Emma Olmstead-Rumsey supported this idea ·
An error occurred while saving the comment Emma Olmstead-Rumsey commented
We use Leap exclusively for front-line work EXCEPT we still use the offline version of the Polaris client for this very reason. We struggle whenever we go offline because our staff is no longer familiar with the client at all. It's as though they are being asked to use two completely unrelated systems that just happen to access the same databases. It would be great if Leap Offline could be modified to reduce the risk of losing transactions.
-
37 votes
We will consider this idea for possible future development. Thank you!
Emma Olmstead-Rumsey supported this idea ·
This would save a lot of time! Thank you for posting this one.