Yes. You can open HIT Tracker by clicking the MTS extension icon and clicking the HIT Tracker button. You can either sync today or the last 45 days. There is not a way to import the HITDB data yet, that will be coming soon though.Just noticed in the MTS change log that indicators were added to show what work you interacted with for that requester / title.
Does anyone know if that means it will keep a DB of sorts for the last 45 days or more? I looked in the queue and am now seeing question marks so hopefully, that's where the records will be stored. If so, might there be a way to import the old HIT DB backup?
OK, thanks so much!Yes. You can open HIT Tracker by clicking the MTS extension icon and clicking the HIT Tracker button. You can either sync today or the last 45 days. There is not a way to import the HITDB data yet, that will be coming soon though.
Thank you, MTurk is making it harder to contact requesters, I'm hoping they didn't rebreak it all and I just missed this one.@Kadauchi
I right clicked a requester from my Logged HITs on HF, composed message and hit Send Message.
This is the error I rec'd:
I'm thrilled that you're incorporating this functionality. Can you kindly elaborate as to what we might see in the HIT Queue? Will it be a list of HITS submitted for the requester or simply a check mark if the HIT has been completed? I do see the submitted / assigned / approved numbers. Also, is the HITDB import functionality slated for the 1st of January along with the rest of Hit Tracker? I just ask so I can plan for the interim and am certainly not trying to pressurize. In fact, I'm amazed by how quickly MTS continues to evolve. Anyway, thanks again. MTS is keeping me afloat on the new platform!Yes. You can open HIT Tracker by clicking the MTS extension icon and clicking the HIT Tracker button. You can either sync today or the last 45 days. There is not a way to import the HITDB data yet, that will be coming soon though.
If you have MTS now, you can do a full 45 day sync (it shouldn't take to long, much faster than HITDB on Www used to do for me). I'm not sure which direction I'm taking, but probably just the overview as is (Showing what is assigned, submitted, returned, abandoned, paid, rejected) and letting users search under History if they want to see the full list. It should be ready Jan 1, the following Monday at the absolute latest. Hardest thing is converting HITDB format to HT.I'm thrilled that you're incorporating this functionality. Can you kindly elaborate as to what we might see in the HIT Queue? Will it be a list of HITS submitted for the requester or simply a check mark if the HIT has been completed? I do see the submitted / assigned / approved numbers. Also, is the HITDB import functionality slated for the 1st of January along with the rest of Hit Tracker? I just ask so I can plan for the interim and am certainly not trying to pressurize. In fact, I'm amazed by how quickly MTS continues to evolve. Anyway, thanks again. MTS is keeping me afloat on the new platform!
I've tested a few times and no issues on my end. You are on 2.0.8 right? MTurk broke 2.0.7's contact requester last night.@Kadauchi
I right clicked a requester from my Logged HITs on HF, composed message and hit Send Message.
This is the error I rec'd:
Ah .. let me update nowI've tested a few times and no issues on my end. You are on 2.0.8 right? MTurk broke 2.0.7's contact requester last night.
It has not. The buttons won't appear if HC is closed. If its not that its a bug and I'll dive into it.@Kadauchi If I click on a HIT in HF and it takes me to “ there are no more HITs available”, the panda buttons to add to HC are no longer there. Have they been removed?
Not to sound like a broken record, but I appreciate the diligence. FWIW, since you're in the process of working on it, it is useful to have the HIT titles (that have been completed for requesters) showing in the Queue. As I'm sure you know, requesters will change the name of a HIT slightly and not having the full list in the Queue would make it harder to catch potential re-takes. It just happened today that a requester adjusted the amount of time the HIT would take in the title. Just my two cents...If you have MTS now, you can do a full 45 day sync (it shouldn't take to long, much faster than HITDB on Www used to do for me). I'm not sure which direction I'm taking, but probably just the overview as is (Showing what is assigned, submitted, returned, abandoned, paid, rejected) and letting users search under History if they want to see the full list. It should be ready Jan 1, the following Monday at the absolute latest. Hardest thing is converting HITDB format to HT.
Just tried contacting a requester myself and received the errors:Thank you, MTurk is making it harder to contact requesters, I'm hoping they didn't rebreak it all and I just missed this one.
You should get redirected back to the HITs page after contacting.Just tried contacting a requester myself and received the errors:
No HITs match your criteria
Unfortunately, there are no HITs that match your search terms and/or applied filters. Consider modifying your criteria or browse all HITs available.
Strange... something is not right
The provided website address is not valid. Below are all HITs available.
Odd that MTURK would make it harder to contact requesters. I mean, we need to be able to communicate!
Requester is for your benefit only. This is what the requester receives when you send a message through MTS's right click.Also noticed that now it just states that the message is to "Requester" instead of their name...
The message did not send as far as I can tell. I was just directed to those errors. This is a requester with no TO history so I couldn't attempt to reach out that way.You should get redirected back to the HITs page after contacting.
If you want you can contact me https://worker.mturk.com/requesters/A2YNI49Y25JPBT/projects and I can tell you if it worked or not, but those errors are expected since this is how mturk is handling contacting requesters.The message did not send as far as I can tell. I was just directed to those errors. This is a requester with no TO history so I couldn't attempt to reach out that way.