Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Selection vs. typing to specify source/target elements involved in mappings seems unintuitive #22

Open
jpav opened this issue Jul 21, 2017 · 0 comments
Milestone

Comments

@jpav
Copy link

jpav commented Jul 21, 2017

Currently, mappings can be created very quickly via two clicks, one on element in the source tree and one in the target tree. Editing existing mappings can also be accomplished via simple tree selection. However, mappings that involve slightly more complicated transformations, such as the combine and separate actions, involve multiple source/target elements. In these cases, the user cannot use selection to add these additional elements to the transformation, but rather must type their names in text fields within the mapping detail area. The need to switch from selecting elements to typing their names seems unintuitive and likely to lead the user to inadvertently creating unwanted new mappings when trying to continue to use the selection paradigm when editing existing mappings. One suggestion would be to consider sacrificing a bit of the speed with simple mappings by introducing an explicit "map" button after the initial source/target selections are made to new mappings. This would allow for a similar flow when editing the aforementioned more advanced mappings such that the user could continue to use selection within the trees and simply click on buttons (presumably next to the associated fields) in the mapping detail area to update the text fields with those selections. The nice part is this would not preclude the use of the existing typing approach to add elements.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants