That would imply "intelligent" software that is built to "learn". This system is not that sophisticated. It's just a database that is algo'd to find similarities and spit them out automatically... nothing "intelligent" about it.
I say we all boycot Smart Match until they improve it.
I'm sorry to hear that you have issues with the smart matches, we are currently working on big improvements for the accuracy of the Smart Matches and a new way to calculate them. This project is advancing pretty good, as I wrote earlier in one of the forum posts - we have made up to 97% accuracy in taking samples of bad matches and recalculating them in the new system (which was able to identify them as bad).
If there's anything at all that you would like me to check such as specific issues with the smart matches I would be more than willing to go through them and to try to explain why would this happen.
We haven't heard of any new reports of individuals losing Smart Matches (which may be as a result of fixing internal bugs in v7113), most of the cases are happening because of accidentally uploading the same trees as new ones (and then deleting the older one).
Smart Matches coming back (or recalculating) depends on the size of your tree, it could take a couple of minutes (very small trees) and it could also take up to a week (very large trees).
What happened in your specific case is that you have uploaded a GEDCOM backup.
Which means that this GEDCOM will be counted as though it's a brand new tree. This will result in all of your smart matches to recalculate. Since you have many individuals on your tree it may take some time until you will see the same matches again (should be few days).
It is always recommended to stick with one tree on your site and to build it up.
Saving this tree under a different name in the family tree builder (using the save as... function) or uploading a different gedcom will result in the project to be calculated as a brand new one - and should be avoided.
We're sorry for the inconvenience and let us know if there's something we could do for you!
thank you for the message. Yes, you are right. The match is not accurate. However, a new mechanism for calculating Smart Matches is already in our developer's hands and is on the road map as part of Smart Matches improvements. This new mechanism will reduce the number of false positive matches you get. It's much more robust than our current system. I'm not making any promises about time frames for release of this new system - there is still a lot to understand about the scope of the project before we can define and promise a time - but I thought you would be interested to know it's in the works.
We are also looking at the possibility of allowing you to configure your matches to show only a certain percentage of quality. It means you will be able to say "I only want to see matches that are above 80%" and then you won't have to be bothered with all the other, lower quality matches. If we can add this feature relatively quickly we will.
I agree that it is annoying when you get notified of a very high number of Smart Matches and very few if any are actually matches. But there have been times when a match of 35% was really a match that I have confirmed - and the other site manager confirmed it as well !! The percentage of accuracy given all depends on how much matching information is in both trees. This can really help the person with the lesser amount of information in their tree. I have found out a lot of information about relatively recent relatives, information that I have confidence is accurate because it comes from a living person closely related to the information. (This has happened to me more than once where someone with the name of "Unknown" was in the other tree but the birthdate, death date or other information was accurate.) If it were not for the inclusion of the lesser accuracy percentages those matches would not have been found and the other person would not have known the actual name of their "Unknown" !!
The biggest problem I have found with the Smart Matches is that occasionally I get notification of a match and when I go to check it out there is no match with anyone. And because of that there is no way to get rid of the match-to-no-one and it just hangs around forever. There is one way to get rid of it but you have to wait until an actual match is made with that tree. Then you click on "confirm all matches" or "reject all matches" to finally eliminate that false match. These options are not available if there is only the non-match with the other tree. This is something that needs to be rectifed and hopefully this will be part of the revisions made to the Smart Match feature.
I think it should be possible to configure what conditions need to be met in order to qualify as a Smart Match. Right now I am piling through a huge stack of so called Smart Matches, most of which are completely irrelevant. New ones keep popping up all the time, and the quality is no better.
As for myself, pretty much all of my entries have been checked and vetted with official records. So if I get an Anders Andersson (and yes, that's like John Smith to you), born 100 years earlier, in a completely different area of the country (or better still, in Norway or Denmark, yes, I get that too), I already know that that record is of no relevance to my research. And when you start getting 50-100 of the same it starts getting really annoying.
If I would be able to configure the conditions in order for a match to qualify, I believe I would get less irrelevant matches.
There are big efforts invested by our developers to update the smart matching system and we are working very hard on it. We have already achieved impressive results. It will take a little bit time though to implement the changes.
We will update you when this update will be available.
I'm so sorry for the any inconvenience that you are having currently!
There are big efforts invested by our developers to update the smart matching system and we are working very hard on it. We have already achieved impressive results. It will take a little bit time though to implement the changes.We will update you when this update will be available.
I suddenly have 91 (!) matches on a very odd named relative, and found that "Unknown", "Olsson", "Petersson" matched "Yllman", and difference in life was more than 200 years. The only thing you missed were a woman for a man. Your "smart match" is keeping me too busy checking off all your irrelevant matching. I think this is a scandal!