Under the new merging process, it appears that the merger can no longer make the decision whether to accept new information from the second profile. For instance, if the existing profile does not show a death date, but the new, second profile does, then the merging process automatically moves the new death date into the merged profile, even if the merger knows that the date on the second profile is not accurate. Under the current system for merging, the merger has the option to accept the new date or not. Seems like that would continue to be an option. Here is an example: I merged Hannah Smalley G18Z-5L9 (created in 2024) into Hannah Smalley LKWB-HMN (created 2012). The older profile did not have a death date because it is unknown. The newer profile has a date of 17 May 1708, which is the date that her deceased husband's will was proved in court. That is NOT a death date for Hannah. I did not want it to be added to the older profile, but there was no choice in the matter. Now the record has that date, along with my ID for adding it which implies that I agree with this proposed date. Sure, I can delete the date after the merge happens, but that puts more burden and steps onto the contributors who are trying to keep superfluous duplicates created by new users from excessively encumbering our one-tree-for-all. I would humbly ask that you reconsider instituting options on acceptance of new information from the merging process. Thank you.