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

Revise how downloaded questionnaire responses are treated. #33

Closed
mbastian93 opened this issue Sep 2, 2021 · 1 comment
Closed

Revise how downloaded questionnaire responses are treated. #33

mbastian93 opened this issue Sep 2, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@mbastian93
Copy link
Contributor

Currently, when executing the downloader script, all available questionnaire responses that were successfully downloaded and decrypted are deleted from the queue. For several reasons this is or might be problematic - or at least unwanted.
Admittedly, the 'delete' step in the downloader script could easily removed but that just leads to the problem, but in that way consecutive executions of the script lead to redundant downloads/decryptions.

From my point of view the following things should be implemented:

  • update the queue table and add columns that indicate, whether the respective response object has been downloaded and decrypted, as well as timestamp, when the last download occurred
  • update the download api to allow download of
    • entries that haven't been downloaded yet (basically, whats currently implemented)
    • all entries
    • downloaded and encrypted entries
    • (optional) entries identified by timestamp (referring to [last?] download) (maybe even range)

Consequently, the downloader script would need to be updated so that the usage of the api can be configured (e.g. with environment variables)

@mbastian93 mbastian93 added the enhancement New feature or request label Sep 2, 2021
@mbastian93
Copy link
Contributor Author

This issue will be closed as #57 at least replaced the download step. Some further work might be done to extend the api in order to allow parameterized queries for questionnaire response object in the queue, but that will be addressed once the details concerning the interface to the ORSC-standard have been worked out.

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

1 participant