Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qualitative Colors #302

Open
isaisabel opened this issue Jun 9, 2021 · 1 comment
Open

Qualitative Colors #302

isaisabel opened this issue Jun 9, 2021 · 1 comment
Labels
enhancement New feature or request Points: 8 8 agile story points seeking feedback Seeking feedback from the community on this issue timescale/imminent Ready to be assigned to developers

Comments

@isaisabel
Copy link
Contributor

isaisabel commented Jun 9, 2021

As a user, I want to be able to color technique cells in the matrix qualitatively according to the comment or a metadata value.

Allow the user to enable qualitative scoring. This interface should probably be found within the color setup interface, which can be moved to the sidebar area implemented in #301.

Values that can be colored qualitatively

The user should be able to select the field used for qualitative scoring. Options should include:

  • comment, wherein I, each unique comment value would get a color. e.g if the user is using comment to denote APT usage (ordered in an alphabetical comma separated list) the color could then uniquely identify the set of APTs using a technique.
  • any defined metadata keys. E.g if the metadata key/value "coverage" ("low"/"medium"/"high") was selected, low would get a color, medium would get a color and high would get a color.

Only one field can be used for quantitative color at a time.

Coloring qualitative data

Once a field has been selected, the user can define the color palate applied the values under that field. There should be two options for quantitative color palates:

  • Ordinal data are defined using a gradient applied to the ordered entries. The user should be able to order the values as desired and the colors within the gradient assigned automatically using that order. The gradient itself should be editable with the same interface as the current score gradient setup.
  • Nominal data allows the user to define the color of each value individually. Predefined nominal data palates should also be available to quickly assign recommended colors to the values, conceptually similar to the options provided by Matplotlib:
    image

Behavior when a new value is added

When a new value is added, e.g a user creates a new comment or metadata value that is not already colored, a new entry should be added to the color palate.

  • For ordinal data, the entry should appear last in the series.
  • For nominal data, a randomized color should be selected (optimally the one furthest from already used colors).

In both cases, the UI should indicate that the user should customize the color, perhaps by flashing highlight on the color setup button or auto-opening the color setup sidebar.

Legend integration

Values of both ordinal and nominal qualitative data should show up in the legend(?). Note: this would be inconsistent with score color which doesn't show up in the legend. Perhaps the legend should be redesigned to show any colors (via score, nominal field) as well as custom user entries are are currently possible.

@isaisabel isaisabel added enhancement New feature or request seeking feedback Seeking feedback from the community on this issue timescale/short-term Becomes timescale/imminent in weeks or months labels Jun 9, 2021
@isaisabel
Copy link
Contributor Author

We may also want to add some sort of autocomplete feature to comment fields if they are selected for generating quantitative color. The autocomplete would recommend existing values of that field (but not disallow new values being added). This would help avoid spelling/capitalization issues creating new qualitative values through user error.

@isaisabel isaisabel added this to the Version 4.5 milestone Jun 16, 2021
@isaisabel isaisabel added the Points: 8 8 agile story points label Jun 24, 2021
@isaisabel isaisabel added timescale/imminent Ready to be assigned to developers and removed timescale/short-term Becomes timescale/imminent in weeks or months labels Jul 16, 2021
@clemiller clemiller removed this from the Version 5.0.0 milestone Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Points: 8 8 agile story points seeking feedback Seeking feedback from the community on this issue timescale/imminent Ready to be assigned to developers
Projects
None yet
Development

No branches or pull requests

2 participants