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

Feature Request: Smart Drift Object Compilation with Filtered Datasets for Enhanced Visualization Clarity #51

Open
ghost opened this issue Dec 13, 2023 · 1 comment

Comments

@ghost
Copy link

ghost commented Dec 13, 2023

Description of Problem:
In the current implementation of the Smart Drift reports, all data points are visualized without any filtering options. This leads to cluttered and sometimes overwhelming visualizations, making it difficult for users to quickly identify and analyze the most relevant data trends and outliers.

Overview of the Solution:
Introduce a feature that allows users to compile Smart Drift objects with options to filter datasets based on user-defined criteria. This would enable the generation of reports that focus on the most pertinent data, providing cleaner and more insightful visualizations.

Examples:

  1. There should be an option to filter data by categories or values that the user considers critical for their analysis.
  2. If we want to filter a country dataset we can pick a column to filter by e.g. "name" and pick our desired countries such as "France" and "Germany"

Blockers:
There may be technical challenges in implementing dynamic filtering that interacts seamlessly with the existing Smart Drift compilation process. We want to make sure that this addition does not make the compilation unnecessarily longer and more cluttered in our code.

Definition of Done:

  1. Apply filters to the dataset before compiling the Smart Drift object.
  2. Generate visualizations in the Smart Drift report that only include the filtered data.
@ThomasBouche
Copy link
Collaborator

Hi,
Thank you for your issue, and your interest for Eurybia !

I understand the need to filter on a sub-sample of the dataset.
But the proposed solution has some disadvantages compared to a user who filters his dataset by himself before putting his datasets in eurybia.

Compared to the solution, it is suitable for simple filters, but sometimes the filters are more complex. The user has the power to manage more complex filters by himself.

If we add these filter parameters, we're adding complexity to Eurybia. This means adding functions to check that filters are applicable, providing messages in the event of errors and adding unit tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant