Another user has marked these people as not-a-match.

SherryGrabill

If a previous user marks a merge as not a match, is there some "required" notation that should indicate so. As I was reviewing a merge with the same notation, there are no notes that validate the merge should not be completed, or why it was considered as not a match. I found no discrepancies other than there were no sources, or dates to contradict the other; the match would be possible by matching spouses, children, location.

Gordon Collett

There is nothing required. Just like there is nothing formally required when editing anything. So there are often many changes in a profiles change log that do not have any reason given for the change.

If the user who marked two profiles put a reason it would show under dismissed Research Helps, in the change log, and when you try to merge them.

If there is no reason given and if you are certain these are the same two people, you can proceed with the merge. Even if there was a reason and you determine the reason was wrong, you can still merge.

FrankLittle

Everything Gordon said is correct, but I would like to point out that if someone has declared them not a match it's very worthwhile finding out why. I'd ask them (though I must admit people don't necessarily respond).

On a related note: though I agree we should provide reasons for our changes, sometimes the explanation is complicated. If (like me) you actually maintain your tree in your own local software or system, or indeed elsewhere from this site, the reason not to declare a match may be obvious to the person taking that decision from (extensive) previous work. I've noticed myself that the more complicated the explanation needed, the less I feel inclined to put in the time and effort required. (Yes, I know this is not good, and I try to fight it.)

Also, the place for lengthy explanations is not really the one offered (which has a limit on the number of characters, anyway), but is better in the Collaboration tab. I'm not sure people often check that before making changes. Some way to link to a relevant discussion or note would be a useful when accepting or rejecting a hint etc. ANd similarly a note that there is a relevant comment would be useful when making a relevant change.

Mary Anna Ebert

@SherryGrabill Thanks for the feedback!

We currently don't require a reason statement for Not a Match when reviewing a merge. There is a balance in what we can impede and require input from our users. We may add some checkbox options like we did for the merge reason statements and that might improve user's communication of why they think it's not a match.

Gordon is correct that even if they have been declared Not a Match, you can still merge them.

Thanks