Patron expiration date to match patron code
We have different time frames for different patron codes. For example a regular adult or child card is two years. We have others, such as a visitor card that is three months and several others. We would like the system to automatically adjust the expiration date to a pre-determined time frame set for each code.
Idea Value
Fewer mistakes made by staff. They often forget to adjust the expiration date for patron codes that vary from our default. Like many things, it's a 'training issue' and we try our best but with the size and turnover mistakes are made. This requires clean up then on our part.
-
Eric Lozauskas commented
Brainstorming a bit: If the Polaris database could have an additional field for each Patron Code for "Default Expiration" to be configured as a number in months "6, 12, 36, etc". Then, when selecting the patron code during patron registration, if Leap could automatically populate the correct expiration date from the "Default Expiration" defined with that selected Patron Code, this would simplify the patron registration process, reduce errors, and still provide the ability for the staffer to override by selecting a different expiration date or term.
Additionally, if when using the renewal functionality it also used the "Default Expiration" of that patron's Patron Code to select the correct renewal, that would be lovely!
Thanks for the consideration!