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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split app data per region and load on demand #743

Open
ivan-aksamentov opened this issue Jun 15, 2020 · 0 comments
Open

Split app data per region and load on demand #743

ivan-aksamentov opened this issue Jun 15, 2020 · 0 comments
Labels
help wanted Extra attention is needed IMPORTANT Take this immediately! s:data Scope: related to data retrieval, parsing, transformation, storage, update s:ui Scope: related to user experience, user interface, usability, accessibility t:feat Type: request of a new feature, functionality, enchancement

Comments

@ivan-aksamentov
Copy link
Member

ivan-aksamentov commented Jun 15, 2020

馃檵 Feature Request

馃敠 Context

Currently the data for all countries is being statically bundled and loaded on startup
https://github.com/neherlab/covid19_scenarios/tree/master/src/assets/data

This is redundant as users most likely are interested in one region or maybe a handful. This also makes the app startup slow, as the JSON are loaded along with the rest of the JS bundle and are then validated.

馃槸 Describe the feature

We want to split the data into chunks per region.

Decisions tomake:

  • What loading mechanism to use, e.g. webpack's dynamic import (import(chunk) => Promise<> ), plain HTTP requests from a public S3 bucket (Don't bunde the data聽#744)
  • Whether to merge all 4 pieces (cases, population, severity and scenario) into one file for that particular region, similar to how Shareable schema works for scenario uploads and URL sharing, or to keep 4 pieces separate (the consideration is that currently in the UI the case counts and age distribution can be changed independently from scenario params)
  • How to not break schemas too much and to maximize backwards compatibility across different I/O types

馃捇 Examples

馃拋 Possible Solution

Related

@ivan-aksamentov ivan-aksamentov added t:feat Type: request of a new feature, functionality, enchancement help wanted Extra attention is needed needs triage Review this and assign labels IMPORTANT Take this immediately! s:data Scope: related to data retrieval, parsing, transformation, storage, update s:ui Scope: related to user experience, user interface, usability, accessibility and removed needs triage Review this and assign labels labels Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed IMPORTANT Take this immediately! s:data Scope: related to data retrieval, parsing, transformation, storage, update s:ui Scope: related to user experience, user interface, usability, accessibility t:feat Type: request of a new feature, functionality, enchancement
Projects
None yet
Development

No branches or pull requests

1 participant