(WIP) St dh port vioscreen #125
Conversation
…unately they don't appear to fit together as yet.
…e-api into st_dh_port_vioscreen
…t_dh_port_vioscreen # Conflicts: # microsetta_private_api/api/implementation.py
…lit generation of url from generation of html wrapping the link
…private-api into vioscreen
| int(vio_info["status"])) | ||
| t.commit() | ||
|
|
||
| # TODO: Any reason to respond with anything? |
There was a problem hiding this comment.
open question: should we extract the FFQ survey results now, or later?
|
|
||
| regcode = SERVER_CONFIG["vioscreen_regcode"] | ||
|
|
||
| # TODO: Specifying a callback url that goes back to our api server is, once |
There was a problem hiding this comment.
Can we just put microsetta-rest.ucsd.edu?
There was a problem hiding this comment.
This requires more thought. It's possible we could have the get return back to the rest api rather than the client, but it would then be up to the rest api to redirect back to the client. It's a slight change from what I had (Vioscreen redirects to client, which then sends a message to the api), but would probably be cleaner for developer implementing the api. Unfortunately, it requires us to hold state of how to redirect to the client on the api side, or alternately to encode a redirect url to the client inside of our encoding of a redirect to the api endpoint. It's probably possible, but something I'd prefer to design out more
…t_dh_port_vioscreen # Conflicts: # microsetta_private_api/example/client_impl.py # repo_test_scratch.py
… the minimalInterface. Users can now take additional surveys. No idea if vioscreen actually works because I can't get past their crypto without real credentials
| @@ -1250,7 +1251,14 @@ components: | |||
| description: Client url to which the customized consent form should be posted. | |||
| schema: | |||
| type: string | |||
| example: "http://www.microsetta.org/workflow_create_human_source" | |||
| example: "https://www.microsetta.org/workflow_create_human_source" | |||
There was a problem hiding this comment.
It's an example url string? 🤷♂️ All I did was make it https
…private-api into vioscreen
…private-api into vioscreen
Survey template id is not survey id Need account and source to write ag_login_surveys Need sample to associate a survey with a sample I needed location headers out of ApiRequests survey ids with no associated answers now appear in ag_login_surveys (these are the vio screen surveys), which complicates lookup of survey_template_id Modifying of vioscreen status changed from update to upsert (insert/update). This bypasses the need to track generation of vioscreen urls - we don’t add a row until a survey is completed. Fixed ancient potential bug in pkcs7 unpadding. Updated vioscreen code for python 3 vioscreen survey_ids now generated as secrets.token_hex(8)
…t_dh_port_vioscreen # Conflicts: # microsetta_private_api/api/implementation.py # microsetta_private_api/example/client.yaml # microsetta_private_api/example/client_impl.py # microsetta_private_api/repo/survey_template_repo.py # microsetta_private_api/templates/source.jinja2
…t_dh_port_vioscreen
…private-api into vioscreen
…sallow retaking a primary or COVID survey
Vioscreen
A work in progress for including vioscreen surveys. Needs testing with real credentials to see if urls generated can access the vioscreen surveys.