[New Feature]: Upgrades to Figaro UI

[sjlewis-jpl]

Checked for duplicates

No - I haven't checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

I'm frustrated when using the Bach UIs to analyze or assess testing results, and am limited by the interface and display options.

Describe the feature request

I need or want [...]

• Timestamp filters: allow all of them to select both the date and the time. Currently one can only select the date. This greatly limits the ability to do testing, as tests run on the same day get mixed together.
  • (adding times to the filters was already submitted in [Bug]: Figaro and Tosca datetime filters don't allow filtering by time #839)
  • What does timestamp capture? Is this the job start time, end time, something else?
  • New temporal filters that would be useful:
    • Job Start Time
    • Job End Time
    • Job Queue Time
• For DAAC Responses & Notifications: be able to filter / split out by product. Being able to zoom in on a particular product type would be very useful.
  • (just remembered that [New Feature]: Filter daac_response_tags by product in Figaro #840 already exists for the DAAC Responses)
  • At bare minimum, these should be separable by DAAC.
• Customizable table columns: being able to select, from a list, which columns to show on the table. The list should at least contain any field that can be filtered on with the preset filters on the left.
• Ability to export the tables to CSV format. Exporting all of the results would be very useful for analysis in Excel or Python. Also being able to export just the "current page" (of 100 results, say) could also be useful.
• For "Page Size": options for larger numbers, say up to 1000 (this would just be a "nice to have" if the export to Excel was implemented and fast).
• Button at the top to go directly to the Reporting UI. There's one to jump to Tosca. One to jump to the Reporting UI would be useful (this is a "nice-to-have").

Many of these might be achievable with the right elasticsearch query string, which is already available. However, constructing those isn't obvious, and would need good documentation for it to be useful to non-developers. If the information button next to this field (little blue circled "i") could redirect to a page specific to our PCM and Elasticsearch databases, that could go a long way towards many of these items.

And like for Tosca, I also suggest giving this UI a more meaningful name (and I know this might be inherited from HySDS and not changeable) - one that gives some clue as to why to use the UI, or what the UI does for a user. Happy to brainstorm on ideas if this is actually feasible.