Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need WorkerId in Mturk Event #2864

Closed
2 tasks
lakshmicode opened this issue Jun 5, 2023 · 2 comments
Closed
2 tasks

Need WorkerId in Mturk Event #2864

lakshmicode opened this issue Jun 5, 2023 · 2 comments
Labels
feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged.

Comments

@lakshmicode
Copy link

lakshmicode commented Jun 5, 2023

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

  • 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

@lakshmicode lakshmicode added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Jun 5, 2023
@github-actions
Copy link

github-actions bot commented Jun 5, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

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.

@mullermp
Copy link
Contributor

mullermp commented Jun 5, 2023

Were you able to resolve your issue? I see that you also opened a discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

No branches or pull requests

2 participants