user - add option for dynamic purge date - e.g. 12 months after expiration date
Right now the purge date is a static value manually inserted when registering a new user. When the user renews registration, purge date must also be manually updated.
In our library regulations we'd like to purge users after a specific amount of time after expiry date. Keeping purge dates manually up to date is however quite an error prone procedure.
It would be great to have the chance to automatically update the value in purge date when saving according to specific a timespan (e.g. 10 months or 10 years after expiration date).
Good idea. It would also be better if the purge date will be automatically updated when we update expiry date.
Alex F commented
Great idea. It would be good to be able to use both options - as some sites are likely to have built processes round the Purge Date. Being able to purge based on an Alma set (generated from either Purge or Expiry date - or both) would be good. Would that work?
Patricia Farnan commented
This is a great idea. While we have logic in place for our SIS imported users, we don't have anything to help with internal users such as reciprocal borrowers, community patrons, etc. When I have a spare vote I will give this idea one!
Luigi Siciliano commented
I mean of course update the value in purge date when saving *the user*.
Emily Altman commented
We like this idea, but as other comments have mentioned, it would also be helpful to us if the purge date were related to the expiry date. Our official policy is for purge date to be one year after the expiry date, but often staff change only the expiry date. We would appreciate if Alma adjusted the purge date automatically, or even just created a pop-up (blocking a purge date earlier than the expiry date, for example).
Caroline Myrberg commented
Or if you could add a rule that automatically changed the purge date when you update the expiry date, because hardly anyone remembers to change purge date manually.
Scott Pfitzinger commented
I've been finding purge dates older than expiry dates, probably because they didn't get updated by staff when they updated the expiry date. It would be nice if the purge date could be calculated based on the expiry date. That way, we could run a job regularly that updates the purge dates to be a year (or whatever we choose) later than the expiry date.
Simon Read commented
Currently the patron purge functionality works based on the purge date.
It would be nice if there was an option to choose to use the expiry date rather than the purge date - we find that staff often forget to change the purge date when they extend the expiry date for patrons so using the expiry date would be more reliable.