Registration/Renewal period based on patron code
We would like to be able to edit the default registration/renewal period based on the patron code rather than just based on the branch. We have certain patron codes that should renew for 1 year instead of our default of 3 years, but they don't have a unique branch in Polaris so we have to change the registration period each time we create a patron, and we have to change the renewal period each time we renew them, leaving more room for error if those steps are missed.
Anonymous
shared this idea
-
Beth Lane
commented
Yes, I'd vote for it! Love the idea.
-
Kevin Liberty
commented
This would greatly reduce the risk of data entry error
-
Stacey McClain
commented
This is a feature we had in our previous ILS that we really miss. It is very helpful and improves data accuracy.
-
Brandon Williams
commented
Great idea for patrons that are out of county or need other permissions. I like it.
-
Andrea Taylor
commented
This is definitely a must for us as well and would help greatly with staff entry error. We have multiple patron types with varying lengths and this would be a perfect solution.
-
Margaret Rose O'Keefe
commented
Not sure why this says Anonymous... it was my idea!
-
Carl Ratz
commented
We would like the expiration date to automatically be set based on the patron code. If the selected patron code is non-resident, then the expiration date would be automatically set to 1 year from the date already set or from today if the account was new. The update could be set with a button. This would allow for the account to be modified without affecting the expiration date when not needed.
-
Emma Olmstead-Rumsey
commented
This would be a great enhancement! My team reviews errors in new patron registrations, and the number one error we see is incorrect expiration date because the registration was for a patron type other than the 'default' and the staff member forgot to update the date.