rfrenchseti
commented
2 years ago Phases of implementation: 1) Allow sub-categories in checkbox fields. Allow multiple levels of sub-category, like "Other/Asteroid/A-C/A/Asteroid AAA111". 2) Allow checkbox fields to be hidden. There is already a mult field for this, but I'm not sure it's paid attention to when displaying the widget. 3) Support arbitrary list of aliases for mult values. 3) Add API support for string searching on checkbox fields. This will require a new type of search term in the URL. 4) Add API support string completion on checkbox fields. 5) Add UI support for adding a string-search version of the widget for checkbox fields in addition to the normal widget.
The "widgets" that allow searching can be expanded to more than just check boxes and range searches. Each data field could actually have multiple ways of search on it (for example, both range and check boxes for Cassini rev_no). In addition:
From Mark:
When we get around to dealing with asteroid and comet targets, which we are sort of committed to dealing with as part of our PDART program, we will have to handle target names in multiple ways too--we can't have a checkbox for every asteroid, but we also don't want to get rid of the checkboxes for planets and moons, so the UI will have to provide both options.
This was actually part of the thinking behind OPUS2--that there could be a variety of UI widgets inside any of those constraint boxes.
[Old content, see #354, #581] For example, I would love to see options to select ranges for things like incidence, emission, phase, latitude and longitude using sliders. Wouldn't it be cool if you could see a map of Enceladus and then draw a box around the region you want to search for?]