Robert, you can control -- to a very limited extent -- the quality of smart matches you get.
In Family Tree Builder, select Tools > Options > Smart matching(tm)
Set "Match similar first names" to No. This will prevent matches for Sarah and Sara or Robert and Roberta or William and Bil.
Set "Match similar last names" to Strict or Very Strict. This will prevent matching Schmitt with Schmidt, Smythe, or Smithers (or worse). You can also choose "Exact matches only" which will severely limit the number of matches you receive and still will not guarantee high percent matches.
It you're getting too few matches, back off a notch and run the search again.
Obviously (to users if not to MH programmers) there needs to be some control over the dates as well, something giving a range for key dates perhaps, such as
plus/minus 1 yr
plus/minus 2 yr
plus/minus 5 yr
plus/minus 10 yr
In the meantime, apply the limited control allowed and see if that improves your results.
thanks tom, for the info. I hate to restrict spelling of names too much because I have found so many variations in the Schmitt name in documents. seems like in the late 1800 so many people came to America with so many different languages it depended who did censuses. also I have seen some of my relatives spell their own name wrong because they couldn't read or write. its been fun trying to connect the dots. I have been able to get more information than I ever imagined about the Schmitt family though. my dads father died when he was only 5 but I seem to have been able to trace that tree better than the other 3 family names I was researching. thank you for the suggestions Robert schmitt
Receiving Smart Matches™, viewing them and comparing trees side by side are free for all users. The following features are available only to Premium and PremiumPlus sites: Expedited matching, the Consensus Page, confirming and rejecting matches, initiating contact with other tree owners, merging matches and copying photos and details from trees.
We show you ALL of your matches, the high quality matches and the lower quality ones.
The list is sorted by quality, so you’ll see the best Matches first, but we also show you the other matches below, so that no information will be hidden, and all your research potential will be met.
I subscribed to My Heritage last week, I uploaded 2 trees and got som great smart matches, so I uploaded the rest of my trees and was waiting for my smart matches, nothing happened in a few days so I done some googling to see if there was something I was doing wrong, only to see that it's quite common for it to take a long time to update, so in the mean time I can't do anything, can't search the trees because the subscription I have doesn't allow it.. feeling a little bit annoyed over it now....
thank you for writing. I can see that you are very new user by us. When you uploaded a GEDCOM it takes by us a couple days (usually up to 7) when the matches are performed and updated in the tree. I see that you have added several trees, even 2 days ago. Please be a little more patient. I updated all your trees manually and you should get them very soon. Thank you for understanding. Kindly let me know if I can help you further.
Maybe let people know via email that it can take days to update, on another website that I'm sure others used too, the matches happen as you add people, so others like me expect it to happen instantly when it doesn't!!! No patience and all that!!
I've just seen the new smart matches, thank you
I've turned off the smart matching on all the rest of my trees, is it better that I turn it on one by one or should I just turn it on all of them now???
thank you for your suggestion. We will think about it. It does not metter, you can have Smart Matches turn on on all of your trees at the same time. It wont cause any problems. Kindly let me know if you need more assistance.
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.