Rework mandatory and optional fields in the registration form

[thom4parisot]

Initial requirement was:

Improve registration form (fields such as Title or Institution should not be mandatory, password length should be clearly indicated, etc.)

My thoughts on its current state:

• username: I don't understand why we ask this information (email sounds more sensible and unique as well); my hunch is asking for a username can already be a NO GO signal that make people fly away from the registration
• password: mandatory ,OK
• confirm password: mandatory, OK
• title: I don't think it's necessary — asking for gender has no value
• first name: it should be optional (GDPR is now live and we should be able to justify why we ask for this kind of personal data)
• last name: ditto
• organisation ~institution~: can be useful but should be optional
• e-mail: I suggest to make it the first field, and to complement it with an information that states it will be used as a unique login identifier on the website (again, maybe a GDPR statement somewhere to state emails are sent because of direct actions of the user on the website, no reselling, no spam, etc.)
• send request: I suggest we rename it as "Create account", or another label that suggests that an account will be created, and a confirmation e-mail will be sent to the aforementioned address.

---

• e-mail*
• password*
• confirm password*
• (first name ?)
• organisation ~institution~

[Create account]

---

Via @pzwsk, taken from #147.

[pzwsk]

Thanks, agree with most of suggestions, some comments though:

Currently, the username is showed on the dataset detail page. See for instance https://index.opendri.org/dataset_details.html?keyds=353

I was however thinking it would be better to show full name + organization with maybe the possibility to contact the person who submitted the info via a contact form, without showing email. Question being: what to show if those fields are optional? (anonymous).

I suggest to replace institution with organization which is more common.

[thom4parisot]

Yes, at this stage all this is only a proposal.

I suggest to write the "Contacting the person who submitted the info" as a separate issue. It's going to be easier to describe the expectations and to prioritize the item.

[CIMAManuel]

I agree with @oncletom for username/email fileds. I suggest to add a optional filed "Name to show" (optional) where the people can write a "public" name. The role can be:

1. Public name if exists or
2. The Name/Surname if there is at least one or
3. Organisation if exits or
4. E-mail So the user must add only a filed to preserve the email information.

A question: fileds Name and Surname could they be the same field?

[nastasi-oq]

username: I don't understand why we ask this information (email sounds more sensible and unique as well); my hunch is asking for a username can already be a NO GO signal that make people fly away from the registration

The reason was related to the possibility to refer to another user without necessarily see/know its email address, so it must be unique and required -> why not use it as login name too ?

[pzwsk]

Some thoughts on this:

• I think it is important to be able to identify the user in some way, so keeping username would make sense in the case user has not provided any name;
• We should not show emails;
• We could have robots as submitter in the future (for instance a robot harvesting data from the Open Data Index of Open Knowledge);
• We shall use US English on the website, as recommended by World Bank;

So here are my suggestions: username* e-mail* password* confirm password* name (optional) organization (optional)

with a mention that username, name and organization would be visible to everyone

By default we show username, if we have name and organization we show both instead

What do you think?

[nastasi-oq]

Not unique names are not so helpful to identify users. If you mean name "AND" organization:

• we must check that the couple is unique
• we must provide a way to associate the real user to the two provided field (with the risk to do typos on both field values).

[pzwsk]

Thanks,

from a db point of view, uniqueness is guaranteed by username. on FE we can show username (+ name and org if provided).

This would enable people to remain anonymous, through a username only, or to promote themselves and their org if they want to.

What do you think?

cc @oncletom @nastasi-oq @gracedoherty @CIMAManuel @dedandy

[gracedoherty]

Optional checkboxes for public information?

Username gracedoh_ When you submit a dataset, your username will be visible to anyone.

Name* _ [ ] Display publicly with dataset submissions

Organization _ [ ] Display publicly with dataset submissions

Email* _ Your email will not be shared publicly.

[pzwsk]

Final version below: