Conditional Required State for Fields on Registration
We would like to be able to control whether or not a given field is required on registration based on the patron code selected. For example, we have a "No Permanent Address" patron code where ideally, address would not be required when that is selected. Or, we use one of our User Defined Fields for Parent/Guardian Information, which we would love to make required when a patron code indicating a minor is selected.
Kelsey Lied
shared this idea
-
Phil Agnew
commented
I like this idea and will point out there are many other potential applications for this. In addition to having a Guardian field, we keep school name data for student cards in one of our UDFs. I'm sure other libraries have additional contextual fields they're simply relying on staff to manage manually. Off the top of my head, I can imagine university libraries with faculty accounts having a tenured field or other such field that only applies to them, membership status for Friends of the Library patrons, organization information for institutional cards, etc.. Being able to enforce requirement options per Patron Code could be useful in a lot of different contexts.