Ticket #307 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Importer mapping step should be improved

Reported by: business@… Owned by: jannekevdp@…
Priority: major Milestone: 0.6.5
Component: Import wizard Version: 0.6.3
Keywords: Cc: jannekevdp@…
Product: Operating system:
URL: Hardware:

Description

Importer mapping step should be improved.
* By default, everything should stay on don't import
* Add a button 'Guess mapping from column names'
* Add a dropdown 'Load saved mapping' (only with the chosen entity and template)
* Add a button 'Save mapping' (and ask for the name)

Add name, entity and template to ImportMapping?.

Change History

Changed 3 years ago by work@…

I find the 'save mappings' functionality overcomplexing and not so userfriendly. I would rather see that the importer became self learning and:

1. store and count mappings
2. store and count user mappings

If, for example, the field 'bla' was mapped 100 times to 'species', and it was mapped 4 times to 'gender' the application would find 'species' most likely and select 'species'.

You could also weigh the user in this mechanism. So if, for example, the field 'bla' was mapped 100 times to 'species', and the user has mapped it 10 times to 'gender' and only 4 times to 'species' the application would find 'gender' most likely and select 'gender'.

The more imports are performed, the more accurate the importer could map the entities...

Changed 3 years ago by business@…

That's a nice idea Jeroen! However, it's not very agile to think so much ahead of our users. The request was to be able to save and load the mappings, this is easy and straightforward to implement, so I think we should do that first.
If users really end up having 100 mappings we should do something about that. But I doubt it. What I have seen so far is that most users have their own standard Excel formats, which result in only a few mappings.
So let's first proceed as proposed in the ticket description.

Changed 3 years ago by work@…

What a user wants does not always reflects what is the best solution ;) So 'being agile' does not mean you should stop thinking about 'what they _really_ want' :) But let's go ahead with your suggestion, and keep the 'learning' importer in mind for the future...

Changed 3 years ago by t.w.abma@…

  • status changed from new to assigned
  • owner changed from t.w.abma@… to business@…

All requested features are implemented in revision 1528, functionally working, but graphically intuitively suggestions are always welcome.

Changed 3 years ago by t.w.abma@…

On top of my last reply I mean: suggestions on how to give the user access to load/save/match/clear functionality, currently it's just a bunch of buttons and divs. Ideas on another approach are welcome.

Changed 3 years ago by business@…

  • milestone changed from 0.7 to 0.6.4

Changed 3 years ago by jannekevdp@…

  • owner changed from business@… to t.w.abma@…
  • cc jannekevdp@… added

When I go to the next step and back again, assigned column properties are mixed up again.
The buttons save,load,clear, match can be more attractive by adding mouseover-text for explanation?
*Save and load options don't work properly yet
*Clear option works properly: puts all to don't import

Changed 3 years ago by t.w.abma@…

  • owner changed from t.w.abma@… to jannekevdp@…

I did the mapping on CI and did a next/previous a few times, but the mappings don't seem to get "mixed up". Could you clarify this a bit more?

Same applies for the Save and Load options, I can save and load mappings here, but it might be that the buttons are not intuitive enough. What did you do to save and load mappings?

Changed 3 years ago by jannekevdp@…

  • owner changed from jannekevdp@… to t.w.abma@…
  • component changed from Unknown to Import wizard

Save and load options works indeed.
However, when I press enter after filling in a new name for saving (instead of pressing save) will leave the page and go directly to first step without saving.

Mixing occurs when:
I hit match, then assign some of the columns manually because they didn't match correctly. When I go to step 3 and back, columns are all assigned following the 'match' scheme. The wizard seems to forget the changes I made manually after the matching.

Changed 3 years ago by t.w.abma@…

  • owner changed from t.w.abma@… to jannekevdp@…

Disabled the <Enter> key so you really have to press the Save button now. And the mixing up of properties after a next/prev is solved too, it now keeps the manual set properties instead of "matching" them again. Please test to confirm.

Changed 3 years ago by jannekevdp@…

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.