[OpenMadrigal-developers] Suggestion for Madrigal user data
William Rideout
brideout at haystack.mit.edu
Thu Jan 27 11:42:12 EST 2005
Suggestion by Ingemar Häggström at Eiscat:
********************************
One thing that we have came across is
that users have downloaded faulty data, which we then have replaced.
But, we don't know whom to tell (that the data was wrong) about it.
So, maybe one could add something to the notes file, whenever someone
downloads data.
IP number and ask for name and email address should be enough. Then, one
also get a record how many is using the data...
I guess one would allow for dummy names/email, but then it's not our
"fault" if they work with bad data..
********************************
Bill Rideout commentary:
This situation could also apply to data that is reprocessed using an improved
algorithm, not just to the case of the original data being faulty.
This could be accomplished by requiring the user to fill out this information in
a form each time they enter a Madrigal site.
A second option is to use the same approach that Madrigal now uses to store user
filter information. To save a filter, a user creates a login that does not
require any permission. That login is meant for identification only, so
security is not an issue. This login is saved as a cookie on their browser, so
they never need to login again unless they change browsers or computers. As
Ingemar says, this doesn't guard against dummy information, but in that case
they simply don't receive this update information.
A third option is to simply make the second approach optional - there would be a
line at the top that says something like, "If you'd like to be notified whenever
a dataset you examine is updated, please login here". If the user was already
logged in, the line would say "You will be notified if any dataset you examine
is later updated."
Any thoughts?
Bill
--
Bill Rideout
MIT Haystack Observatory
Email: brideout at haystack.mit.edu
Phone: 781 981-5624
More information about the OpenMadrigal-developers
mailing list