I know about the problem of duplicate naming of children as I have several in my tree. However I have opened up a new branch that includes a number of well known people and these seem to be producing most of the Smart Matches at present. Just after my post yesterday I looked at a new match with another tree in which the same person was repeated eight times, each with a slight variation in the details.
I take your point about older trees sometimes being the most reliable.
I find that if the trees are carefully named then it may be possible to work out which is the main tree, often helped by the number of people in the tree I will confirm a name in that tree and ignore the other trees. Unfortunately some trees have the most obscure names which doen't help. It is a pity that site mangers aren't more thoughtful and avoid abstract names.
Yesterday I clicked on the green smart match button on one of my tree members. Got a whole bunch of matches. Today I clicked on the same button, same person and was told there were no matches. What is up with this?
The Smart Matches are generated when you make a change in your family tree either via your online family site or if you use the Family Tree Builder Software and synchronize to your website. The data in your family tree will then be compared with over 27 million other family trees at MyHeritage. It may take several days to collect the data, depending on the size of the tree.
The Smart Match technology is very dynamic. In this "intermediate period" web-masters make changes in their family trees sometimes even remove individual profile cards and even entire family trees. The result is that you have received a message that you have a Smart Match, but that the data has been removed. The result is an empty smart match.
If you would like to me to check it more thoroughly for you, please give me the name of that person to which you received those Smart Matches.
I checked that person you mentioned and I see that you have confirmed two Smart Matches to him, because I can see on his profile page under the 'Sources citations' section that information.
Those matches, however, do not appear on the Smart Matches page on the site. I believe that the reason might be that you have confirmed those matches on your Family Tree Builder, copied the source onto the data of your project and then synced it to the site.
Since the Smart Matches that appear on the site are not connected directly to the matches that you received on Family Tree Builder, by confirming on one of the platforms, it will not influence on what you see on the other platform.
The Smart Matches within FTB and the Smart Matches within the Family Site are different and are not connected. They are generated apart from each other. If you confirm a Smart Match for Person A in FTB and you also have a Smart Match in the Family Site for Person A, then confirming the Smart Match in FTB for that person will not affect the pending Smart Match in the Site. These are two different Smart Match algorithms and do not affect each other. Maybe it is the same Match for the same person, but since it was generated by different algorithms (FTB and Site) it is seen as separate Match.
But, if you merge a Smart Match in FTB, meaning you add information from the Match to the person card and you save and sync, then this information will of course be synced to the site and the Information is the same as in FTB, but this happens because you took data out of the match and attached/merged it within the person card.
I never, and I mean never do updates or smart matches on the site. I do everything in FTB and then sync it to the site. I only use the site so others can see the tree. Seems like MyHeritage has a problem with the smart match system.
In FTB, I clicked on the Smart Match button at the top of the screen. I got the screen below. William Frost has 5 Matches and one of them is Confirmed. When I clicked on the name William Frost I got the second screen below that says there are no Smart Matches for William Frost. How can one screen say there are 5 Smart Matches and the other screen say there are no Smart Matches?
So it pretty much confirms my previous explanation. The match was a 'blank' one. The user on the other side probably delete his tree, made it private or made that person private or delete that person from his/her tree.
Therefore, once you refreshed the system on your FTB, those matches aren't available any longer.
Just so you know, all 4 people who deleted William Frost from their trees or made him private on the same day just decided on the same day and in the same hour to put him back into their trees or to make him public again.
Remember you had four empty matches before? Those matches had already been privatised/deleted.
But because the Smart Matches page on your Family Tree Builder wasn't updated, you still had that link for those matches, but when you clicked on it, you couldn't see those matches.
When you, yesterday, refreshed the system by loading and syncing the project, FTB then again 'looked for' those matches, understood that those 4 didn't exist anymore and then 'deleted' them from your FTB.
So basically, what happend was that you had the system refreshed. It sent new information to your Family Tree Builder that now those 4 matches didn't exist anymore and because of that they disappeared from the list. Before, your Family Tree Builder had the information that there were matches, which wasn't already true, but it continued showing the link because you have not refreshed the system.
I would like to share with you a more comprehensive and technical explanation on Smart Matches, as it seems that my previous explanation seemed to simplistic for you or that a lack of technical terms might have given you the impression of 'incorrectness'.
On the family site:
After you sync your tree, or edit your tree the smart matches are being sent for reprocessing.
A daemon (a robot) is being sent to match the individuals on tree with other individuals on other sites.
Once the daemon has finished checking all the matches it stores them in a Database and eventually presented to the member.
The member can confirm and reject the matches, and he can also ignore specific trees and never receive it.
There might be an incident where there is a number in the Pending matches, but the smart matches page is empty. This happens due to the fact that after the daemon has collected all the information and stored it in the Database, the information has been changed.
Which means that the information that the daemon collected is outdated, which also means that the site can't find the individuals that it was referring to in the past.
For example the following process describes the problem (in a very oversimplified manner):
You uploaded tree X.
The daemon found you a match with tree Y and stored it in Smart Matches Database (SMD).
The site manager of tree Y deleted the tree.
The matches are presented to you and the pending says (13) matches for tree Y but there are no matches when you open it.
It happens because tree Y in database SMD is referring to tree Y, but it can't find it.
On the Family Tree Builder:
The smart matches system is split into two different systems:
1. Ad-hoc matches
2. Normal smart matches
1. Ad-hoc Matches provide you with instant findings, all you have to do is edit something on a profile of a person and the family tree builder software will automatically look for individuals in other trees that fit this.
It does not have a smart algorithm and so you wouldn't necessarily receive the same matches as the other system.
2. Normal Smart Matches will look for smart matches with it's own algorithm and is using the Smart matches Database. Which means that if you didn't sync it wouldn't let you click on the "Update" button to receivematches.
There might be inconsistencies between the Normal Smart Matches on the family tree builder and the Smart matches on the family site in the number of matches as they use different algorithms to present the data to the user.
The connection between the family tree builder and the site:
There is almost no connection between the systems, as they are both very separate.
Confirmation on one of the matches in the FTB doesn't confirm the same match on the family site online!
Vice versa doesn't happen as well!
Only manipulation to the tree data will result in the syncing of the information (NOT confirms or rejects! only tree data! such as name change).
While FTB uses the same database of matches it wouldn't necessarily show the same amount of matches, in fact the more accurate presentation of the matches would be on the family site.
I hope it helps you to understand how the system works.