Settings and activity
125 results found
-
10 votes
An error occurred while saving the comment 
Emma Olmstead-Rumsey
supported this idea
·
-
8 votesEmma Olmstead-Rumsey
supported this idea
·
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Yes, PLEASE!
-
12 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This seems like it really needs to be fixed. Why not have one system-level table for this and allow entries in it to be suppressed or not at different libraries/branches? That is what is done for a lot of similar items and seems to be much 'safer' in terms of potential for error.
Emma Olmstead-Rumsey
supported this idea
·
-
28 votesEmma Olmstead-Rumsey
supported this idea
·
-
40 votesEmma Olmstead-Rumsey
shared this idea
·
-
45 votesEmma Olmstead-Rumsey
supported this idea
·
-
8 votesEmma Olmstead-Rumsey
supported this idea
·
-
9 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Agreed. While the majority of our patrons really like auto-renewal, we regularly receive requests from patrons who want to opt out.
Emma Olmstead-Rumsey
supported this idea
·
-
10 votesEmma Olmstead-Rumsey
supported this idea
·
-
5 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Just curious Brandon, what is your current workflow? Before we allowed patrons to cancel held items themselves, staff would receive the request, pull the item, check it in, and choose "no" to the "continue to hold item?" prompt. We liked that because it stopped the item status from being changed until the item was physically removed from the shelf. I would worry with cancellation that staff would cancel the item in Leap and then get busy and never remove it from the shelf.
-
5 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
I think Authorized User must be a UDF field that your library has set up. I like the idea of having the option to have UDFs display in the header, but would not want this by default at our library.
Emma Olmstead-Rumsey
supported this idea
·
-
72 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is especially important with the addition of pickup areas in 7.5. We've gotten a lot of feedback from front-line staff that the pickup area information is not clearly visible on the hold slips and stuff gets mis-shelved.
Emma Olmstead-Rumsey
supported this idea
·
-
14 votesEmma Olmstead-Rumsey
supported this idea
·
-
34 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
Adding myvoice to the other comments. Many of our patrons believe our catalog IS our website, and the only way to reach them online is to display information directly on the catalog homepage as this would allow.
You can SORT OF do this now by adding a custom PAC banner, but it is very finicky, especially if you are hosted, and requires your library to have someone able to make a graphic that fits Polaris's requirements and a sysadmin who can quickly access this area at short notice.
Emma Olmstead-Rumsey
supported this idea
·
-
16 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is especially important since email notifications account for 90+% of most libraries' notifications, and with the way Polaris is set up, they are practically the only channel for almost due/autorenew messages, so even patrons who are signed up for a different notification method may still be receiving email messages with the incorrect name on them.
Emma Olmstead-Rumsey
supported this idea
·
-
46 votes
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
The inconsistency of this drives me crazy. Why can you search for 'digital but not physical books' but not for 'physical but not digital books'? It doesn't make sense, and more importantly, most of our ebook users are searching our ebook platforms (Libby, hoopla, etc.), not the PAC. The patrons using the PAC are specifically there because they want physical items.
Emma Olmstead-Rumsey
supported this idea
·
-
26 votes
This functionality will be included when we deliver the MEEP idea winner for this first cycle.
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This would have saved us a lot of grief when we launched LX Starter. We had lots of configuration issues between our City email server and Amazon SES, resulting in many notifications being marked as spam by receiving email servers and never delivered. If we had had the ability to test instead of having to go live with real notices to patrons, we wouldn't have had the interruption in service to patrons.
The issues also made our staff really pessimistic and cynical about LX Starter and Vega because that was their first experience with the platform. I told them how we were switching over to this great new service but what it did, from their perspective, was basically break email notices for a couple of months.
An error occurred while saving the comment Emma Olmstead-Rumsey
commented
This is vital. Our biggest issue with LX Starter has been message delivery, so being able to test the look of messages is less important than being able to test the delivery process.
Emma Olmstead-Rumsey
supported this idea
·
-
12 votesEmma Olmstead-Rumsey
supported this idea
·
-
17 votesEmma Olmstead-Rumsey
supported this idea
·
-
14 votesEmma Olmstead-Rumsey
supported this idea
·
Yes! We were on the fence about using it but ended up deciding to use it precisely because we didn't think we'd be able to stop staff from using it by accident.
The fact that the damaged 'status' is a sort of ghost status that only exists in Leap creates a lot of issues. It would be nice to be able to opt out of this new 'feature.''