Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User attributes not clear #55

Closed
Matthijsy opened this issue Jun 26, 2019 · 0 comments · Fixed by #119
Closed

User attributes not clear #55

Matthijsy opened this issue Jun 26, 2019 · 0 comments · Fixed by #119

Comments

@Matthijsy
Copy link
Contributor

Currently the user fields are a bit of a mess. It is not clear when they are required and to which 'category' for the frontend they belong. I hope this issue makes this clear and makes it possible to implement this.

Column Group viewable create by board create by user required default
id technical always no no yes
username technical always no no yes
email general user_setting yes yes yes
first_name general always yes yes yes
last_name general always yes yes yes
last_name_prefix general always yes yes yes
birthday general user_setting yes yes yes
address general user_setting yes yes yes
postcode general user_setting yes yes yes
city general user_setting yes yes yes
phone_number general user_setting yes yes yes
study general user_setting yes yes no
start_study general user_setting yes yes no
food_preferences general user_settings yes yes no
vegetarian general user_settings yes yes yes
emergency_contact protected user/board yes yes no
emergency_number protected user/board yes yes no
picture_publication_preference privacy user/board yes yes yes always_aks
ifes_data_sharing_preference privacy user/board no yes is_activated null
info_in_almanak privacy user/board no yes is_activated null
almanak_subscription_preference privacy user/board yes yes yes paper
digtus_subscription_preference privacy user/board yes yes yes paper
user_details_sharing_preference privacy user/board yes yes is_activated null

The main difference with the current implementation is that some fields become required as soon as the user is activated.

Another option to fix this issue is to give everything a default and add a boolean which keeps track if the user should see the 'privacy check popup'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant