Settings and activity
45 results found
-
57 votes
An error occurred while saving the comment 
Christy Sayre
supported this idea
·
-
58 votesChristy Sayre
supported this idea
·
-
82 votesChristy Sayre
supported this idea
·
-
15 votesChristy Sayre
supported this idea
·
-
19 votesChristy Sayre
supported this idea
·
-
148 votesChristy Sayre
supported this idea
·
An error occurred while saving the comment Christy Sayre
commented
Thank you for keeping this under review! Our circulation staff would like to see a better indication that the display items should be handled differently when being checked in. It's not enough to put them in their own Shelf Location, because when items are checked in, the shelf location isn't announced, nor is the Temporary Location, if used.
Ideally, there would be some indication to set them aside to be returned to that display.
Some of the circulation statuses have special properties, for example Bindery items cannot be checked out. If there was a Circulation status of Display which had a special property, such as a popup of some sort, staff could return them to the special display to be rediscovered by the patron. Even a column in the Checked in items list that could show the Display circulation status or shelf location (or both--see screenshot) would be an improvement and could help staff determine at a glance what items should be shelved differently.
Thanks again for keeping this idea open. -
90 votes
An error occurred while saving the comment Christy Sayre
commented
In our consortium, we provide library staff with SimplyReports logins and train them to find their way around creating reports. So all of the different format options Daniel suggested would be all the different ways, potentially, that the many folks aside from admins could want to format their reports. So please, we hope you're planning to improve this.
Christy Sayre
supported this idea
·
-
7 votes
An error occurred while saving the comment Christy Sayre
commented
Glad to hear that! We'd love to see a smoother procedure for self-registration in Vega--let me know if we can do any testing or help otherwise.
An error occurred while saving the comment Christy Sayre
commented
Appreciate that pointer, Gabrielle. Happy to report that it's working with a requirement to include date of birth.
In examining the options at this level, we discovered the option to include a warning that users must be 13 or older to complete the registration form. However, this can only be configured for users who choose "If you are not registered for library services, click or tap here to register now" from within PowerPAC's login link. Our patron registration begins with a link in Vega Discover, which takes them to the page that comes up *after* the patron clicks the above-mentioned link, so unfortunately our users will not see the warning.We'd love a way to be able to deploy this COPPA warning in our Vega Discover setting.
An error occurred while saving the comment Christy Sayre
commented
Hi Gabrielle, thanks for pointing that out--we hadn't seen that option. Just requiring a birthdate may be the answer, and it's not a bad piece to require anyway.
Christy Sayre
shared this idea
·
-
27 votesChristy Sayre
supported this idea
·
-
47 votes
An error occurred while saving the comment Christy Sayre
commented
Some patron-identifying fields would be helpful in our consortium, particularly Patron code, but possibly patron assigned branch. This would help libraries decide whether to fill the hold and could ultimately lead to better service.
Christy Sayre
supported this idea
·
-
28 votesChristy Sayre
supported this idea
·
-
32 votesChristy Sayre
supported this idea
·
-
33 votesChristy Sayre
supported this idea
·
-
37 votesChristy Sayre
supported this idea
·
-
77 votes
An error occurred while saving the comment Christy Sayre
commented
I recently had a request for this from staff in one of our libraries, and discovered there's not an ideal way to add this info, so I would like to see a data well for this.
Christy Sayre
supported this idea
·
-
68 votesChristy Sayre
supported this idea
·
-
85 votesChristy Sayre
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for consideration in an upcoming release.
An error occurred while saving the comment Christy Sayre
commented
As an administrator, this would be a huge time-saver. It's very difficult to line up a real-time test of a service like this.
Christy Sayre
supported this idea
·
-
4 votes
An error occurred while saving the comment Christy Sayre
commented
We have a growing number of app users, and it would be a nice additional way for staff to push out quick messages to individual patrons -- "we've been trying to reach you!" "You left your library card here, we're keeping it safe"
Christy Sayre
supported this idea
·
-
75 votes
An error occurred while saving the comment Christy Sayre
commented
The notices in their current form, while nice to look at, are very confusing and we receive constant questions about it.
Christy Sayre
supported this idea
·
.JPG){kind=link}
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.