-
Notifications
You must be signed in to change notification settings - Fork 36
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
Turnkey epidemic system #21
Comments
One possible approach: Variables & secrets in .env file Inputs: Outputs (and how to create them): Not present yet but may need: |
It'd be useful to know what the common fields and what the specific extension points are for various diseases, so we can understand what the "day zero" platform looks like and how we would configure/extend it to the specific needs of any outbreak. Also just foregrounding a couple of implications in this proposal which may well be valid but probably deserve explicit consideration:
|
This sounds great. Find attached day_zero schema for review (@outbreakprepared @ksewalk ) : M |
@Mougk I think this schema is great. The only thing it does not include is the country and status drop down options. |
@Mougk Schema looks good. My only additional thought is whether we want to add a tab for a summary table. |
@Mougk is this schema the latest version? Can you add indications of which fields are required/optional (in the Covid-19 line list confirmation date and location are required)? |
Not quite, let's discuss during next standup. |
@Mougk @aimeehan1 @iamleeg Here is the updated day zero schema based on our most recent conversations. |
|
Broke this out into a number of issues. |
As a programmer supporting research I would like to push a button that creates a new system (infrastructure, services, etc.) to accommodate any new epidemics. Similar to our turnkey partner infrastructure, we could specify some values in a configuration file (like S3 bucket name, Google document ID) and run a script that would create and run an (minimum viable) application stack that satisfies some set of curator, researcher, and software requirements.
This would include, but not be limited to:
The text was updated successfully, but these errors were encountered: