Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-14361

Filtering should be available in all tabular data viewers

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Firefly
    • Labels:
    • Team:
      Science User Interface

      Description

      In playing with the very nice (thank you!) FITS-file-extension browser and looking at some recent LSST data files, I ran across a couple of places where the following feature would be very useful:

      Whenever we are displaying a tabular view of something that may scroll vertically, it would be good to be able to filter the rows by the contents of the columns.

      The places this came up today were:

      • The right-hand pane of the FITS file browser, in which header contents are displayed - since FITS files often have hundreds or even thousands of headers.
      • The column/filter properties dialog in the table viewer - LSST has many tables with hundreds of rows (and WISE has some very wide tables, too). In this latter case, once UCDs are available in the column metadata, it will become very useful to filter on them (enabling, e.g., "show me all the positional columns", "show me all the flux columns").

      Other obvious places in the system where this would be helpful include:

      • The normal FITS header browser available from the image toolbar "info" button.
      • The HiPS properties viewer.

      The UI element to allow this should be the same head-of-column filter field that we use in our main table viewer.

      If/when we add full-text search/filtering to meet NED's request, it would be appropriate to make this available more or less everywhere, too.

        Attachments

          Issue Links

            Activity

            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            This has been implemented, over the past three years, in almost all of the places in the Firefly UI where filtering on tables is at all relevant or useful.

            There is a current ticket in the IPAC Jira system, https://jira.ipac.caltech.edu/browse/FIREFLY-920 , that we are using to evaluate changing the global default for tables to "filtering enabled", with explicit overrides needed for any new cases where the filter might be inappropriate (they are rare, at best).

            However, all the use cases mentioned in the present DM ticket have already been addressed, including the FITS header table, the column selection dialog in the TAP search screen, and so on, so this ticket can be marked "done".

            Show
            gpdf Gregory Dubois-Felsmann added a comment - This has been implemented, over the past three years, in almost all of the places in the Firefly UI where filtering on tables is at all relevant or useful. There is a current ticket in the IPAC Jira system, https://jira.ipac.caltech.edu/browse/FIREFLY-920 , that we are using to evaluate changing the global default for tables to "filtering enabled", with explicit overrides needed for any new cases where the filter might be inappropriate (they are rare, at best). However, all the use cases mentioned in the present DM ticket have already been addressed, including the FITS header table, the column selection dialog in the TAP search screen, and so on, so this ticket can be marked "done".

              People

              Assignee:
              xiuqin Xiuqin Wu [X] (Inactive)
              Reporter:
              gpdf Gregory Dubois-Felsmann
              Watchers:
              David Shupe, Gregory Dubois-Felsmann, Trey Roby, Xiuqin Wu [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.