Assuming we put surveys on Turk, we can have precision access management with qualifications. For example we can let any worker see a panel intro HIT, and then qualify them so next time they look they see the survey HIT we need them to complete.
My understanding is that qualifications can be somewhat automatically administered, so its even possible that we can define a funnel of qualifications and surveys so that in a worker completes a survey they automatically can see the next survey we want them to work on.
This general approach means we can invest a lot less in deciding who should do what, and just rely on some kind of rule based system to provision access. This has a challenge that that system may be a little hard to understand and we might want to be careful in its design, so as not to accidentally allow every worker to do all our surveys over time (because that will cost a lot).
@rivera-lanasm — if you are looking at the turk API docs and features it might be useful to try to work out if there are any limitations on these conditional qualification things. Of course if we didn't have conditional qualifications, we could still do a manual update on cron, but if we can make it happen without intervention, it provides a great way for us to deal with other slack in the worker experience (specifically, if we recruit someone to do something but we don't have room for them yet, they could perhaps do a few surveys until we do have room for them.)
Assuming we put surveys on Turk, we can have precision access management with qualifications. For example we can let any worker see a panel intro HIT, and then qualify them so next time they look they see the survey HIT we need them to complete.
My understanding is that qualifications can be somewhat automatically administered, so its even possible that we can define a funnel of qualifications and surveys so that in a worker completes a survey they automatically can see the next survey we want them to work on.
This general approach means we can invest a lot less in deciding who should do what, and just rely on some kind of rule based system to provision access. This has a challenge that that system may be a little hard to understand and we might want to be careful in its design, so as not to accidentally allow every worker to do all our surveys over time (because that will cost a lot).
@rivera-lanasm — if you are looking at the turk API docs and features it might be useful to try to work out if there are any limitations on these conditional qualification things. Of course if we didn't have conditional qualifications, we could still do a manual update on cron, but if we can make it happen without intervention, it provides a great way for us to deal with other slack in the worker experience (specifically, if we recruit someone to do something but we don't have room for them yet, they could perhaps do a few surveys until we do have room for them.)