Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
Linked to others proposals we submitted lately is another request from our client which deals with the customization of the registration form.
The aim through this feature is to collect data enabling him to improve his evaluation of his actions for his users. Data would be age, gender and others as already written in this proposal (https://meta.decidim.org/processes/roadmap/f/122/proposals/14381).
Obviously this is a sensitive matter regarding Decidim’s social contract.
Obviously this is a sensitive matter regarding Decidim’s social contract.
We thought about making the registration form customizable by the admin from the back office. The responsibility of collecting the data being his, the admin would have to justify in terms and conditions the collection of additional personal data.
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
View all comments
Conversation with Antti Hukkanen
To add to this, we have later found it would be useful to have this possibility also in addition to the authorization metadatas. Authorization metadatas serve a specific purpose for "sticky" data that is provided by the authorization provider, e.g.
In some instances admins would like to add extra information fields for the users that the users themselves could control under their profile information. I believe this is technically already possible in the user models but it would require creating the forms that allow collecting and validating this data before it is stored.
If this was added to the core, I would suggest it would be possible to control which fields show up on the registration form and which fields do not show up during the registration. Those fields that are not in registration, could be controlled under the profile information where you can currently control your name, email, nickname, personal URL and about description.
The field types that could be controlled could be similar to those that are right now available for surveys/forms. I vaguely remember seeing some conversation about this particular aspect but I couldn't find it after searching a while.
Hey Antti,
Here are two approaches that come close to what what you are describing
https://github.com/PopulateTools/decidim-module-extrauserfields (I like that you can export the data)
https://github.com/OpenSourcePolitics/decidim-module-sociodemographicauthorization_handler (User can edit the info inputed)
Would love to collaborate on something that would answer to all requirements
Thanks a lot Virgile for these reference implementations!
The first one (extrauserfields) is definitely to this direction that would be preferred regarding these needs. The fields would, however, need to be different but a similar approach would definitely work.
It would be great if these fields could be defined dynamically defined either in a config file or the admin/system panel. But I understand it's a challenge, not so simple to implemet.
Anyways, these are great resources, we'll think further when this comes to the table.
Loading comments ...