Advanced Search>Adding Rules

[PriyaDoIT]

When adding a rule to a data set one must choose if something is equal or not equal to some filter value. However, in some cases, it is not obvious to the user what the filter value could be, leading the user to no results.

For example: As a user, I want to filter only on food establishements that did NOT pass a food inspection. So here are the steps that I'd take:
Dataset = Food Inspection
Add Rule
1st drop down: select results
2nd drop down: equal to
Enter Filter Value --- here is where the user could potentially get stuck with no results. I entered "Fail," "Failed," "Not Passed," and no results. I still am not certain what to enter.

I then changed the query to not equal to Pass and I ended up with food establishments that passed their inspection.

This is just one example, but could apply to other queries as well. In some cases, would it be possible to make the filter value a drop down of all possible results?

[PriyaDoIT]

Although this feature is available in WG, it was determined in weekly meeting that it would be difficult to implement with Plenar.io and would lead to performance issues.

[smarziano]

I just wanted to add that based on experiences from the CUTGroup test, this would be an important enhancement. There needs to be more guidance for users to know how to use the filters and what their options are. Currently, OpenGrid advanced search requires some knowledge of the dataset to use it fully.