Click on your name in the top right of the MyHeritage screen. Then click on My Sites, then on the site you want to delete. Once there, click on Settings, then on General, then on Administration. Then you can delete that particular site. Do that for each duplicate or for any tree you want to delete.
Please accept my sympathy. I'm afraid I can't help much.
Question 1: "Am I really expected to review 460 matches?"
No. You are welcome to totally ignore useless matches. When you review the matches with someone else's site you should find controls to "confirm all", "reject all" and "ignore this tree". That last one lets you remove a specific family tree from all future smart matches (so you could block those two sites).
I only pay attention to smart matches that I have called for. And few of them have been of any real value or use to me. But that's just my family; your mileage may vary.
Question 2: "I have thousands of duplications within my own imported tree."
Are you using Family Tree Builder? If so, check Tools > Check for Duplicates. This will tell you what you already know, that you have duplicate individuals.
The utility may find 100% duplicates but it may also tell you, for example, that there is a 38% chance that Mary Ferguson b. 1871 and Mary Jane Fergus b. 1940 are duplicates. No, it's not terribly intelligent, and there's no way to teach it to be less stupid (by not showing me anything below 80% likelihood, for example).
For each of those duplicates, however iffy, you are given a choice of ignoring it or.... ignoring it.
Now, an intelligent software developer would have realized that a user will want to merge the data between two duplicate individuals. Exactly as you do for two individuals found via a Smart Match, only for two individuals within your own tree.
Instead, you need to manually check the data for each duplicated person, manually move from one to the other (the "keeper"), fact by fact, note by note, date by date then manually delete the other copy (the "gonner").
To make this nominally easier, you can save the Duplicates report to a file, then print it so that over the course of the next few weeks you can manually keep track of which duplicates you have manually merged and those you haven't yet got around to....
Yes, it's a huge burden. The inability to automatically merge duplicate individuals is an excellent example of asinine programming, and yet another thing I hope the MH developers will get around to fixing.
In the meantime, someone on the support team may have a workaround.
Suggestions you ask>Well I can tell you from 2 years of experience that you have just become the latest to realise their is a problem with duplicated trees.
It get even worse- if you locate the "tree owner"and invite myheritage to chastise him/her or even that they recomend a rationalisation of the trees- they (MH) will refuse your request- and why-- because they will not interfer with the tree publishing and it would bean invasion of THAT tree owener's privacy.
Your objsectivity in wanting to rid the duplicate trees carries no value. This is just a piece of the world that myheritage live in- they have "POLICY"on privacy and intervention- my view change the god dam policy- but not likley.
They revel in the fact that you have got a over stated number of actual smart matches- in the eyes of MY you have a great number of matches abd THAT is waht sells my heritage- you have got 460 matches not 230- so THAT means its good from MH - the user - you are ..just irrelevant and you will be ignored.
Just because a connection(son) is not included on the tree doesn't mean that the actual match should be rejected. No wonder there are so many problems.
?? Not sure what this refers to
Personally, I am getting fed up with the whole Smart Match thing and ignore all of them. They're more nuisance than help.
Did you know that you can turn off Smart Matching in FTB V6 (and probably V7 as well) ? Go to Tools > Options > Smart Matching (tm) and set Auto Match to "No". This will prevent FTB from looking for Smart Matches when you add a new person or edit an existing record. This will speed up FTB considerably.
It won't stop the online version from finding them, though.
It means that all of the information was correct. But a family member was not on the tree, so the match to the person on the tree was rejected by the other person after I had accepted it. In other words John Smith and Joe Smith are father and son. I have John on my tree, but not Joe. I get a match for John, but since my tree also doesn't include Joe, the other person rejects our mutual match for John, even though every detail matches and it's clearly the same person. How is the system supposed to understand what real matches are if people are so silly that way?
...I have John on my tree, but not Joe. I get a match for John, but since my tree also doesn't include Joe, the other person rejects our mutual match for John, even though every detail matches and it's clearly the same person....
Thank you, now I understand. What happens when you confirm and the other site manager rejects the same match? does anything bad happen? For that matter, what happens if you both confirm? Or both reject? Or both ignore?
As far as I can tell, it doesn't make any difference.
I like to check to see if the other tree has data that I lack. If they have a tree that goes back to antiquity but I can't see any proof, evidence, or sources, I leave quickly. If I see notes, sources, etc. that obviously came from my tree, I leave quickly. I used to ask the site manager how they know that John was the father of Joe, but nobody ever replied, or they would say, "I got it from a smart match" so I stopped doing that. No point in perpetuating unsupported links.
Beyond that, I can't see a single benefit to paying any attention at all to Smart Matches. I don't confirm, I don't reject, I just ignore them.
It may not matter in the end, but I think that if more people accept or reject validly, the system will "learn" your tree better and make you less likely to get crazy matches that don't make any sense. That's my theory anyway.
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!