I would use auth.User as is. When a new user (no existing django session) enters the code, django creates a user account (random username and password) behind the scenes and logs in the user. Then the user is identifiable as long as they stay on that machine. Set the logout interval to whatever you need for the experiment duration.
On May 19, 2010, at 2:50 PM, Junkie Dolphin wrote: > Hello everybody, > I am coding a django app for performing an online, anonymous > experiment system. The idea is that we give a login code to a group of > participants (e.g. students at our university) and tell them a > specific time window (usually a couple of hours) during which they can > login to the website using that code we gave them (hence no > registration required). Once they login the website randomly matches > pairs of participants for a game (the actual experiment). > > The key factor here is anonymity. We don't want participants to give > us any personal information, but still we need to identify each > anonymous user in order to do the random matching. > > What would be the best solution? I was thinking to use the builtin > authentication system but I don't know if it would be better to extend > django.contrib.auth.User or just use a plain form. > > -Giovanni > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
