It would be helpful if Patron Expiration Dates could be automatically determined by the Patron Code. For example, Adult patrons expire at three years while Reciprocal patrons expire at one year.

The city gets reimbursed for customers outside the city limits. It's important that these accounts expire each year and renewed so that we can get those funds.

This is something we really need -- the only patrons that are renewed for 3 years are resident patrons. Our libraries register other types of patrons on a daily basis and usually they neglect to change the expiry on those.

This is a great idea. We have libraries who are manually changing the Expiration Date for 3 months when they assign a 'New' patron code.

Yes, I'd vote for it! Love the idea.

This would greatly reduce the risk of data entry error

This is a feature we had in our previous ILS that we really miss. It is very helpful and improves data accuracy.

Great idea for patrons that are out of county or need other permissions. I like it.

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.

Not sure why this says Anonymous... it was my idea!

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.

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.