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 Virgile Deville
@ahu we are currently re-discussing how to implement this in Decidim ? Do you still think AH meta data is still the way to go ? We were thinking maybe we could use Decidim forms on the user profile.
Regarding controlling what the user can do, yes, the authorization metadatas are meant for controlling that.
But the usability for manual form-based authorizations is not really great right now. This works when we are using e-identification services since we get the data from a central digital registry automatically during the authentication process. But when entered manually, users have no idea what is an "authorization", how they can get to that view and why they should authorize themselves.
It works the best when this happens through an action they tried to perform but they did not have the right to do so due to missing authorization metadata. E.g. in the budgeting view, it shows a popup that data is missing and then they can authorize themselves after which they are redirected back to the budgeting view. This is quite OK right now.
So in my opinion:
1. The necessary backend functionality is already there through the authorization metadatas and action authorizers.
2. Entering of the manual form-based metadata is currently quite difficult and could be definitely improved, e.g. during the registration process. Not in the current registration form (users already feel it's too difficult) but the next step after that (it would be also a great place to show the sign up for newsletter which is currently missed for omniauth registrations). Entering this data during the registration process and changing it in the user profile would make it easier IMO but I'm not sure how to handle the case if there are multiple authorizations. Maybe you could define for the authorization handlers which of these fields should be displayed in the user profile form?
3. Some of the data should be marked "permanent" (e.g. date of birth cannot change) and some of it the user should be able to change.
Loading comments ...