Open marcelgerber opened 2 weeks ago
Currently, in indicator-based explorers, we can only reference indicators using their ID.
However, that ID is not meaningful in any way, and moreover, it is not stable between different (staging) servers.
We should enable referencing indicators by ETL path.
We want to have this feature usable by Jul 11, for the update of the world population explorer.
We talked quickly about this in a dev meeting, and we prefer doing this at bake time.
Core problem
Currently, in indicator-based explorers, we can only reference indicators using their ID.
However, that ID is not meaningful in any way, and moreover, it is not stable between different (staging) servers.
Proposed solution
We should enable referencing indicators by ETL path.
Context
We want to have this feature usable by Jul 11, for the update of the world population explorer.
Where should the resolution "ETL path -> indicator ID" happen?
We talked quickly about this in a dev meeting, and we prefer doing this at bake time.