Multi page surveys

[markwhiting]

Set up to manage multiple pages, e.g., RME, using something like a page column.

[markwhiting]

• How do we tell the system about pages? Whats on a new page, whats the order, can you go back?
• Do you store incrementally at each page? if so, how? (i.e., one row in DB per page, or a local object thats dumped in DB when no more pages come in)
• Does the back end give all pages at once, or one page at a time?

[markwhiting]

@karansampath can you try to solve this next?

[markwhiting]

How's this going?

[karansampath]

Was focused on task mapping for the past week so haven't done much on this yet. I should have a good idea of how to go about this by tomorrow's meeting.

[markwhiting]

OK. Thats fine, task mapping is more time critical for now.

[karansampath]

• User disconnects/closes, we should only save the final survey
• Add disclaimer saying that 'You cannot come back to this page' at the end of every page
• Add .page column to allow for alphanumeric ordering of pages
• Allow for randomization of letters/numbers in .page
• Modify RME survey to be multi-page and check which of the other surveys are designed to be single page only

[markwhiting]

Check in. When do you think this can be completed?

[karansampath]

Sorry, was under the weather with COVID-like symptoms. Surveys have been modified, and am working on modifying VSCode now. Will ensure it is done by tomorrow.

[karansampath]

Having been working on this in #40

[markwhiting]

Just checking in, is this basically done?

[sumants-dev]

@karansampath if you need help and blocked, we can set up a time to go through it next week