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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataset-specifc Period codelists lead to catastrophic UI/X #76

Open
Robsteranium opened this issue May 4, 2021 · 0 comments
Open

Dataset-specifc Period codelists lead to catastrophic UI/X #76

Robsteranium opened this issue May 4, 2021 · 0 comments
Labels
data Related to some underlying/upstream data issue enhancement New feature or request etl Related to the etl/pipelines

Comments

@Robsteranium
Copy link
Contributor

Robsteranium commented May 4, 2021

image (3)

This would be resolved by using a single intervals codelist.

This could be arranged with grouping by interval containment:

  • 2021
    • 2021Q1
      • 2021-01
      • 2021-02
      • ...
    • 2021Q2
    • ...
  • 2022

Or with grouping by interval length:

  • Years
    • 2021
    • 2022
    • ...
  • Quarters
    • 2020Q4
    • 2021Q1
    • 2021Q2
    • ...
  • Months
    • 2020-12
    • 2021-01
    • 2021-02
    • ...

If we can't get the data in this form, we could always add a post-processing step that modified the data (either within ES or before ingestion).

@Robsteranium Robsteranium added data Related to some underlying/upstream data issue enhancement New feature or request etl Related to the etl/pipelines labels May 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Related to some underlying/upstream data issue enhancement New feature or request etl Related to the etl/pipelines
Projects
None yet
Development

No branches or pull requests

1 participant