Is it possible to get a report against rejected merges that shows the ones where the data matches?

+17 votes
I just finished proposing merges for duplicate branches where the merges were rejected back in 2013.   The only way I found them was to stumble upon them.  There are so many valid rejections that finding the ones that are not valid is like finding a needle in a haystack.

I wonder if it is possible to take the "rejected merge list" and do a compare to find the subset of profile that might just be duplicates?   I know the arborists would be more than willing to work this subset of profiles and figure out if they are really 'not the same person'.
in WikiTree Tech by Robin Lee G2G6 Pilot (736k points)

1 Answer

+12 votes
Hi Robin,

Let's see ...

You're proposing something like a combination of and

FindMatches searches for possible matches for profiles in your Watchlist. You can set it to include rejected matches.

BrowseMatches can show rejected matches, but not just the ones that were proposed or that FindMatches searches would report.

The problem with the FindMatches feature is that it's just for your own Watchlist. You're proposing something that could be used site-wide.

Assuming I'm understanding you correctly ... how could we do it? I think we'd have to add a FindMatches search feature to BrowseMatches. As you page through rejected matches, it would search to see if they are likely matches and filter the ones that are not likely.

It's feasible but not a simple addition.

by Chris Whitten G2G Astronaut (1.3m points)
Will it not be possible to put the "rejected merge list" in table format where more information is visible.

That way we will be able see instantly if they are similar or not.
Do the feeds that Aleš works with contain any information on whether the profile is involved in a pending merge/unmerged match/rejected match?

Related questions

+24 votes
6 answers
+22 votes
11 answers
+36 votes
2 answers
+21 votes
1 answer
+6 votes
2 answers

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright