https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21648
Mark Rogers <marcos.rog...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marcos.rog...@gmail.com
--- Comment #17 from Mark Rogers <marcos.rog...@gmail.com> ---
I agree that prevention of data loss/corruption is important. It sounds like
the implementation of Andrew's suggestion to have a full interface to merge
both patrons (though great) is currently a barrier to getting a more functional
solution for those of us who have required non-repeating patron attributes.
Would it be possible to simply treat the non-repeating patron attributes the
same way as the standard patron fields? That is, the default behavior would be
to retain those non-repeating attributes belonging to the patron record that
was chosen when initiating the merge rather than the values for those
attributes provided by the non-selected patron. The screen where the merge is
confirmed already has links to both patron records, allowing the differences of
patron records and additional patron attributes to be compared, albeit somewhat
manually.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
