Settings and activity
60 results found
-
23 votes
An error occurred while saving the comment 
Christy Sayre
supported this idea
·
-
6 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
·
-
6 votesChristy Sayre
supported this idea
·
-
5 votesChristy Sayre
supported this idea
·
-
37 votesChristy Sayre
supported this idea
·
-
In a Consortium Environment, Have Home Library Float to the Top of Availability in Catalog Item Page
6 votesChristy Sayre
supported this idea
·
-
143 votes
An error occurred while saving the comment Christy Sayre
commented
Please fix this flaw. Because of this, we're actually hindering library service and wasting human resources throughout our system.
Christy Sayre
supported this idea
·
-
39 votesChristy Sayre
supported this idea
·
-
12 votesChristy Sayre
supported this idea
·
-
13 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.
-
36 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.
-
23 votesChristy Sayre
supported this idea
·
-
5 votes
An error occurred while saving the comment Christy Sayre
commented
If that ability is controlled by permission, those without the permission just won't be able to add a volume, which has a similar negative impact in a consortium setting, where some items might have a volume indication, correctly formatted or not, and others have no volume indicated.
Another idea might be the ability to create a drop-down selection populated with correctly and suitably formatted volume indication. -
15 votesChristy Sayre
supported this idea
·
-
6 votesChristy Sayre
supported this idea
·
-
9 votesChristy Sayre
supported this idea
·
-
21 votesChristy Sayre
supported this idea
·
-
20 votesChristy Sayre
supported this idea
·
-
69 votes
An error occurred while saving the comment Christy Sayre
commented
Yes, Please! We need something better, because the process of updating these to missing is too cumbersome. For each item, there's a series of steps:
they need to be checked in;
if there's a hold, refuse that;
but then reactivate the hold;
then it might want to transit to its home branch, so refuse that;
then there might be a block of some sort, so continue through that;
And this is all just to get the one item checked in.
You still need to mark it missing, which is a few more steps.
Imagine if have a list of 20 of these.Christy Sayre
supported this idea
·
-
65 votesChristy Sayre
supported this idea
·
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.