-
Notifications
You must be signed in to change notification settings - Fork 25
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
Researcher version of validation page - validate users #1550
Comments
I this this should be fairly doable! From the backend, we'll probably have to tweak how labels are retrieve (easy) and think about what it means to send out missions (harder). If we choose not to send missions (since I'm not sure what a "mission" means in this context), there might need to be a few front-end modifications as well (i.e., getting rid of the mission container & code that updates any mission progress). I don't think the front-end modifications should be too drastic (hopefully) - although I could be wrong! |
I think there should still be missions! Maybe the missions aren't necessarily of one label type or of exactly 10 labels, but I don't see any reason to not use missions. |
We have two new use cases for this feature! First, we have high school volunteers who use Project Sidewalk as part of their required community service hours for graduation, NHS, etc. We usually have a back and forth as they learn to use the tool; I give them feedback after every hour or two of work. This could make that process easier! The second use case is for use in the classroom. We just used Project Sidewalk in a class at UIC, and one issue we ran into is that TAs are typically responsible for specific students. We trained the TAs in using the Validate interface, but it serves up labels from random users. This feature would be perfect for this situation! |
We can now accomplish this through #3510 |
It would be useful to allow the validation page to show labels from only one user (only accessible by researchers). This would make it easier to verify that turkers are auditing in good faith (while simultaneously adding validation data!!).
@aileenzeng how hard do you think this would be to do? I would want to use the current validation interface, just make it so that the back-end only serves up labels from a specified user. Possibly labels of all label types mixed together.
The text was updated successfully, but these errors were encountered: