New Script: TurkerViewJS Description: [h2]TurkerViewJS[/h2] Allows users to get live data from TurkerView.com for both Requesters & individual HITs. [h3]HIT API[/h3] Accessible from the HITs page & for HITs inside a worker's queue this allows registered TurkerView users a chance to get even more accurate data on the specific HIT they're viewing/working on. turkerview worker mturk script To review/install the full script check out TurkerView!
TurkerViewJS Description: TurkerViewJS allows users to get live data from TurkerView.com for both Requesters & individual HITs. [h3]HIT API[/h3] Accessible from the HITs page & for HITs inside a worker's queue this allows registered TurkerView users a chance to get even more accurate data on the specific HIT they're viewing/working on. CHANGELOG for v3.0.0: Added the ability to export HITs directly to TurkerHub from the worker.mturk HITs page and queue. To review/install the full script check out TurkerView!
TurkerViewJS Updated CHANGELOG for v3.0.1: Cleaned up some triggers, indicated a successful export, fixed a bug w/ titles not transferring to TV correctly. Said a little prayer for Status Detail pages on worker. To review/install the full script check out TurkerView!
TurkerViewJS Updated CHANGELOG for v3.0.2: Incorporated @, function parameter building (probably incorrectly) as a new learning experience, will clean it up when I do full sit-down for this when we get a clearer view of www lifecycle. Cleaned up some tiny things, organized my to do for when www dies so I can fully clean this script up. Added more prominant warnings for rejections/blocks To review/install the full script check out TurkerView!
TurkerViewJS Updated CHANGELOG for v3.0.3: Fixed a bug preventing the script from working properly on www. Thanks @DikDik To review/install the full script check out TurkerView!
TurkerViewJS Updated CHANGELOG for v4.0.0: Major overhaul for worker.mturk transition. Will now track completion times WITHOUT the use of third party scripts, attaches a TurkerView Dashboard to mTurk itself so you don't have to leave your workflow as often to leave reviews, as well as some various bug fixes. To review/install the full script check out TurkerView!
TurkerViewJS Updated to v5.0.0 CHANGELOG for v5.0.0: Added review qualifications, a short participation agreement, GID tracking for more accurate review exports, and minor bugfixes. To review/install the full script check out TurkerView!
TurkerViewJS Updated to v6.0.0 CHANGELOG for v6.0.0: Introduced more server-side validation of data. You'll need to upgrade to 6.0.0 in order to leave reviews now, unfortunately this wont be obvious when attempting to leave reviews from the outdated version so please pass along the word. Rating communication now requires a comment, as does rating pay & hourly too far apart. To review/install the full script check out TurkerView!
TurkerViewJS Updated to v6.3.0 CHANGELOG for v6.3.0: Added proper handling for changes in qual/screener/demographic review guidelines. Added a 'hide reviewed' button to make the dashboard for reviews cleaner. To review/install the full script check out TurkerView!
TurkerViewJS Updated to v6.5.0 CHANGELOG for v6.5.0: Added an hourly wage tracker to the top bar on MTurk. You can use this to pause the hourly tracking for TVJS to step away while taking breaks from HITs. It uses moments (datetime) to do the tracking so will be unaffected by background tab throttling/similar issues. To review/install the full script check out TurkerView!
TurkerViewJS Updated to v9.0.0 CHANGELOG for v9.0.0: You can now review HITs from up to 3 days ago. Custom warning levels for all different types of return reviews. Multiple changes to the return review system & preparation for future overhauls. To review/install the full script check out TurkerView!
Why do we have to write 40 characters minimum to return a hit for broken content/not loading? 40 characters is too much to be typing in regularly when typing, "Broken or Doesn't load." suffices. This will just cause users to not report broken content.
We'd prefer higher quality comments than just saying something is "broken" - there are a lot of times when a user is simply wrong (reporting as broken for no-code, for instance) so its important to get more context about what is broken in the HIT. The 40 character threshold might be too high but that can be adjusted
I feel the 40 characters limit is high as well. I was going to comment "12 pages of reading and questions" on a $0.30 HIT, but the character limit detered me from that and I just returned it without doing the review.
