hi, as a requester, i can set 1. "HIT expires in" x days 2. "Results are automatically approved in" x days I've sign-in as a worker and saw that these 2 settings are not viewable by a worker. I'm wondering, do workers care about these 2 settings? For example, if i'm a worker, i would like to know when will my work be approved. But it seems there's no way to find out as a worker until the hit has been submitted and a worker can only wait for approval (not knowing when it will be approved)? Am asking since I want to be a creditable requester and build trust with workers
Well, workers who have installed a script are able to see when HITs will automatically be approved, to me, personally it's very helpful to know that. As for seeing when the HIT expires, I'm not sure if such a script exists, that's not something important to me, however.
A script is not even necessary - viewing the source code and searching for “hitAutoAppDelayInSeconds” reveals the number. So there is really nothing hidden from those who truly want to know.
1. Always shown. Like this, for a random HIT. HIT Expiration Date: Jun 26, 2012 (6 days 23 hours) 2. What khalinov said. If you want to build trust with the workers then make sure you read the policies so you're not requesting things that are against policy. Keep doing that and you'll receive bad reviews on turkoptican, in forums, etc. Workers don't trust people that put up questionable HITs.
thanks for helping, folks. izzxpopz, may i know where can i get that script? Khalinov, looks like "hitAutoAppDelayInSeconds" is only found after clicking into a HIT (view a HIT in this grooup). Is there no better way of seeing this info from the "ALL HITS" list or search results? Whimsy, always shown and i missed it. Your advice noted. Question: I think (might be wrong) that this date gets pushed back when their are hits rejected and republished back to the marketplace?
Munawar, thanks but it looks like that script is just for firefox? I use chrome only nowadays, is there something similar for chrome?
Not that I'm aware of. If a requester had thousands of HITs (let's say) and gave 24 hours to do each HIT, then for a few days people could just trade through accepting and returning HITs...pushing the expiration date back and back and back. If I go to the HIT ending soonest, accept it, return it...it will still expire at the same time.