Okay - I’ll do my best transcribing this from our Circulation Head!
There’s been instances where we’d like to resend notices in Vega - things like our autorenewals, late notices, and hold notices. We have them on a schedule, but a couple of times things have happened where the first ones of the day didn’t go out. In Sierra, we were able to do that, but we were told we cannot do that in Polaris, and I just wanted to check in with all of you to make sure that was accurate. If we can do that, could you let me know how?
There is not a way to resend. Do you know what might be causing issue with your first ones not going out? I know some people have mentioned that notices werent going out when they expected them to and realized they needed to adjust their schedule in LX Starter to better coincide with the times the jobs run on the server.
Thank you, Katie! I forwarded your message to our Head of Circ. Here’s what she said: I reset all the due dates for that day affected (forwarding an extra week) and all these items were picked up in future notices and autorenewals.
I guess any time our system updates, I will have to watch for this glitch. Not ideal. I wish Polaris had a suggestion on how to avoid that.
Sorry - one more note from her: I’m wondering if we just make sure our updates are done very late in the day or overnight moving forward? Our last notices go out around 8 pm.
I had to adjust the timing of our notices in LX starter as she mentions.
If you mean system upgrades, you can talk with Clarivate about making those in off hours. It is typically a paid service, and there are limited upgrade window days when it can be done because of limited staff. But it is worth it for us. We still do have to go back and check over all our SQL jobs to make sure none of them got missed and we need to rerun them.
