-
Notifications
You must be signed in to change notification settings - Fork 0
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
Forced/Required Response Feature #56
Comments
Required is already implemented for all questions by default as a server level setting. What I think would be useful here is something like an optional column in CSVs called |
I think we would need to reconcile this with the overall |
Can you summarize your policy?
I’d just assume required is on by default for everything and then some things are optional if there’s a column that expresses that.
… On Dec 13, 2021, at 03:39, Karan Sampath ***@***.***> wrote:
I think we would need to reconcile this with the overall required check that we already have in place. i.e. Do we want both overall and individual required variables? If not, how would we indicate survey-wide required characteristics (is it useful to have any disclaimer if no questions are required?). I've modified the code to include my interpretation of this, but let me know if it needs changes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes exactly, so each question is required unless specified (will take on that value in that case (i.e. either true or false)). |
(This is a feature that we may not require at the moment as we run our own surveys. But we may need it once we start running other people's surveys) But:
The text was updated successfully, but these errors were encountered: