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
Currently, we only have one data type that we support (how likely does the voter like or support a candidate). We need to not only map VAN's response to the current model, but also create new ones that support the different input types.
Priority should be given to the current existing data type, obviously.
The text was updated successfully, but these errors were encountered:
Ok so just to be super clear, we're talking about:
Pulling down NGP VAN's SurveyQuestions, which includes the list of eligible SurveyResponses for each question, being able to send them down to the mobile apps, and then record people's answers to those questions via NGP VAN's CanvasResponses?
My understanding is that these are not only two different endpoints, but two different data models. #129 pertains to the SurveyQuestions available to a walk list, or in general for the campaign, etc. #128, as I see it, depends in part to what Canvass Responses are tied to a Survey Question (as well as the list of canvass responses in general).
This is all to support the following scenario:
App user pulls down a walk list from FTB
FTB produces a path for every canvas location
FTB user knocks on doors, ask X Survey Question, records Y Canvas Response.
FTB user goes to other door on list, repeat previous step until list is traversed.
Currently, we only have one data type that we support (how likely does the voter like or support a candidate). We need to not only map VAN's response to the current model, but also create new ones that support the different input types.
Priority should be given to the current existing data type, obviously.
The text was updated successfully, but these errors were encountered: