Read and Write data

[jwillenbring]

As an ECP SDK lead I want to have the ability to read and write information so that responses can be updated periodically without starting over, and can be archived and mined when submitted.

Parent	Children	Related	Blocks	Depends On

Acceptance Criteria:

A file containing information about the structure and content of questions and any existing responses can be read by the tool and displayed.

A file containing information about the structure and content of questions (this might be specific to the version of the questions) and all responses currently stored in the tool can be written out to a file.

Description, Additional Detail, Context:

One motivation for this is that I would like to be able to process an output file in such a way as to bring it to the next version of the community policies. For example, if the next revision modifies one policy to add another required component, deletes one policy, and adds another, we should be able to process existing responses with a script, and then the team could read in the resulting file with the new version of the policies such that their existing responses are pre-populated and they only need to address the one new policy and the one new component of the other policy.

We also want this so that we can look at responses across products and generate reports about compatibility. This would also require that we are able to look at certain versions of responses, so the database would need to have some concept of versioning. We would want only one response per product per version to be considered. We would like to be able to generate reports comparing policy compatibility one year ago to current policy compatibility. One way to do this might be to set up a different URL for responses each time info is gathered. There are other ways this could be done.

Implemented By Task(s):

• Task: <task url or ID>