-
Notifications
You must be signed in to change notification settings - Fork 28
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
Bug report - multiple filters don't work in Trends plots #338
Comments
I was just playing around with the filters yesterday and noticed that two filters does work if one is a date range and the other is metadata. So perhaps there is something preventing two filters of the same type (Report metadata)? |
This is interesting, and probably indicates a flaw in my filtering logic. I might have to rethink it. |
I ran into this as well, and although my situation might be a little different, I think the same issue is at play in both cases. In my case, I have Reports that have multiple metadata fields that I am interested in filtering against. So for example: I want to make a filter that only shows Report 1. The current filtering uses "AND" logic for filters within the same group, however each This is how I think the data are actually stored: The short-term, less-ideal solution that I can see is to make separate filter queries for each field and then apply an INTERSECT operator. The more-ideal solution might be to have all metadata fields in the same "row". There are probably better solutions, but this is what I have gathered so far. |
Describe the bug
When making a trends plot, applying two filters (e.g. Report_metadata_config_subtitle and Report_metadata_username) means no plot is generated (empty axes) even when the two filters work fine individually.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A new plot is made that only includes data uploaded by a specific user, filtered by assay (recorded in config subtitle in the jsons)
Actual behaviour
Empty axis appears (no datapoints)
The text was updated successfully, but these errors were encountered: