Where is "Not a Match" button for record hints? I know there used to be one.

LegacyUser

Michael W. McCormick, AG® said: Where is "Not a Match" button for record hints? I know there used to be one.

I think it may have gone away with the recent update?

LegacyUser

Michael W. McCormick, AG® said: Okay, it looks like the reason I could not find it is because this record is already attached to the right people.

I guess the only way I can make this record "Not a match" is to detach the correct one, and then mark the wrong one "not a match" and then reattach the correct one.

The Not a match button is usually in this spot, but does not show up because something is already attached.

This is a bug that proves that another "Not a match" button should be put somewhere or something needs to be fixed. Such a button could be added next to every place that had a "review and attach" button.

LegacyUser

Mark E. Gower said: Michael, Why are you having a conversation only with yourself? You are right-- one should not have to go into the "Source Link" to say "NOT A MATCH". However, I am finding many duplicate source records, as well as records for children that mention the parents.

LegacyUser

Cynthia Louise Van Dam said: Some people suggest attaching duplicate sources. That way they will show up as attached and not get attached to a duplicate. Sometimes there is slightly different information on a source in a different indexing. for instance I have seen marriage records that sometimes do and sometimes don't include the parents names. I know there is debate about whether to attach information about children to their parents. I attach records like that to prove the relationships. But I know others feel that clutters up the sources. I don't think any such records should be marked not a match.

LegacyUser

Gordon Collett said: Interesting set of bugs that you found here that should get the source linker programmers and the hints system programmers scratching their heads.

In addition to your question of why is the "not a match" button missing from any hint, is the question of why this hint is pointing at both Clifford and Cheston when Cheston is the better match anyway.

Here is a picture of the entire family as sourced from this census entry:



I see that on Cheston's page, you have the same, but reversed situation. There is a census hint there for Clifford which points to Cheston's record.

It appears that the hints routine considers Chasten and Clifford probable duplicates. However the possible duplicates routine does not find them as possible duplicates.

If this is going to happen whenever two siblings have similar names and similar birth dates, the "Not A Match" button definitely has to be present. It would be too hard to remember to check all the source hints first and mark all the not a matches first before attaching any of the sources.

LegacyUser

robertkehrer said: Michael,
Our UX designers have been discussing a solution to this problem. I expect we'll have something designed, tested and implemented shortly.

Mark, Cynthia,
Duplication in some of the record datasets is a known issue that the records publication teams have been working on over the last few months. We will shortly have in place the required technology to deprecate these duplicate records. The recommendation is that you link these up to to properly indicate they belong to the person in the Family Tree and keep other users from creating duplicates in the tree.

Gordon,
Could you send me the URL from the top of this attach tool page so I can recreate what you are looking at and take a look at what can/should be done.

-Robert Kehrer
sr prod mgr

LegacyUser

Gordon Collett said: Just start from the ID that Michael provided: K6W4-59G

You'll see then entire path of the problem starting with Michael's relative, Clifford, whose page has the hint for his brother, Cheston, that won't go away and can't be declared as not a match.

LegacyUser

David Roderick McLean said: A temporary work-around is to:
1. Go to the person page.
2. Detach the source.
3. Find the source and select "not a match"

LegacyUser

Mark E. Gower said: The problem is NOT the source but the person being matched to. Change the person on the left and everything will then match-up. If Not, then drag each person, on the left, to line-up with the right person, on the right.

LegacyUser

Jade said: One simply moves the listing on the left down to the one that actually matches it, **before** attaching to the wrong one. In the example above, click on "detach," then move the listing.

LegacyUser

Gordon Collett said: Actually, as Michael explains above, all the census sources are attached to the right person. In his example above, I did go one step further and change the focus person on the right from Clifford to Chesten. When you do that, everyone shifts to the proper position, everyone is attached properly, there are no warning signs, there are no attach buttons, and Clifford's hint is still on Cheston's page and Cheston's hint is still on Clifford's page.

If you clicked the detach link in the example above, it would detach the source for Cheston from Cheston's record - that is why the two sections show dark green when you hover over them.

LegacyUser

Gordon Collett said: I did that and everyone does line up just fine. The sources are connected properly to the proper people. This issue here is the hints that are on the wrong people and cannot be marked "Not A Match."

LegacyUser

Edwin Evenson said: Five years later, there still seems to be a problem with how to remove an incorrect
record hint from a persons time line. Please keep coding.