Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add messages to users #144

Open
vsoch opened this issue May 7, 2016 · 2 comments
Open

add messages to users #144

vsoch opened this issue May 7, 2016 · 2 comments

Comments

@vsoch
Copy link
Member

vsoch commented May 7, 2016

  • reminders: should be variable associated with (hit? battery?) to send a reminder (custom message? pre-determined message?) This happens before time runs out.
  • credit / makeup: should be an email with a link to (the same hit to submit for approval? a new hit for credit? a canned message or custom?)
@IanEisenberg
Copy link
Member

I think the reminders should be associated with a HIT. I have a 10 hour battery, but sometimes make the HIT 6 days, sometimes 2 weeks, etc.

As we pile up the variables the need for a battery specific template HIT becomes important. It would definitely help and improve the user experience if I could define a template HIT which I can base new HITs off of. That we if I have to change one variable, but am okay with everything else I can.

We want to send a reminder(s) before the time runs out if the HIT has not been submitted. The canned response could just be
"This is a reminder that you have not yet completed our HIT, [HIT name]. You only have [time left] to complete it. Please do your best to complete the remaining tasks!"

I don't think we should give the option to inundate workers with reminders. Maybe give the option for just one reminder in 'days before end'?


As for make up - how would we link them to the "same hit to submit for approval"? There is no way for them to submit the HIT without finishing it. All they can do is release it.

Instead, an option to send an automatically generated dummy HIT would be excellent. This should definitely be a variable, thus allowing researchers to decide to manually respond.

An issue is that anyone can accept a dummy HIT unless you give the worker a qualification. This makes automatically doing this annoying.

@IanEisenberg
Copy link
Member

@rwblair

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants