There could be several reasons why no smart matches are generated. One of them is when a webmaster removes the display of the tree from the website. This way all related smart matches to this tree will be deleted as well. In other cases it looks as if there are no smart matches. The tree could have been synced from the Family Tree Builder software under a new, different name. And when this happens, this specific tree will be seen as a new tree, for which new smart matches will be generated. And this process may take some time, especially if the tree is large and has more than approx 2000 persons. I recommend you to logg in to your website and here click on the family tree > manage trees options.
Have a look at the display of both family trees and make a decicion with which tree you wish to continue to work. Duplicate trees will eventualy produce double smart matches, which is not recommended.
Jack is right - we could try and give a tree some priority in the smart match queue which I have arranged for you and you will see the results soon.
If you have any further questions just write to email@example.com and we wil assist you personally.
thanks for your detailed answer,I chose tree JaneKneis_2013 ashead tree and turned off match for the tree JaneKneis.But I Wonder, when I was checking manage tree to day suddenly JaneKneis is head tree and not JaneKneis_2013.
Maybe the best thing is to delete the tree not be used (JaneKneis)?
and yes, I know now that it was a big mistake to delete the old tree,I had a lot of match, it's something you only do once.
You can choose which tree you wish to see on display first. Just click on family tree > manage trees and mark the tree
of your choice as default tree by clicking on this option at the right side. You will see the green symbol on the left side that shows this tree is on display.
When the smart match option is unmarked and turned of then there is no immediate reason to delete the tree.
But if the trees are duplicates, I would recommend to consider it, in order to prevent possible mistakes.
New smart matches will be generated soon for your new tree. It may take some time as it will be compared with 27 million other trees at MyHeritage.If you already communicate with other webmasters regarding your mutual matches you could inform them by explaining that new smart matches will soon show for this tree and the reason why.
I can maybe see the relevance and even the possible need to not show information on minor children who are living. And that is just maybe. Anyway, the thousands of <Private> showing up on smart matches of people who have been dead for a hundred years drives me crazy.
Please, people use discretion in seeking privacy. .....hmmm people post family tree on internet and still expect privacy? Just sayin..
I think many people have settings on the web site set to restrict data access.
To fix this :
on the web, Hover the cursor over your name at the top left of the screen. select site settings.
go to : site settings/"My privacy"/"Access"
check all the boxes "on"
This is not a fix for all private issues ... a second problem (for me at least) was a number of individules that had no birth or death dates. The program considers them alive and there is no easy way to find them. I go into FTB and open the list people tab on the left, sort by death date and go down the list checking each person that has no birth date. I set them to deceased and the private flag goes away. I wish there was a better way.
There also seems to be a "bug" in the logic, The smartmatch screen shows private for some of the info but if you go to the "compare tree" function you can see the data. I think that this is related to the problem I have with matching trees in FTB where the other persons tree shows private but I can go online and see the info. (this alse sometimes results in the persons merged showing as unknown with no other data.
You can set FTB so that living people are marked Private. I suspect that in some cases, that "Private" is only because no death date has been entered. Matilda was born in 1803 but with no death date entered, the software may assume she's still alive.
Under Tools > Options > Warnings, you can set the maximum age for a living person. All this does is give a warning when you enter someone into your database. "Warning: Matilda Surname is not marked as deceased and is rather old (210). Are you sure you want to continue? Yes/No"
Choosing Yes accepts the record as is, and Matilda at 210 is considered to be strong, healthy, living, and Private.
Choosing No goes back to the record so that you can mark her Deceased and put in a death date if you know it.
I have often wished there were a choice for "Yes, mark this person deceased" to save me the extra click, or that the code was intelligent enough to recognize that this person's age is over the set maximum age and should automatically be marked as deceased and not even bother me with the warning.
I don't know, Tom. Ever hear of Methusalah, who lived six or seven hundred years?????
The "private" issue is irritating. Might be a great product suggestion that you've raised to get a note telling us if we've failed to enter deseased and that it will cause others to see private on our tree, when we didn't intend it to happen.
Too funny! Yeah, none of mine either. Best we've had lived to 120 years. Only a total of 9 got to 100 or better. I don't know if I want to live that long, except to fill in all the missing info on my tree, and it may take that long the way it's been going! Have a great day and thanks, I needed a good laugh!
You are quite right. This is the way it is supposed to work - but there is more to it! Most people do not seem to realise that a major part of their persons are marked private. When I have tested this with fellow genealogists which seem to have a lot of these cases. In the case you just described the Private flag is not necessarily set, you just have to make the conclusion yourself that the only reason why other people are seeing your persons as Private, is because of their age is exceeding the set limit. In other words you are not warned in any way that a Private sign is set.
There are also other problems with the Private designations. It is actually quite easy to bypass this function in the online version, which is illegal, at least in my country.
I understand an and agree we must protect the privacy of living individuals. The deceased flag can easily be set in the personal computer software. Why not make the same function available on the web software side. (at least for persons born before 1800)
Our Smart Matches system should receive the following 4 different matches for these two pairs:
1) Jim Smith - Joanie and Sally
2) Jim Smith - Joanie and Joanie
3) Jim Smith - Sally and Sally
4) Jim Smith - Sally and Joanie
The reason for this is that the smart matches system doesn't have a lot of excluding algorithms and thus it finds a lot of matches they may not match 100%. We are working on an update for the system where therer will be an extra filtering where it would hide the two unrelated matches.
Let me know if you have any further questions and I apologize for the inconvenience.