Currently, the database contains only a selection of metrics, some of them make no sense (have no data for most countries) because parsing the data from WB format to the format used in our queries might take a lot of time.
What to do
Decide whether to include IDs or full names (perhaps an internal ID - entity pairing dictionary for 'safety'?) of countries and metrics, as it might make a significant difference when encoding pre-generated data into JSON files for later use.
Lists of supported countries and metrics should be reviewed again carefully, then:
newly selected metrics and countries should be parsed into a new master table
the query should use a new table
a small, test set of pre-generated quiz instances should be created (nth, if the approach with storing quiz data on e.g. S3 will be implemented)
Currently, the database contains only a selection of metrics, some of them make no sense (have no data for most countries) because parsing the data from WB format to the format used in our queries might take a lot of time.
What to do
Decide whether to include IDs or full names (perhaps an internal ID - entity pairing dictionary for 'safety'?) of countries and metrics, as it might make a significant difference when encoding pre-generated data into JSON files for later use.
Lists of supported countries and metrics should be reviewed again carefully, then: