[Yanel-dev] Registering user information

[Guillaume Déflache]

Michael Wechner schrieb:
> Hi

Hi!


> I have form which people need to submit their name, address, etc. in 
> order to be able to download a white-paper.
> 
> I would like to register these people as users within Yanel, because at 
> some later stage they might be using more services
> and hence need a password, etc.
> 
> Here my questions/concerns
> 
> - Does it make sense to register such users as regular  Yanel users (via 
> the IdentityManager)  without password?

I think it does, they may be "incomplete" users but the goal is still 
that they may become full-fledged users (especially those who may end 
contributing metadata (ratings, tags) or even content).

Although we have to be careful that this does not force us to 
authenticate these users as other more internal users that may have to 
use LDAP, some kind of SSO, etc.

And finally we may also only use the same Java interfaces and code but 
clone the UI to segregate contacts/leads from real users into separate 
screens with different credentials.


> - What about user-id? (because it doesn't make sense to ask for a 
> user-id in the first stage)

As Bruno suggested we may user their E-mail (if they gave it to us; 
anyway don't forget we may always need E-mail/SMS confirmation to avoid 
spamming...)
Or we may hash all the contact information they gave us for example; it 
would be rehashed when the user wants to change its real name or other 
data and cannot find himself anymore! Then maybe if we really need 
logins for nicknames as such those should be in a separate field.


> - What about the scalability of the Yanel user management interface?

Asking many more or less personal data should ensure not too many people 
register at the beginning! ;)
More seriously we would have to make any other contact/lead managment UI 
scalable anyway, so why not this one?
There are already several XXX/FIXME/TODO notes in the code itself, maybe 
start looking there.
For now I think up to 100-200 users may be OK, even if painful 
usability-wise.


Cheers,
    Guillaume