Settings and activity
76 results found
-
4 votes
Christy Sayre
shared this idea
·
-
8 votes
An error occurred while saving the comment
Christy Sayre
supported this idea
·
-
72 votes
An error occurred while saving the comment
Christy Sayre
commented
This is something we really need -- the only patrons that are renewed for 3 years are resident patrons. Our libraries register other types of patrons on a daily basis and usually they neglect to change the expiry on those.
Christy Sayre
supported this idea
·
-
12 votes
An error occurred while saving the comment
Christy Sayre
commented
Even with "Credit for Overpayment" set to No and staff permissions removed for "Create a Patron Account Credit", the system doesn't prevent them from creating a credit when a lost and paid item is recovered.
Christy Sayre
shared this idea
·
-
38 votes
Christy Sayre
supported this idea
·
-
68 votes
Christy Sayre
supported this idea
·
-
48 votes
An error occurred while saving the comment
Christy Sayre
commented
This would be a huge timesaver. We already use Leap, but it would save time and be less confusing if we could see remote records side by side with our existing ones within Leap. Switching between tabs in the browser or scanning across different browser windows introduces a drag on continuity of the workflow and slows down decisionmaking.
Christy Sayre
supported this idea
·
-
5 votes
Christy Sayre
supported this idea
·
-
49 votes
Christy Sayre
supported this idea
·
-
16 votes
Christy Sayre
supported this idea
·
-
41 votes
An error occurred while saving the comment
Christy Sayre
commented
Getting undelivered txt reports and it's hard to determine where it's coming from--hopefully that will slow down quite a bit when this is enabled and we'll stop being concerned/following up one at a time with patrons.
Christy Sayre
supported this idea
·
-
11 votes
An error occurred while saving the comment
Christy Sayre
commented
In general, it would be helpful to tie the expiry date to the patron type, and let us configure it. In our consortium, only Resident patrons have a 3 year expiry. All others, such as Non-Resident, Teacher, Student, Reciprocal, have a 1 year expiry, and frequently, changing that due to patron type is overlooked, which is difficult to clean up.
Christy Sayre
supported this idea
·
-
5 votes
Christy Sayre
supported this idea
·
-
43 votes
Christy Sayre
supported this idea
·
-
In a Consortium Environment, Have Home Library Float to the Top of Availability in Catalog Item Page
14 votes
Christy Sayre
supported this idea
·
-
159 votes
An error occurred while saving the comment
Christy Sayre
commented
Please fix this critical flaw. Because of this, we're actually hindering library service and wasting human resources throughout our system.
Christy Sayre
supported this idea
·
-
61 votes
Christy Sayre
supported this idea
·
-
17 votes
Christy Sayre
supported this idea
·
-
34 votes
An error occurred while saving the comment
Christy Sayre
commented
...or just include the date the item was returned. This is a common question our libraries hear from their homebound patrons.
-
43 votes
An error occurred while saving the comment
Christy Sayre
commented
We like the 24-hour idea. We'd also like to see the system use the Trapping Preferences to favor local patrons' holds when items are receiving final steps in the cataloging process and are scanned (check-in). At this point a year into our Polaris journey, we're only just discovering that the Trapping Preference does not always favor the hold for the local patron, but only does so when an eligible item is being checked in from the Out status, or if the item was scanned into the check-in workform without already having been linked to a Pending request.
The arrangement of the info is definitely confusing. Staff really are looking for either the last borrower, or info about the current loan, so that mock-up (lastCircB) nicely arranges this info in a way that's more clear.