Settings and activity
24 results found
-
15 votes
Sheryl VanderWagen
supported this idea
·
-
5 votes
An error occurred while saving the comment Sheryl VanderWagen
shared this idea
·
-
8 votesSheryl VanderWagen
shared this idea
·
-
19 votes
An error occurred while saving the comment Sheryl VanderWagen
commented
I agree. For those of us in a consortium and for notice administrators this would be very helpful. Sorting works OK but not all of our members follow our instructions for naming conventions and so that makes it difficult when you have to help someone because something isn't working properly. In addition, several of our notice jobs are run by notice administrator centrally for everyone and it would be great if we could "Pin" those jobs to the top of the list, saving some extra clicks.
Sheryl VanderWagen
supported this idea
·
-
37 votesSheryl VanderWagen
supported this idea
·
-
37 votes
This idea was selected in MEEP voting for inclusion in Sierra 6.3.
An error occurred while saving the comment Sheryl VanderWagen
commented
We encounter this so many times and YES! 4 hours is way too long to keep a record locked and frontline staff have no idea what causes this message as a rule, so we're always explaining what might be the cause (although we never really know the reason) and patrons certainly don't understand why that staff member can't help them right now. It has also caused problems with our Bibliocommons catalog and fines payment through it where the payment is accepted and patron credit card charged but then the charges never clear the record in Sierra. That causes an even larger PR problem (thankfully these occurrences are rare but even rare is too often!)
Sheryl VanderWagen
supported this idea
·
-
12 votesSheryl VanderWagen
supported this idea
·
-
8 votesSheryl VanderWagen
supported this idea
·
-
36 votes
The product manager will review this idea for possible inclusion in a future release.
Sheryl VanderWagen
supported this idea
·
-
36 votesSheryl VanderWagen
supported this idea
·
-
16 votesSheryl VanderWagen
supported this idea
·
-
35 votesSheryl VanderWagen
supported this idea
·
-
70 votesSheryl VanderWagen
supported this idea
·
-
51 votes
An error occurred while saving the comment Sheryl VanderWagen
commented
I just went through our many many loan rules to set up the additional courtesy notice and was wishing the same thing. But I would, at the same time, be extremely nervous about doing this globally. I kind of wanted to see each one as I was doing this. I wonder if this would really be worth it, for the frequency it might be used weighed against the potential "damage" that can be done.
Sheryl VanderWagen
supported this idea
·
-
58 votesSheryl VanderWagen
supported this idea
·
-
54 votes
This idea has been selected to include in Sierra 6.4
An error occurred while saving the comment Sheryl VanderWagen
commented
This would also be a great feature for Patron Record creation. On our system, this is where I've received the most comments about wanting to go back. It would really help those situations where staff DOESN'T go back and fix things. So I like the "any record" option, not just for bib records.
Sheryl VanderWagen
supported this idea
·
-
58 votes
An error occurred while saving the comment Sheryl VanderWagen
commented
This would be very helpful. We don't have a lot of individual user accounts, this would be great to be able to change for either staff changes and/or name changes
Sheryl VanderWagen
supported this idea
·
-
82 votes
This idea has been selected to include in Sierra 6.4.
An error occurred while saving the comment Sheryl VanderWagen
commented
Automation of this process would be really great as would also the ideal of not changing the updated date. In our consortium, since the process is manual, I don't run this until I've created some of our monthly reports that use that updated date. So for us, its always been done the 3rd weekend in January. In regards to the updated date, at one time (maybe back to Millinnum - I don't remember exactly when). At one time, not updating this date had been reported as a bug which was later "fixed". Those of us who used it up until that time were caught off guard when that fix was implemented. At that time, there were several requests at that point to put back the old behavior. So it seems to me that over the years, some want the updated date to change and others don't so making it an option might be a better choice along with being able to set the time/date when the the process is run.
Sheryl VanderWagen
supported this idea
·
-
47 votesSheryl VanderWagen
supported this idea
·
-
25 votesSheryl VanderWagen
supported this idea
·
Was asked about this functionality using Sierra Web. We are a 40 member consortium and so for us to put users on Sierra Web is impractical at this time (on any given day we have 300+ SDA logins). I was notified that this can be done in Sierra Web but since most of our staff logins use the SDA, for them to switch between the SDA and Sierra Web to do this, is not really feasible.