We need to identify how the outputs of the extractor app will be demo'd.
It seems that extractor v1 is focused on creating a summary report (and accompanying APIs) for a single place and indicator definition.
A big expectation from the user group is to be able to contextualize their place of interest with identical analysis of other places.
We can build out some custom reporting for this but connecting with an existing frontend would emphasize the modular design (ie: "separation of duties") behind this which help make the extract-app maximally reusable.
In this issue @7yl4r will explore potential user-facing views of the extract-app outputs.
We need to identify how the outputs of the extractor app will be demo'd. It seems that extractor v1 is focused on creating a summary report (and accompanying APIs) for a single place and indicator definition. A big expectation from the user group is to be able to contextualize their place of interest with identical analysis of other places. We can build out some custom reporting for this but connecting with an existing frontend would emphasize the modular design (ie: "separation of duties") behind this which help make the extract-app maximally reusable.
In this issue @7yl4r will explore potential user-facing views of the extract-app outputs.
Some ideas: