Specifying 25 results in 25 groups being displayed but 10 is still selected in the control. Specifying "All" doesn't render anything.

Suggest pushing the cutoff argument to the Show first N groups control's values array if the argument isn't one of 10/25/"All" and setting the control's checked radio button to cutoff. An argument of All should map to the number of groups in the data.

Discuss details with JW

chart's got way too much horizontal space

Test notes

• Filters are grouped together and appear to the left of the chart.
• Other controls are grouped together and appear to the right of the chart.

and default to query aging category

Test notes

• A new dropdown appears that allows the user to update the bar grouping.
• Defaults to Query Age Category.

Default to Visit/Folder. Related to #72 .

Consider whether we can convert the raw json (from d3.csv()) to a nested structure to save space and improve processing speed. Something like:

Remove Form: Field from listing columns.

Could we include an option to see all variables on each datastream (Visually the same thing as when the graphic is grouped by form, with each variable having a stacked bar of all four query types & the overall count)?

Add button to reset chart to default

Make the y-axis labels look like links (blue+underline) when they are clickable.

When the chart is re-renderering

Suggestion from Heather K:

"This looks great. I think the only other thing I’d like to be able to compare sites somehow. For example, compare forms by site to see if one site has more than others within a specific form which could highlight systematic differences within a site."

Right now you can select one or multiple types of query status via the clickable legend, but to see the data listing you can only select one query status at a time (by clicking one bar). The same situation applies to other filters like only being able to select one form at a time.

DMEDS would like to have the ability to see one or multiple types of query status in the data listing. i.e. they would like to be able to see any combination of closed, cancelled, open, and answered queries in the data listing you get when you click the bar(s) in the chart. They would also like to see any combination of filters in the data listing. For instance, selecting "Group by" equal to "Form" and then being able to click on the bars for any combination of forms in order to have them display in the data listing below.

Test notes

• Verify that all data filters are now multi-select.
• Verify that multiple bars in the chart can be highlighted.

Default to Query Open By: Marking Group. Related to #72 .

In the current pending version of webcharts, I'm not seeing anything loaded when I render the chart in CAT. I see the same behavior in all browsers.

Current instance is missing the CSV export feature from Webcharts

Test notes

• Verify that the listing export button displays by default.

Create a self-contained example page like Spencer did for Paneled Outlier Explorer here: https://rhoinc.github.io/paneled-outlier-explorer/build/test-page/

Pull the data from viz-library so that it isn't stored in two places

from @agstn

Add the following:

• include Site in "Group by" control
• include Site and Marking Group as standard filters.

In certain situations the chart indicates that there are "X More" items that could be displayed on the y-axis even though the setting is set to show all.

An example exists in RhoMAP Test for ITN058AI where "Show First N Groups" is set to "All" but the chart has text stating "and 7 more" on the y-axis.

Just use form field. Will also need to update clickable y-axis a bit.

Add a filter for OPEN_TIME and implement conditional check to guarantee backwards compatability

Test Notes

• Verify that a new filter appears for Query Open Time and filters appropriately.
• Using a dataset without the OPEN_TIME variable, verify that the chart still renders without this filter.

In some cases the Query Age column doesn't sort correctly in a numerical fashion. See the screenshot for an example.

Test notes

• The Query Age column should sort numerically rather than alphanumerically. All other columns should sort alphanumerically.

As you can see in the screenshot, the x-axis is abnormally large for the size of the bars displayed. It should adjust based on the size of the bars. This bug seems to be introduced when the user chooses "Grouped" in the bar arrangement toggle.

This was found by DMEDS and they would like it to be addressed in the next version.

Test notes

• The Data Guidelines page in the wiki details all required and options renderer settings that serve to map input data.

Avoid calling in Internet Explorer.

When I was creating documentation for the latest release, I noticed that the Marking Group and Visit filters were missing.

Test notes

• By default a filter labeled Marking Group (and one labeled Visit/Folder) should appear in the controls, both multi-selects.
• The setting associated with each is marking_group_col and visit_col, and defaults to Query Open By: Marking Group and Visit/Folder respectively.

Filters on form
Group by form field

Can we add a Visit filter to the graphic? Given how Rave handles folder renaming this could potentially be a bit unwieldy, but I'll look at streamlining the .csv before it gets to the graphic.

(Request from Derek via email on 5/24/16)

The marking group filter disappears when I enter the settings for the visit filter - we want to make the marking group filter a customization

Not urgent

Right now the Query Age Category filters are data driven, but DMEDS has requested that we enforce a standard set of options. Options should be:

• 0-2 weeks
• 2-4 weeks
• 4-8 weeks
• 8-16 weeks

• 16 weeks

• Closed
• Cancelled

Test notes

• The Query Age Category filter should have seven statuses:
  • 0-2 weeks
  • 2-4 weeks
  • 4-8 weeks
  • 8-16 weeks
  • >16 weeks
  • Closed
  • Cancelled
• These statuses are derived in the renderer given a variable whose name defaults to Query Age, measured in days.

Specifically offset vertically as a function of both y.rangeBand() and the associated query status as it appears in the query status order.

Probably related to way values are being pushed in to arrays in the default-settings.js file. Hopefully we just need to build in a check for multiples before pushing.

in src/chart/onResize.js:

      chart.filters
        .filter(filter => filter.col !== chart.config.status_col)
        .forEach(filter => {
          if (filtered === false && filter.val !== "All")
            filtered =
              d[filter.col] !== filter.val ||
              filter.val.indexOf(d[filter.col]) === -1;
        });

update to treat string and array filter.val values independently:

        chart.filters.filter(function (filter) {
          return filter.col !== chart.config.status_col;
        }).forEach(function (filter) {
          if (filtered === false && filter.val !== "All")
                filtered = typeof filter.val === 'string'
                    ? d[filter.col] !== filter.val
                    : filter.val.indexOf(d[filter.col]) === -1;
        });

Click on a bar get a table