[Koha-bugs] [Bug 23019] Ability to create 'matching profiles' when importing records

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23019

--- Comment #32 from Agustín Moyano <agustinmoyano at theke.io> ---
Hi Katrin, I'll respond between lines

(In reply to Katrin Fischer from comment #29)
> This works, but I feel the GUI is not very intuitive. Actually, it took me a
> while to figure it out. 
> 
> The profile is "started" at the top of the page, but then after making your
> settings, you have to make sure to hit "Update profile" for the settings to
> be saved. So the workflow is like this to add a profile for it to work:
> 
> 1) Enter a name for a profile, click on add
> 2) Make the settings you want
> 3) DONT CLICK IMPORT - or your profile will save with the wrong values
> 4) Go back up, click "Update profile"
> 5) Import
> 
> I got it wrong the first time and was very confused why the "wrong" values
> showed up on managing the staged import. 
> 
> If a profile was selected, values can be changed. After importing it's not
> clear what was used for the import - the values from the profile or those
> set (and not saved in the profile) of the form? The profile values will show.
> 

Selecting a profile just pre-fills the form, if you change a value in the form,
that's what counts for importing.

I thought it good to keep that flexibility, thinking that maybe someone trying
to import, might want to use almost all values from a profile, but change just
one or two. 

> I really believe we need to improve this a bit before including it.
> 
> Ideas:
> 
> - Remove the buttons from the profile on top of the form and only show the
> list of existing profiles there.
> - If a profile is selected, change the values in the form below.
> - When one of the settings is changed, show a hint behind the field.
> - When importing:
>   - when profile is used and no field was changed: import
>   - when no profile was used: import
>   - when profile was used and values changed: ask if the profile or the
> changed values should be used (and possibly if the existing profile should
> be updated)
> - At the end of the form offer to save the settings as a new profile or
> update the existing one. This way, you can start at the top and work your
> way down.
> 

I'll remove the profile from the top and place them below. I'll also add a text
to clarify that selecting a profile just pre-fill's your form, but values can
be changed.

> 
> Alternatively: 
> - Allow creating, updating and deleting profiles from a different
> configuration screen. 
> - When a profile is selected, disable the other form fields so it's an
> "either or" and it's always clear what will be applied for the import.

I thought of this, but it would be a configuration screen exactly the same as
this one.. it seemed kind of repetitive and less maintainable.

-- 
You are receiving this mail because:
You are watching all bug changes.