Settings and activity
100 results found
-
14 votes
Emma Olmstead-Rumsey
supported this idea
·
-
47 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
supported this idea
·
-
5 votesEmma Olmstead-Rumsey
supported this idea
·
-
17 votesEmma Olmstead-Rumsey
supported this idea
·
-
20 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Now that Pickup Areas were added in 7.5, this feature is even more crucial. I don't see how implementing it could break any existing workflows, either.
Emma Olmstead-Rumsey
supported this idea
·
-
16 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Isn't this how "blocking notes" work? Despite the "blocking" in their name...
-
68 votesEmma Olmstead-Rumsey
supported this idea
·
-
17 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
A colleague mentioned to me that if a library has preferred pickup LOCATION turned on, the patron will see a "make this my default" checkbox that appears below the pickup area dropdown menu, strongly suggesting that default pickup area is supported even though it is not. If this support can't be added, could the wording on the box be updated to clarify that checking it will only set the pickup branch, NOT the pickup area within that branch?
Emma Olmstead-Rumsey
supported this idea
·
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is key for libraries to be able to implement Pickup Areas without feature loss. We are one of the many libraries that set up a whole extra branch for a second pickup area in the same branch. We wound that branch down and now we have a lot of crabby patrons who feel like they LOST the ability to choose their preferred pickup spot when this feature was turned on.
-
5 votesEmma Olmstead-Rumsey
supported this idea
·
-
57 votesEmma Olmstead-Rumsey
supported this idea
·
-
13 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is a really good idea. Like Nicole, we still have specialized staff using the client, but most staff are on Leap. We'd benefit from this feature.
Emma Olmstead-Rumsey
supported this idea
·
-
7 votesEmma Olmstead-Rumsey
supported this idea
·
-
13 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Yes, please! We are hosted. I would honestly take mandatory patching on Polaris's schedule over the system now, where a patch is available but doesn't get applied until I find the problem it's designed to fix and create a support ticket for it.
Emma Olmstead-Rumsey
supported this idea
·
-
43 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is a clever idea! We would definitely use this as Daniel suggested to communicate actual information to staff--similar to how after you log into something after it's updated to a new version, many programs and sites have a banner at the top alerting you to the changes.
-
10 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Yes, please! Something like "barcode not found" would be much more helpful.
Emma Olmstead-Rumsey
supported this idea
·
-
10 votesEmma Olmstead-Rumsey
shared this idea
·
-
42 votesUNDER REVIEW · 7 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
I agree with Miles--we initially adopted this workflow and reverted back to our old one in part because of this problem. Since 'declared damaged' is weirdly only a status in Leap, and not its own status in the underlying client, none of our processes to review and delete records for items we no longer have would work with this status. We would only start using the workflow again if the status were regularized and this feature were added.
Emma Olmstead-Rumsey
supported this idea
·
-
12 votesEmma Olmstead-Rumsey
supported this idea
·
-
13 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Yes, please! We would definitely use this feature.
Emma Olmstead-Rumsey
supported this idea
·
-
21 votesEmma Olmstead-Rumsey
supported this idea
·
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
I believe cancellation notifications can be toggled on and off at a high level, but I like the idea of doing it more granularly.
We have cancellation notices turned off globally in our system precisely because we can't have them turned on without sending a million of them for every single unclaimed item. We don't float, so a held item that went to unclaimed will have been pulled off the shelf and put into our delivery run the next day. That's just about when the patron gets the cancellation notice and contacts us to say "wait, I still want that!" Then they have to wait a few days for it to be pointlessly chauffeured to its home branch, only to fill a hold and go straight back to the one it was just at on the hold shelf. My previous system did have those notices turned on and it created a LOT of frustration for patrons.
Yes, please make this change! The very fact that the same action has different permissions depending on the access point or workform used to potentially make the change is already bizarre. The fact that there's a permission allowing someone to take action X on 1,000 records but not on one record just makes it worse.