Create a Back End Updating Feature
A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.
So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the patch installed, and I said yes, please do that.
But step back and you see the problem. This was a known issue. And there was a patch. So... why not just patch the system? I think there needs to be some kind of updating feature for ILS admins where we can see a list of available patches for known issues with our build of Polaris. And then, if we're seeing those issues, or we can recreate them, we should be able to install the patch from that updating system. This would be something like Windows Update or Discover in KDE. Applications of patches should be left to the discretion of the local ILS admin team, but at least they'd know there were issues and solutions are available for them.
Daniel Messer
shared this idea
-
Lynn Reynish
commented
We had a notification option available to us when our library was on Horizon. If you wanted to, you could run the patch yourself or you could schedule it with a technician. I will note that point upgrades also worked that way and I ran a few on my own but scheduled others with support.
That said, the relationship between customers and Dynix support was quite different back then in many ways and I'm with Wes in being happy with a simple notification option for known issues at this point.
-
Wes Osborn
commented
I commend the attempt to shoot for the moon on this one, but I'd also be happy with just a way to get a push notification when something is added to the Known Issues list - you used to have that option, but I don't think it works in the new supportal anymore.
Given that Polaris has never really been self-patchable and with more libraries moving to hosting I feel like that only becomes more so, it feels like finding another middle ground is likely needed.