search

SuffolkLITLab / docassemble-ALWeaver

A tool to help quickly generate draft interviews from an existing document (pdf or DOCX) for the docassemble platform.
https://apps-test.suffolklitlab.org/start/ALWeaver/assembly_line/#/1
MIT License
19 stars 6 forks source link

Add more flexibility to storing of variables with store_variables_snapshot #223

Closed plocket closed 2 years ago

plocket commented 3 years ago

store_variables_snapshot:

  1. It does seem like it would belong in the interview order, but I'd think data would be gathered in an umbrella interview if that were happening.
  2. Is there a piece of information that's more reliably required than address? It doesn't seem like it to me, but I know that the form I'm working wants to avoid collecting an address. Perhaps the referrer? This may be in its own issue eventually.

Originally posted by @plocket in https://github.com/SuffolkLITLab/docassemble-assemblylinewizard/issues/153#issuecomment-774731126

plocket commented 3 years ago

From @BryceStevenWilley (in PR comment):

I think I missed this convo when it happened: https://github.com/SuffolkLITLab/docassemble-assemblylinewizard/issues/153#issuecomment-774731126. IMO we would want this to not be in the umbrella interview, especially if we want to see how many people are using a specific form. For example, if we made an optional indigency form that was used in several other forms, X and Y, we'd want to know how many people actually used the indigency form, not just how many filled out X and Y, right?

nonprofittechy commented 3 years ago

I think we need to coordinate with the view stats package and figure out how to capture both universal and specific interview stats at different keys in the database.

Because without any prefix the stats are saved by the most top level interview file, I think we probably want this in the main code block.

We would need a different design to save stats that reflected which extra sub interviews were included in the parent interview

nonprofittechy commented 3 years ago

I think the way for us to think about this is more flexibility. Making it easier, perhaps with a YAML list of field names, for the author to specify what variables get stored in the snapshot.

We also want to think of two classes of information:

  1. Anonymous statistics and analytics
  2. Detailed structured data that might get warehoused for a court to make use of later or sent directly as metadata with the form.
nonprofittechy commented 2 years ago

Closing this one--#255 better captures what we want, as does https://github.com/SuffolkLITLab/docassemble-InterviewStats/issues/13