You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Mturk Event has EventType, EventTimestamp, HITId, AssignmentId and HITTypeId.
Since the AssignmentId is reused multiple times for when workers returning/abandoning assignments, We could not determine which event belongs to which worker and events forwarded to SQS message are not always in same created order.
So we need WorkerId data inside Mturk event data.
Use Case
Since the AssignmentId is reused multiple times for when workers returning/abandoning assignments, We could not determine which event belongs to which worker and events forwarded to SQS message are not in same created order always.
Sometimes we are facing issues with assignments worker doing the survey which has re-assigned AssignmentId.
Proposed Solution
We need WorkerId data inside Mturk event data to handle the events effectively.
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
SDK version used
3
Environment details (OS name and version, etc.)
Ubuntu 20.04
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the feature
The current Mturk Event has EventType, EventTimestamp, HITId, AssignmentId and HITTypeId.
Since the AssignmentId is reused multiple times for when workers returning/abandoning assignments, We could not determine which event belongs to which worker and events forwarded to SQS message are not always in same created order.
So we need WorkerId data inside Mturk event data.
Use Case
Since the AssignmentId is reused multiple times for when workers returning/abandoning assignments, We could not determine which event belongs to which worker and events forwarded to SQS message are not in same created order always.
Sometimes we are facing issues with assignments worker doing the survey which has re-assigned AssignmentId.
Proposed Solution
We need WorkerId data inside Mturk event data to handle the events effectively.
Other Information
No response
Acknowledgements
SDK version used
3
Environment details (OS name and version, etc.)
Ubuntu 20.04
The text was updated successfully, but these errors were encountered: