eloyer
commented
7 months ago Makes sense to me — the existing list vis already adds columns conditionally based on the sorting that's applied to the lens, and once the refactoring in this pr has been merged, it will be even easier to add behavior like this (I think it could be done by default, without any additional UI, as long as there are some sizing checks, which are also already partially in place). I don't have the bandwidth to tackle this myself, but if you're interested in working on it I can give some pointers once we merge the pr above.
alexdryden
This is based on some feedback I received from a group on the UIUC campus who uses Scalar and was echoed by an author who is publishing a book using Scalar with the Illinois Open Publishing Network. I noticed some recent work on column display handling for lenses, so I thought this might be a ripe time to suggest this feature.
Issue:
When users build a lens with metadata facets for a list view, they would like the to see the metadata they are querying as a results column.
Example:
A user wants to see all pages that are within 50 miles of the center of Berlin that do not contain the word "Berlin" in the iptc:city field. They are interested in the query primarily to see which cities are represented, however, that data isn't returned and displayed in the list.
Roadblocks/Risks:
Managing how many columns are represented in the results
Implementation ideas:
There could be a checkbox as part of the configuration interface that would indicate if this field should be included in the results, something like this:
Alternatively, a more complete solution might add an additional drop down when the list is selected that allows users to select which columns to display for this lens: