Log in
Sign up
View all  |  Close all
#
Subject
Posted by
Actions
1
Mass Smart Matching Commands
Paul J. Lareau
- Close
I can easily understand why the system would not want to dilute the accuracy of confirmed SM's, and you may not want to make it easier to be lazy, but it would be a big help for people managing very large databases and huge candidate SM lists to be able, in some circumstances, to confirm or reject blocks of candidate SM's instead of one-by-one, or all.  Some circumstances that might be suggested:

*  Selecting displayed candidate SM's =, <, or > a particular accuracy estimate percentage, e.g., confirm all SM's > 90%, or reject all SM's < 50%.    This would save time to devote to candidate SM's that might need a bit more careful checking.

*  Selecting all candidate SM's that are currently displayed on a screen to be confirmed or rejected with one keystroke.

*  Using a standard CNTL-Select function to select a number of entries (not necessarily absolutely consecutively) to confirm or reject groups.

While these would ultimately cause some sloppiness and errors in confirming/rejecting, it is likely that the lack of such features contributes to at least as many and possibly many more errors when users confirm "all" without even looking at them, when faced with 10,000 candidate SM's, for lack of time, or simply refuse to take the time to confirm or reject any of them and let the numbers build up.

No reply to this is needed.   Just a suggestion that might help many users at all levels.

Paul J. Lareau
- Reply
2
RE: Mass Smart Matching Commands
Paul J. Lareau
- Close
Another related suggestion that might be a bit easier to implement.

Under SMART MATCHES / Confirmed by Others / Review and Confirm:   

When you select a particular site, only the first 20 matches are shown.   Your choices are to edit them individually, or Confirm All / Reject All / Ignore Tree.     Unfortunately, the "Confirm All" is set to confirm ALL the preconfirmed SM's on that site, which is likely to have more (lots more!) preconfirmed SM's than the 20 you are allowed to see and check out.  The only way to see the whole set of SM's by clicking out of the Preconfirmed SM's subprogram, and it is cumbersome to say the least to get back.   

 What this needs is an added command to Confirm These 20 / Reject these 20.   Use of  "all" in this particular function is pretty much useless, unless you're into approving lots of things you can't easily examine.   But if you can process those 20 normally, mass (or selectively) approve/reject them as needed, then somehow load the "next 20" for processing, you can get through approving preconfirmed SM's quite efficiently and accurately.   This is really important in dealing with sites that have hundreds or thousands of preconfirmed SM's waiting.   And since you'd already be limiting the mass approval or rejection to only 20 at a time, it would actually improve accuracy since the entries are in %chance level.

 Without that fix, I pretty much have to limit myself to using this subprogram in cases where the site has 20 or fewer preconfirmed SM's awaiting me.    The program change that would fix this problem could also be applied to my other mass SM suggestions above.

 Paul J. Lareau

Paul J. Lareau
- Reply
3
RE: Mass Smart Matching Commands [2]
Esther Weinberg
- Close

Hi Paul, 

You are correct that this suggestion may be easier to implement.

Regardless, I will make sure that it gets passed on to the appropriate department for further consideration.

Best Regards,

Esther / MyHeritage Team 

Esther Weinberg
- Reply
4
RE: Mass Smart Matching Commands
Olav Bringedal
- Close

I second this suggestion, or alternatively just use check-boxes in the list with

 "accept", "reject" and "accept but "wrong details"  boxes and a submit button at the bottom of each list page

 

Olav Bringedal
Norge
- Reply
5
RE: Mass Smart Matching Commands [2]
Athol Geoffrey Stewart
- Close

I answered this but then the sky stole my answer.

YES!

We need 'Accept with wrong details' or maybe "Accept with some discrepancies".

It is essential because I want to confirm the match with the person, WITHOUT giving the impression that I am confirming all the details, when our details differ.

Geoff

 

Athol Geoffrey Stewart
Australia
- Reply
6
RE: Mass Smart Matching Commands [3]
Aviv Ben-Arie
- Close

Hi Athol,

Thank you for writing to us.

I  saw that in other forum threads you made a few additional suggestions regarding Smart Matches. I will forward all these to our development team, as they are all good helpful suggestions. 

 

Regards,

Aviv

MyHeritage.com Team  

Aviv Ben-Arie
Israel
- Reply
7
RE: Mass Smart Matching Commands [2]
Jens Martin Kofoed
- Close

I would be great if it will be possible to multi select "matches" and then reject the match. I got many matches where my person is dead before the match person is born or the bord/dead date differ with more then 20 years

/Jens

Jens Martin Kofoed
Danmark
- Reply
8
RE: Mass Smart Matching Commands [3]
Esther Weinberg
- Close

Thank you all for the suggestions. 

I will pass it on to the appropriate department for consideration.

Best Regards,

Esther / MyHeritage Team 

Esther Weinberg
- Reply
 
Loading...
Loading...