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

[FEATURE]: storing survey input from players #114

Open
gumillie222 opened this issue Dec 4, 2024 · 3 comments
Open

[FEATURE]: storing survey input from players #114

gumillie222 opened this issue Dec 4, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@gumillie222
Copy link
Contributor

User Story

As a researcher, I want to be able to visually identify that the survey has been submitted and see the inputs.

Feature description

Survey is in the deliberation-empirica sub-module, where it contains the storage location for survey answers. Since players are mock objects in researcher portal, we want to figure out a way to store that. Perhaps we would also like display to that somehow to show that the survey is completed.

What would this feature enable?

Researchers are able to confirm that a survey has been completed and the inputs. In addition, they can use these stored inputs to generate further related questions.

Priority

None

@gumillie222 gumillie222 added the enhancement New feature or request label Dec 4, 2024
@shapeseas
Copy link
Collaborator

Two possible approaches:

  1. Users click/provide input on survey in render panel
  2. Detect the survey questions and then have those refs/dependencies panel

@gumillie222 - where is this data stored? check mock player and mock stage
@evanping - detect if references from survey can be parsed

@evanping
Copy link
Collaborator

evanping commented Feb 7, 2025

Right now the way we write and use references is that we can write a reference in the code editor and the portal will detect it and have it appear as an input in the dependencies panel. That is where the user can put custom inputs.

The possible workflow for this issue could be:
If the user wants to render an element in response to a survey answer, add a conditional reference to that element referencing the survey (i.e. survey.surveyName.question). This will let the user add inputs and conditionally render.

I will add an issue to add the ability to create conditional references via the gui.

@gumillie222
Copy link
Contributor Author

gumillie222 commented Feb 14, 2025

Image

This is a screenshot of the console when player submits the survey. It seems like the mock player object isn't connected to the survey submission, which means that the survey response will not be saved in mock player. "scoreSha" and "surveySha" might have something to do with where it's stored, but I'm not entire sure where the exact location is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants