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

Import Module improvements #1991

Open
3 of 16 tasks
sleidig opened this issue Sep 7, 2023 · 0 comments
Open
3 of 16 tasks

Import Module improvements #1991

sleidig opened this issue Sep 7, 2023 · 0 comments
Labels
Type: UX concerning user interface and in a broader sense user experience
Milestone

Comments

@sleidig
Copy link
Member

sleidig commented Sep 7, 2023

Based on initial user observations, there are a number of small-ish things to improve about our import UI:

  • not intuitive what are columns, what are profile entity fields (visualization?)
  • no warning indicator for date after selecting field, but format config is required
  • if column headers are not in first row -> column mapping screen very confusing (!)
  • dropdown options that are long and have a line break are hard to distinguish from the next option in the list
  • imported data might contain multiple different date formats (with/without leading zero of month, ...)
  • "continue" button sometimes overlooked
  • empty strings are imported as "null"
  • unmapped or empty values of enum props are shown as "[invalid option] undefined" in the preview (should just be empty)
  • column mapping dropdowns are rather narrow, hard to read to full field names (--> give more width)
  • save column mapping already when first continuing from the mapping step (in case the import fails the user otherwise has to re-select all the mappings ...)

value mapping popup:

  • popup warning for date value mapping about "unmapped values" would better be phrased as "unparseable values" or the like
  • warning popup for boolean value mapping "unmapped values" is misleading if the user actually wants to map some values to be - imported as "unchecked" (i.e. false) but there is no way to distinguish unmapped and mapped to "false" currently
  • boolean value mapping: more visual clarity that left value will turn into right value (checkbox is not selecting what value from left is imported but represents the actual value after import)

preview screen:

  • Import: need loading bar for preview #2429
  • sort order of rows to match the imported file? or maybe an extra column giving the row in imported file?
  • scrollbar horizontal not available in preview (some columns seem to be "missing" because they are out of the screen)
@sleidig sleidig added this to the Import UI milestone Sep 7, 2023
@sleidig sleidig moved this from Triage to Todo [community help wanted] in All Tasks & Issues Sep 20, 2023
@sleidig sleidig moved this from Todo (ready for work) to Triage / Analysis in All Tasks & Issues Feb 12, 2024
@sleidig sleidig added Type: UX concerning user interface and in a broader sense user experience and removed Type: Bug labels Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: UX concerning user interface and in a broader sense user experience
Projects
Status: Triage / Analysis
Development

No branches or pull requests

1 participant