Ticket #200 (closed task: fixed)

Opened 2 months ago

Last modified 1 month ago

Browse table in opus data

Reported by: pwaddell Owned by: aaronr
Priority: normal Milestone: AZ-SMART Phase 1
Component: AZ-SMART Version:
Keywords: Cc:

Description

In the opus data tree, the context menu now contains two export options. We should add a Browse Table option for nodes that contain export table entries. The browse table option should open a table browser widget in a tabbed window on the right hand side of the GUI, allowing quick viewing of the contents of any table in opus data.

Change History

Changed 1 month ago by travis

If it helps at all, there a table view widget in opus_gui.results.forms.view_table_form

it basically takes in a storage location for an opus storage object and loads the data into the table. you'd have to change the top of the load_table method (as the visualization object is specific to the results manager, and find a different way to obtain the table's primary keys (if you want to order the columns in a particular way).

Changed 1 month ago by aaronr

  • status changed from new to closed
  • resolution set to fixed

This ticket has been worked on by myself as well as Alan to get the Dataset class working for arbitrary dataset viewing. With this last set of changes table viewing and viewing of table summaries are working:

R3512 - Fixing the problem where right click actions related to scripts were not showing up in the opus data section. The problem was two fold. First the nesting of scripts was made one deeper in earlier XML changes and that confused the logic for linking the datasets to scripts. Second, the classification field was made to have the attribute of hidden which made it invisible to the logic that was relying on the GUI model-view index for the location of that element. That element is now found within the DOM tree.

R3513-R3514 - Two fixes for data display in table view. First is to properly display the int, float, string variables by first checking their numpy type and converting to basic python types before passing to qvariant. Next is to add a right alignment on our table view by hooking into the Qt.TextAlignmentRole? in the data() method of our abstract table class.

R3515 - Catching datasets that are empty, single rows, single columns, or have special types in them. Trying to make the data set viewing more robust in the table view.

Marking this ticket as closed as table view of datasets via right click menu from the opus data section of the GUI is now supported.

Note: See TracTickets for help on using tickets.