Customize the New Patron Registration form
We would like to customize the New Patron Registration form to hide the fields that we do not use, such as Gender, Job category, and many others.
It would also be nice to have templates so that selecting a user group might display specific fields, the same way that choosing "User has institutional record" causes the password field to disappear and Owning system dropdown to appear.
It is now possible to configure the fields that appear in the Patron Registration and the Edit User Info (from the Manage Patron Services page) forms in Alma.
The new option makes it possible to configure a form that is fine-tuned to the library's needs and manages only the information the library wants to manage.
For more information see August Release Notes
-
The ability to hide fields in the patron registration form is planned to be released in the upcoming August 2022 release.
There are no plans to enable user form templates.
-
Stephanie Roach commented
Is this idea still planned? If so, which parts of it are planned--customizing the form fields OR form templates?
Please provide an update.
-
Melanie West commented
I see this shows as "Planned" as of June 16, 2019. Is there an update?
When can we expect this change to happen so the User Registration Form can be customized?
-
Melanie West commented
Making the form customizable as described above would be a huge help. Being able to add the secondary identifier from the same page would also be a time-saver.
-
Nan Clark commented
Any improvements that help the circulation desk operate more efficiently has my vote!
-
Daniel Múnera Willes commented
One of the most awaited features!
It does not only help with institution-specific use of those fields, but it also helps us to keep data clean and to avoid trusting on the memory of our staff, even though we are able to set fields as required.
If applied to production environment, please note that it should not only work on new user registration form but when editing user information tabs.
-
Manu Schwendener commented
+1
-
Karol Krakowiak commented
It's an absolutely must have feature.
-
Michael Johnson commented
In reviewing user data we intend to export to an outside server, we found a few instances where potentially confidential data was manually entered on fields where we do not normally import data, and where we do not wish data to be manually entered. These fields could potentially expose information that we consider confidential.
Consequently, we are interested in the ability to modify our configuration to block these fields from ever having data entered in them at all.
Specifically, the fields are: "Title", "Gender" and "Birthdate"
-
Nicola Carson commented
Fantastic idea - I've given it another 2 votes....
-
Dawnelle Ricciardi commented
I would love this!! Having all those useless fields makes no sense at all.
-
Tom Kistell commented
Yes! This would be ever so useful.
-
C Havely commented
I agree that templates would be most useful.
-
Christine Hinterhofer commented
Great idea. The form is quite overloaded, makes it more difficult for staff. Templates would help a lot.
-
Marco Tomassini commented
I strongly agree! It could be a useful simplification
-
Annelie Edelmann commented
This is a great idea -- especially since 3 "preferred" name fields have been added with the February 2019 release (as already mentioned below), which we do not intend to use! Wished I had votes left for this idea ...
-
Ulrike Joosten-Wilke commented
We fill out 7 of 21 fields in the User Information section. It would be less confusing and more ergonomic for staff if we could define a much shorter input mask.
-
François Renaville commented
This idea has become even more relevant now that three new fields have been added with the February 2019 release: Preferred first name, Preferred middle name, and Preferred last name. For libraries that do not use these extra fields, both "User Details" and "Register New Patron" forms have somehow or other become overloaded...
-
François Renaville commented
I strongly agree!
-
Anonymous commented
Less is more -- the forms should be customizable as Wendy indicates.