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

Results of the UX test (advanced user) 1 #3

Open
2 of 45 tasks
a-kohlhase opened this issue Aug 21, 2019 · 0 comments
Open
2 of 45 tasks

Results of the UX test (advanced user) 1 #3

a-kohlhase opened this issue Aug 21, 2019 · 0 comments
Assignees
Labels
ux-issue UX test results

Comments

@a-kohlhase
Copy link
Collaborator

a-kohlhase commented Aug 21, 2019

MoSCoW (must-have, should-have, could-have, won't have)

MUST-Haves

  • Description Z/4Z not clear

  • filter f(3) is missing

  • Too many clicks before seeing results:

    1. select filter
    2. edit filter variable
    3. ENTER or clicking check icon
    4. clicking "Display results" button
    5. The minus-symbol not so clear
  • Results found:

    • Mismatch with list
    • initialize result list when updating this field
  • "Display results" button should be automatically changed to "Update results" button, if the two-step process is kept up

  • Default column order unclear

  • Default row order insensible

  • Default filter order? Lexicographic

  • Default data set order

  • Status of selected option for Boolean filters unclear

  • Default value for filter "invertible" should be set to true

  • Export to Gap, Sage, Excel/CVS (all, checkboxes)

  • Information about data set

  • font choice too small, color of text not very high in contrast

  • Instead of Home-Button (which functionality is already done via logo) create Contact-Button for creating the owners of the MathDataHub website

  • column names in "choose cols" do not correspond with actual col names

  • column headers should be left-aligned

  • grid structure in table should be clearly visualized

  • finished Boolean filter set to true not identifiable as identical with filter name

  • After having chosen a filter, the focus should go to the editable variables for that filter

SHOULD-Haves

  • search filters (with autocompletion)

  • filters are added via logical AND: extend this via

    • OR, IF, NEGATION, Parenthesis, equality
    • OR, IF, ODD, EVEN, positive (case-insensitive)
    • AND (which is typical case), subconditions like f(0)=f(1) or direct SQL-Queries (like Wikipedia formulae rendered and in LaTeX)
  • enable customizable nested ordering in results

  • search data sets (with autocompletion)

  • pagination option misses out on option "all"

  • "filter" should be replaced by "conditions"

  • Select filter area was clicked

  • Choose columns:

    • Cancel button confusing
    • didn't grab selected columns to available columns
    • didn't change col width
    • didn't try to change the order
    • "choose", "select", "available" all related, but differently named (suggestion: use visibility aspect)
  • too much scrolling space in results list

  • The finished filter variables should be clickable and open their edit-interface;

  • allow to enter more filter specifications (like 0<f(0)<3) at the same time

  • small (hover, click on ?-icon) tooltip information and link for

    • definition
    • example
    • How-to-use-it
    • related filter (e.g. for invertible the filters injective and surjective)
  • responsive design: showing only (positioning) after having selected filters

  • Order of filter entries could determine sorting order of rows

  • author should be able to set the order for filters

  • sampling (randomly) a small set for export

  • English as lingua franca not enough, but maybe "easy solution" via autocompletion list with multilingual entries

  • With caution (privacy issues if published on a general base --> "Make public" button needed): MathDataHub as a community tool

    • with recommender system,
    • contact other people interested in this combination of filters for dataset
    • contact author of data set directly or indirectly (possibly providing own eMail address), e.g. to inform about a missing case
  • Show-Checkboxes

  • Annotation tool for filters, combination of filters

  • Quality of data sets marked via stars/thumbs-up/…

  • Make use of semantics of lists for applying filters, e.g. apply a filter to the second entry in a list

  • tagging data-sets

  • session history

WONT-Haves

  • Instead of f(0), f(1), f(2): f(<…>)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux-issue UX test results
Projects
None yet
Development

No branches or pull requests

3 participants