Log in
Sign up
View all  |  Close all
#
Subject
Posted by
Actions
1
Smart matching list unmanageable
Vincent Veldman
- Close

I have 3709 Smart Matches up to this date for 319 people.

Which is not a big issue of course, I can set accuracy higher to lower the "hitlist"

But what I'm missing is the feature to "hide" those matches where I already checked all

and confirmed/rejected them.

For example: "Andries Harms Veldman" has 88 Matches. 17 of them are valid matches I've confirmed.

71 of them are not valid which I've rejected. But there's only the notification of the 17 confirmed.

So I can't be sure if I checked them all, or not.. I.e. maybe a new smart match comes up from a new 

family tree and then there would be 89 Matches, 17 confirmed, 71 rejected, and 1 unconfirmed.

But there's no way for me to know the actual status.

So, it would be a very good feature (option) if I could tell the program:"if all the smart matches of a specific

name are confirmed and/or rejected, then hide this person" so the moment a new unconfirmed match has been found

it comes back to the list of smart matches telling me:" 89 matches, 1 waiting for confirmation/rejection"

If this is too much work for the software development department to be included to the next patch/upgrade,

then at least consider the possibility to change the displayed message from "88 (17 confirmed)" into

"88" if all has been confirmed/rejected or "88 (xy waiting for confirmation/rejection)"

 

Thanks once again for reading my suggestions

 

Vincent Veldman
Moscow
- Reply
2
RE: Smart matching list unmanageable
Eric Dalton
- Close
The best way to keep track of smart matches is to view them by family tree instead of by name. Then view them by site manager instead of by New Matches. That way you can keep track of everything you have and haven't confirmed.
Eric Dalton
- Reply
3
RE: Smart matching list unmanageable [2]
Vincent Veldman
- Close
Good point! But it would still be easier if there were an option "hide rejected/confirmed"
Vincent Veldman
Moscow
- Reply
 
Loading...
Loading...