LSST requirement DMS-PRTL-REQ-0047 states that the Portal Aspect (i.e., Firefly) should provide a "property sheet" interface to an individual row of data from a table.

Specification: The Portal aspect shall permit the inspection of all the data in a single row of a tabular data query result as a "property sheet" for that row, taking advantage of available metadata to supply units and other semantic information for each column value.

*Discussion: Resources permitting, the property sheet may be elaborated to provide additional functionality (typically, further queries) associated with particular data items displayed.
Property sheets should, where enabled by metadata, appropriately exhibit relationships between columns, such by displaying a value and its uncertainty together.
The system must provide a generic property sheet functionality for any table for which full metadata is available. It may also provide custom property sheets for commonly-queried tables such as Object, ForcedSource, Visit, etc. that provide a more scientifically useful layout, and additional available workflows, than possible just from the metadata.

(related, but this is not the subject of this ticket itself) With the related idea in DM-11154 in mind, I would like this facility to include the capability to execute the operation "show me all the information available for this object". That is, if the original tabular query was for a limited set of columns, and a property sheet for a row from this query result is requested, there should be a UI element that permits requesting the full set of available columns (i.e., a "SELECT *"). Some design work is required for how this would handle situations where the tabular query arose from a join or other more complex query.

Xiuqin Wu [X] may want to assign me a subtask to write a more detailed specification for this task.