Need permission to turn off Damaged Feature in Polaris 7.5
The Damaged feature in Polaris 7.5 was implemented without a permission to enable libraries to turn it off if they prefer their existing procedure. Because we can't turn it off and we have several hundred staff members, many new, all of whom do not have all our procedures memorized, some of the staff now use the Damage feature. This means that we now need a report to catch these transactions and extra staff time to undo them. To try to mitigate, we changed the string "Damaged" to "Do not use". It would be much preferred if a permission would allow us to hide the functionality from the UI entirely. (A permission or configuration allowing libraries to hide any new feature they don't want to use should actually be a requirement for every new feature since Polaris has so many libraries with widely varying procedures. No implementation will work for everyone.) Thanks for considering!
-
Miles Wagers commented
Totally agree with this! We're upgrading to 7.6 soon (from 7.4) and I'm running into the exact same thing. I like the idea of the new "declare damaged" workflow, but I don't think we're ready to move away from our current workflow at the moment. It would be so useful to be able to suppress the "declare damaged" options from both the check in window and also the patron record just to prevent items from ending up in this new circ status.
-
Emma Olmstead-Rumsey commented
Yes! We were on the fence about using it but ended up deciding to use it precisely because we didn't think we'd be able to stop staff from using it by accident.
The fact that the damaged 'status' is a sort of ghost status that only exists in Leap creates a lot of issues. It would be nice to be able to opt out of this new 'feature.''