Idea #3296
Updated by Ward Vandewege over 9 years ago
Example form fields: Form fields we want to collect: * Institution/Company (required) Title * Lab Organization * Website URL * Title * What best describes your role (dropdown): Bio-informatician Computational Biologist Biologist/Geneticist Software Developers IT Other Education (BA, Masters, PhD, etc.) New behavior and implementation notes: * Add a link in the email address dropdown menu in Workbench called 'Edit profile'. * Add a new page (@/users/{my_uuid}/edit@) with a form allowing the user to add/edit profile data. * Get the list of form fields from the @user_profile_form_fields@ configuration value, which should be a hash of profile_key → [form_field_title, form_field_description]. * Store the values in user prefs: @current_user.prefs["profile"]["title"]@, etc. * On the "edit profile" page, display (but not offer to edit) the user fields that get populated automatically during the OpenID login process (email, first name, last name, identity_url). * Add comments to @application.defaults.yml@ showing how to add profile fields. * The default configuration should be an empty hash (i.e., no form fields are shown, and the link to the "edit profile" page is removed from the email address dropdown menu). * If the @user_profile_form_fields@ configuration hash is non-empty, and the current user's prefs["profile"] is nil or empty: ** Redirect most[1] dashboard pages to the "edit profile" page. ** Add an alert panel to the "edit profile" page asking the user to please provide the following information. fn1. Avoid constructing a catch-22 where (for example) the user agreement cannot be signed until the profile is edited, and vice versa.