Add a new input component that would be something between InputCheckboxes, InputSelect and InputText: It would show a fixed number of alternatives by default, you could request it to show more alternatives, and you could type in a text to filter down the results. Now implemented as InputField that replaces InputCheckboxes, InputSelect and InputText.
Decide if pre-fetching aggregations on the first load of the SearchContext makes sense. On the production machine pre-loading the aggregations is detrimental. The aggregations should be loaded only on demand (e.g. opening a menu).
Normalization of statistics: should they be normalized to the total number of results or to the sum of doc_counts for that specific aggregation? For now we can keep them normalized to the amount of results.
Filter chips not updated from search bar. Unable to produce on local machine, will need to check again on v1 deployment.
The search bar is not prominent or recognizable enough. I moved the search icon to the beginning (like e.g. in GMail search, and made the placeholder text always visible to make the search bar more recognizable. We could also try using some colour to highlight it more, but blue buttons are not consistent with the rest of the UI and blue outline is not compatible with the focused state.
Suggestion list ordering hardfixes
Less method-oriented column defaults.
Entry accordion details sizing, ellipsis for program version
Datasets defaults value: no datasets
raw_id, external_id: at the end, do not show if not present.
Timestamps in results table not correctly formatted.
Commas for large numbers, e.g. search results
Number of search results should always be shown, but avoid showing them twice
Cross instead of minus for removing statistics, toggle on name, menus into dropdowns, circled add/remove icons. There is now a GUI option that can be used to toggle between different variants for the icon, icon alignment and menu style.
Text input variant = standard, switching between variants. There is now a GUI option for switching between input variants and sizes.
Scaling defaults in filter registry, think of reasobale defaults
Disable exclude_from_search if no user interaction has been done.
Metainfo quantities should be searchable (metadata.quantities). Just in the search bar? Or additionally in IDs.
Disable statistics in visibility.
Filled icons, try smaller icons.
Option for whether aggregations are collapsed or not.
The "show more" button gets hidden during loading. Best option would be to disable the button during loading and maybe even showing a spinner, but this may be a bit hard since tracking the status of indidivual API calls is hard with the current API mechanism that tries to combine as many calls as possible.