Settings and activity
125 results found
-
24 votes
An error occurred while saving the comment 
Emma Olmstead-Rumsey
supported this idea
·
-
18 votesUNDER REVIEW · 3 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
We'd really like to see item history entries added when no circ status change is made. This helps us find the true 'last touch' on an item and thus find things that are missing, or identify what staff member is making a pattern of errors. I know that would greatly increase the length of Leap item histories, but that could be addressed by customers choosing a shorter time period to display.
Emma Olmstead-Rumsey
supported this idea
·
-
8 votesEmma Olmstead-Rumsey
supported this idea
·
-
17 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Yes, please!
Emma Olmstead-Rumsey
supported this idea
·
-
6 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This would be such a nice enhancement! If you are scheduled on desk for a 1-hour shift, being told to wait 30 minutes and try again is not a useable solution. Especially if it's a night or weekend and there is no one with viable Leap/Polaris access to replace you on desk. Our staff end up sharing logins with one another in order to get work done, which is the exact opposite of the security protocol instructions we give them!
I'd also like to mention that I have a related request in that, until this solution is implemented, asks for a unique error message in Leap so that staff KNOW they are locked out instead of receiving repeated 'wrong password' messages, which encourage them to keep trying to log in and just extend the lockout period: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/48507272-leap-lockouts-due-to-incorrect-password-entry-shou
-
7 votesEmma Olmstead-Rumsey
supported this idea
·
-
11 votesEmma Olmstead-Rumsey
supported this idea
·
-
16 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
We would prefer this as a feature that could be opted into by individual Polaris customers. I like the idea but I anticipate a lot of staff and patron pushback if it were suddenly included in a future release and we couldn't fully control the timeline of implementing it.
Emma Olmstead-Rumsey
supported this idea
·
-
22 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is really important! Especially in a larger system or consortium where you have multiple sysadmins. I am currently training a new person and it's very difficult to gauge what he has and has not mastered since I can't trace changes back to any individual staff member in most cases.
Emma Olmstead-Rumsey
supported this idea
·
-
22 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
What a clever idea! We currently process these kinds of requests through email as well, and it's very inefficient. As Wes says, sometimes it feels like holds processing is the only thing you can get branch staff to do daily. It would be great to have the option to incorporate shelf checks into a more efficient, familiar workflow.
Emma Olmstead-Rumsey
supported this idea
·
-
18 votesEmma Olmstead-Rumsey
supported this idea
·
-
2 votesEmma Olmstead-Rumsey
shared this idea
·
-
46 votesEmma Olmstead-Rumsey
supported this idea
·
-
106 votesEmma Olmstead-Rumsey
supported this idea
·
-
18 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This would be a nice feature.
Emma Olmstead-Rumsey
supported this idea
·
-
14 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
We'd prefer this be an optional setting in sysadmin rather than automatic. Our system does not use patron associations and we would not want them created automatically.
-
11 votesEmma Olmstead-Rumsey
supported this idea
·
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is one of the most commonly-requested things by front-line staff for our system admins to run SQL queries for. Staff being able to do this themselves would definitely save us time, and it would provide better customer service by resolving the issues that generate these questions more quickly.
-
43 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Please, please implement this! We have a patron who has fines and an expired card who is regularly placing holds, collecting the held items from our self-serve hold shelf (which most libraries have...) and walking out with the items without checking them out. We are looking at hundreds of dollars of lost materials.
Emma Olmstead-Rumsey
supported this idea
·
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This should maybe be linked to this idea, too: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46813915-block-patron-hold-requests-in-the-pac-if-they-are
-
20 votesEmma Olmstead-Rumsey
shared this idea
·
-
23 votesEmma Olmstead-Rumsey
supported this idea
·
Yes, please! The patrons who are returning Lost items are typically the same patrons who are anxious to have their those items checked in immediately in order to resolve the blocks on their account so they can check out new materials.
In addition, having ANY exceptions to what can be handled by SIP check in/smart returns undermines any marketing message of "items will be removed from your account as soon as you put them through this slot." Libraries either have to add caveats to their advertising, which muddies the waters for patrons, or deal with patron frustration when "You said this would get checked in right away!" but it didn't.