Skip to content

[Schema Builder] Load: Improve feedback, consistency, and flexible input #550

Description

@cmrn-rhi

Disclaimer: Generated from 'UX Review - DH Schema Editor (2025)' worksheet tab '2) Heuristic Review' using Claude Code on 2026-06-04; please review to the original sheet for the original human curated version of this information.

Overview: These findings highlight opportunities to strengthen visual clarity and user control — specifically around making interface states immediately readable at a glance, keeping visual feedback consistent across interactions, and ensuring users can recover or re-apply actions without unnecessary detours.

Findings in this issue:

  • Finding ID 61.1 - Make it easier for the user to comprehend what is happening "at-a-glance". (Cosmetic - No Action Impact)
  • Finding ID 61.2 - UI consistency. (Cosmetic - No Action Impact)
  • Finding ID 61.3 - The ability for the user to execute commands even if they stray from the expected course of action. (Minor - Action Friction)

Finding ID: 61.1

Severity: Cosmetic - No Action Impact
Review Status: 3- Ready for Review
Priority: Awaiting dev review
Originally Reported: 2026-01-15 (DH 1.9.9, dh2-1m-rework)

Issue

Overall good but there are a couple of things that stand out to me: (1) When I see the "concise form" it isn't immediately obvious to me what I am looking at, whereas the non-concise version makes it clear I am comparing and mapping column headers. The concise form is super useful but I don't think we should start users there, instead give them the full view so they can form a quick cogntive model of what they are doing. (2) The "custom mapping library" feels a bit like information overload when I am just trying to get my bearings on the basic mapping.
I found no issues with the actual data mapping. All the columns and their contents mapped where they were supposed to and the custom mapping library behaved as expected.

Goal

Make it easier for the user to comprehend what is happening "at-a-glance".

Recommendation

  • (1) Have the default view be the non-concise form so that users can form a full mental model of what they are looking at. I know this may feel counterintuitive but I do strongly believe this would be easier for users to mentally process / recognize. It also makes it easier for users who aren't familiar with this error to see the yellow column highlights described in the info text.
  • (2) Have the "Custom Mapping Library" start minimized, breaking up the density of information they are immediately presented with.
  • (3) Add a window header / error title like "Header Mismatch Detected" that gives users a quick reference to what is happening.
  • (4) Capitalize the form headers "Template Field" and "Data Table Field" to better match with other DataHarmonizer UI elements.
  • (5) Relable "Reset form" to "Reset Mapping"; it matches better with "Apply Mapping" and is more descriptibe of the action that occurs when they press the button.
  • (6) [Not shown in recommendation mockup] Make it so the yellow highlight includes the bracket ")" so that single digit numbers have a more prominent highlight/
  • (7) [Not shown in recommendation mockup] Suggested changes to infotext: Some template fields do not match the fields in your selected data file . Unmatched fields appear in orange and can be corrected by dragging the appropriate data field to the corresponding template row; any field left unmapped will not have its data imported. Yellow highlights mark column numbers for fields that already match but appear in a different order than in the template; this has no effect on the imported data because matching fields are automatically aligned. In the case of JSON files that contain only fields with values, you may see many unmatched template fields; these do not need to be mapped.

Issue Screenshot / GIF

Image

Recommendation Mockup

Image

Finding ID: 61.2

Severity: Cosmetic - No Action Impact
Review Status: 3- Ready for Review
Priority: Awaiting dev review
Originally Reported: 2026-01-15 (DH 1.9.9, dh2-1m-rework)

Issue

When some clicks and drags a data table field header there is visual feedback in the form of a colour change where the new position is a bright blue and the old empty position is a muted blue. When a save mapping profile is applied we don't see the same colour change feedback, everything remains orange.

Goal

UI consistency.

Recommendation

  • Make it so the colour change feedback described also occurs after a mapping profile has been applied.

Issue Screenshot / GIF

Image

Finding ID: 61.3

Severity: Minor - Action Friction
Review Status: 3- Ready for Review
Priority: Awaiting dev review
Originally Reported: 2026-01-15 (DH 1.9.9, dh2-1m-rework)

Issue

If you reset the form after applying a custom library pofile - there isn't a direct action that allows the user to reapply the profile, they have to click off into another menu option and then reselect the desired profile which is awkward or could even cause a user top give up on the task.

Goal

The ability for the user to execute commands even if they stray from the expected course of action.

Recommendation

  • Include an "Apply Profile" action button.

Metadata

Metadata

Assignees

No one assigned

    Labels

    UXUser Experience related issue

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions