05/31 - Funky Friday!

[GTR]

Looks like the bubble bath worked.. Zoya is laying on my bed watching Dave & Ava trying to recover from the trauma of food coloring

don't let her get ahold of glitter

 

[thismegan]

Scrambled Eggs PopTarts

Toaster Scrambles are/were OK from what I remember...

PE $19.55, and I'm pretty sure I picked the best article from that Searle Center HIT, so +$4.00 bonus.

 

[Kristina M Greer]

don't let her get ahold of glitter

haha for real.. I have tons of that stuff, plus bunch of rhinestones, which when she was younger knocked a bunch off my desk when i was working on something. you know how hard it is to pick that stuff out of carpet lol

 

[JenniLeigh]

and I'm pretty sure I picked the best article from that Searle Center HIT, so +$4.00 bonus.

Ooooooh.... it didn't say anything about the bonus at the end, so I assumed it was fake o.0

 

[HelloHello]

Toaster Scrambles are/were OK from what I remember...

PE $19.55, and I'm pretty sure I picked the best article from that Searle Center HIT, so +$4.00 bonus.

They are good!

 

[HelloHello]

Mass shooting Virginia Beach just reported - 11 dead.

 

[Our Research]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

 

[C to the J]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

It's all good ImpactStory.
Mturk doesn't make figuring out these things easy and no one blames you.

So those of us who passed (got a 44 myself) aren't going to need to take again though, correct?

 

[JenniLeigh]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

Thank you for coming to clear up the mishaps, and relieving some tension. You're very busy, and it always means a lot to us when requesters take the time to care.

 

[Kennedy]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

Thank you for the clarification.

 

[Robedom]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

Appreciate the clarification and excited to (hopefully) work on the full hits. Thanks for working hard to get everyone paid as well!

 

[Our Research]

It's all good ImpactStory.
So those of us who passed (got a 44 myself) aren't going to need to take again though, correct?

No, I don't think so. The 95% qualifying score on the last version was 43 and we're going to run with that. It's not great but at this point and with the tools we have available we have to choose between people feeling ripped off for doing the qual and not getting paid, or people being (understandably) irritated at missing out. The second option seems less bad.

 

[GTR]

I take it it's too late to take the qual for the Impactstory HIT's now

lol

 

[Kristina M Greer]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

Thanx Richard you are awesome as always

 

[LowCalCalzone]

I take it it's too late to take the qual for the Impactstory HIT's now

lol

Got a 42 score when I took it yestserday

 

[JenniLeigh]

Man, it died.

I guess I'll take a poultry break before I fill the gap with Georges...

 

[dreamonjaded1]

Mass shooting Virginia Beach just reported - 11 dead.

This world has gotten ridiculous!

 

[C to the J]

I take it it's too late to take the qual for the Impactstory HIT's now

lol

This guy.

 

[Kennedy]

So here's what happened with that qualification test mess yesterday:

The idea was to have detailed training and a test that would take half an hour to an hour, and use a qualification to record the score on the test. I felt this was too much to ask for without paying people, so I put a batch of do-nothing HITs behind the qual so people could get paid for them after the test. We only wanted to qualify 25-50 people or so to start and the limited number of HIT assignments was supposed to accomplish this.

The first problem was that you could hit the "get paid for trying" threshold by answering "yes" to every question. There were a lot of these submissions. I updated the test figuring that retaking it wouldn't be a big deal since it wouldn't take nearly as long as the first time. This caused a bunch of confusion about what score was needed, with 4 different numbers floating around.

Second problem: I assumed HIT assignments would be held while people took the test. They aren't. So a lot of people took the test with the promise of a paying HIT behind it which then disappeared. I spent most of the last work day trying to get these people paid.

The third problem, and ultimately the reason we pulled the qualification, is that there's no way to close the test except to delete the qualification and copy everyone's scores to a new one. As some of you discovered, this means it gets deleted while people are in the middle of the test. This is even worse since I have no way to verify who this happened to and I can't just be a money piñata.

We're looking for a small enough pool of qualified workers that I should have just done a normal qualifying batch and processed it manually. Sorry for the frustration and drama it stirred up. For the record, I'm not aware of any answers having been shared.

I also want to thank you for taking the time to not only pay those who worked on that qual, but for stopping in here and explaining things. People in here want to do their best for each requester, and just like requesters, we occasionally get burned. It is a good feeling to know that you have an interest in the well-being of the people who are willing and want to do a good job for you.
Thank you.

 

[mboone73]

Man, it died.

I guess I'll take a poultry break before I fill the gap with Georges...