One liner
Let's use our MDIM infrastructure to power explorers.
Context
Explorers are a nice product that our users like. However, their backend is a bit hacky. We released MDIMs last year, trying to create a space for multi-dimensional indicators. From a technical point of view, we reckon that MDIMs and Explorers are very similar: They both are collections of charts.
Therefore, to mitigate the code maintenance burden and enable explorers to benefit from the features MDIMs brought, we will migrate explorers into MDIMs. This migration will be finalized only once we are sure that MDIMs and Explorers reach feature parity (i.e., features that Explorers have but MDIMs lack). This analysis is ongoing.
Pre-requisite: Explorers in ETL
A prerequisite for migrating explorers to MDIMs is that we first have all explorers in ETL, using export://explorers steps. Currently, different explorers might use different backends (CSV-, Grapher-, ETL, etc.). We track progress on this task in:
The task
The translation of explorers to MDIMs should be done incrementally, without affecting end users. This means we should ensure the public explorer URLs continue to work during and after the translation process.
- Start migrating the least popular explorers
- Create a PR per explorer to make it easier for Q&A. Could do more exceptionally.
- Make sure that redirects are in place.
One liner
Let's use our MDIM infrastructure to power explorers.
Context
Explorers are a nice product that our users like. However, their backend is a bit hacky. We released MDIMs last year, trying to create a space for multi-dimensional indicators. From a technical point of view, we reckon that MDIMs and Explorers are very similar: They both are collections of charts.
Therefore, to mitigate the code maintenance burden and enable explorers to benefit from the features MDIMs brought, we will migrate explorers into MDIMs. This migration will be finalized only once we are sure that MDIMs and Explorers reach feature parity (i.e., features that Explorers have but MDIMs lack). This analysis is ongoing.
Pre-requisite: Explorers in ETL
A prerequisite for migrating explorers to MDIMs is that we first have all explorers in ETL, using
export://explorerssteps. Currently, different explorers might use different backends (CSV-, Grapher-, ETL, etc.). We track progress on this task in:The task
The translation of explorers to MDIMs should be done incrementally, without affecting end users. This means we should ensure the public explorer URLs continue to work during and after the translation process.