about duplicate profiles

Question

Is there a way to find out WHY & by WHO merges were rejected ?

I am working on clearing out duplicate profiles & I see soooo many obvious duplicate profiles with rejected merges. As a data doctor, how can I figure out what someone thinks needs to be fixed, when the profiles have the same names with exact same birth & death dates.

If there is no current way to do this, what do others think about forcing a response to why the merge is being rejected. Thanks

Comments

You can try pm'ing the profile manager. If you don't get a response, post the profile to the G2G

---

but that is the problem ... there are 2 profile managers involved & I don't know WHICH profile manager rejected the merge. I am loathe to bother so many profile managers that were NOT the ones who rejected the merge.

---

It was probably the creator of the most recent profile who rejected it on creation. It would not show on the Changes tab of either profile. I'm afraid some people don't really check the suggested duplicates when creating a profile.... And actually sometimes it is quite a loooong list. Propose the merge again, and you will see if someone responds?

---

I get an email when someone rejects a merge I have proposed, which includes their comment as to why they rejected. That comment should also be in the comments section on one of the profiles. Wondering if  you can reject without explaining why. and if an email is sent if they don't fill in the comment box.

Answer 1

wouldn't it be on the Changes tab?

Comments

thanks for the suggestion, but I checked & no it is not recorded there.

Answer 2

One of the most promising ways to approach such a situation is bringing it up here in G2G if the issue can not be resolved with the profile managers in question. A broader range of people can assess the situation and pros and cons can be discussed and a decision could possibly be reached.

Comments

that is fine with me & if it were an occasional problem. BUT I fear others will be annoyed with too many such messages. I make or initiate about 10 merges per day & have to bypass about 5 rejected merges per day, so it would be a lot of extra work to make messages about each of them & I think other readers here would begin to think it was clutter as they are not working on this specific topic.

Here is the last one I looked at ... Manerva CARTER

https://www.wikitree.com/wiki/Carter-21132

https://www.wikitree.com/wiki/Carter-11676

---

This one looks like it was rejected on creation of the second profile, Carter-21132. You know, when you create a profile and it shows a list of "close enough" profiles so that if you see that the person already has a profile, you don't create a duplicate. At this point if you check (x) some of the profiles on the list, you are marking them as Rejected Matches and they will be listed as such.

The person who created Carter-21132  was a newbie. Just re-propose the merge, state your case clearly insisting that the merge ought to be rejected ONLY if the two profiles are sure to represent different people. If it's rejected again, then...

---

thanks for the info :)

I didn't know about rejecting merges upon creation.

---

I see your point. Same dates and places, same father and yet rejected for whatever reason. Especially since the source for one seams to be the other via MyHeritage.com. I have removed the rejection and re-proposed the merge. I'll watch and start the Problems with Members process if no solution can be found.

---

I don;t always take note of who the profile managers. In this case,I don't think there will be any problem because I have actually been in contact with THIS particular profile manager about a different profile, asking her to correct something & I also offered to fix it for her if she didn't know how & she gave me free license to fix it as I saw fit ...

https://www.wikitree.com/wiki/French-7266

Answer 3

Since I learned something from about creation rejections from my last question.

I would like to follow up about a another duplicate problem that I often see which is Unmerged Matches. I am wondering why people refuse to merge 2 profiles that to me are obvious duplicates. Now my "guess" is that your answer may be that they are waiting for sources to magically appear without the profile manager having to do any work searching for them. I have seen many of these that are hanging around for a couple of years.

Below is an example of a recent on ...does this one have something to do with recent creation also ? I hope to gain some insight on these kind of merges rejections also ...

https://www.wikitree.com/wiki/Sherk-35

https://www.wikitree.com/wiki/Sherk-63

These 2 guys have same name, exact same dates, are both born in the same American county & both died in the same Canadian county. The likelihood that these are 2 different people, is so remote that it is not worth considering.

So why postpone the merge ? Why have both profile managers & data doctors & sourcerers & connectors all work separately on 2 different profiles. Why not merge the obvious duplicates & then put all the found source info on just one profile. I do not think sources are needed in a case like this, to conclude that both profile creators are talking about the same person. Thanks for your input :)

Comments

Just came across one that is over 2 years old & even has the same wife's name ... but the proposed merge is still set as an Unmerged Match...waiting years for sources to appear, I presume ...

https://www.wikitree.com/wiki/Wood-11847

https://www.wikitree.com/wiki/Wood-11207

The chance that 2 different man would marry 2 different women with the same name is very rare indeed, but I have never seen it happen in the same century. These 2 couples even have a child with the same name.

If a profile manage sets an Unmerged Match, shouldn't they look for sources asap ? Otherwise after nothing has been done for a month or so, why can't someone else make the decision to merge them ?

---

I create an unmerged match when the two profiles are clearly a match, but there are duplicate profiles (or conflicting profiles) for the parents and earlier generations. It's important to merge the parents before the child, to avoid disconnecting one set of parents.