When it comes to faceted search / filtering on the schema list pages (see left-hand side of wireframe), we have a few questions.
Can a user perform faceted search/filtering for any field?
The simplest approach would be to add an option for any field in the schema. The majority of schemas only have a small number of fields so this might be ok. However, there are also case where there are considerably more fields. For example, brownfield-land has 19. Having 19 options for the user to search / filter on would be too many.
Therefore, we might want to look into creating a way to override the default (filter option per field) with an alternative (we choose 5 important options).
How do we auto-generate the faceting options?
We will be generating many list pages, each with it's own set of faceting options. How should we decide on the type of facet? Types include ranges for dates and numerical values, radio buttons for small number of values, autocomplete for longer sets of values, freeform text, etc
One idea is to use the datatype of a field to determine which type to use.
Need to explore if that will work across the board.
AND or OR
Should the faceting be
- AND (this field is this AND that field is that)
- OR (this field is this OR that field is that)
What are the implications of choosing one approach over the other?
When it comes to faceted search / filtering on the schema list pages (see left-hand side of wireframe), we have a few questions.
Can a user perform faceted search/filtering for any field?
The simplest approach would be to add an option for any field in the schema. The majority of schemas only have a small number of fields so this might be ok. However, there are also case where there are considerably more fields. For example, brownfield-land has 19. Having 19 options for the user to search / filter on would be too many.
Therefore, we might want to look into creating a way to override the default (filter option per field) with an alternative (we choose 5 important options).
How do we auto-generate the faceting options?
We will be generating many list pages, each with it's own set of faceting options. How should we decide on the type of facet? Types include ranges for dates and numerical values, radio buttons for small number of values, autocomplete for longer sets of values, freeform text, etc
One idea is to use the datatype of a field to determine which type to use.
Need to explore if that will work across the board.
AND or OR
Should the faceting be
What are the implications of choosing one approach over the other?