Like many who publish their trees on this site, I do not use the local version of myHeritage. As I make changes to my home database, I would like to push those change up to my existing online tree without having to add them manually (time consuming) or having to delete and reload a new tree (and lose all my confirmed connections). Your SmartMatching technology could be used to allow one to upload a new GEDCOM file, updating and adding where appropriate. This would be very useful.
Is there a reason that you choose not to publish your tree to your family site?
When you publish your tree, the first time the whole tree is uploaded. Any next time that you publish your tree, the tree that you have on your site is updated, and only the changes are uploaded to your site.
So what you're saying is that If I import again, it only updates what has changed? Deleted people are removed, new people are added, and facts are updated? And confirmed matches are retained, and don't have to be reconfirmed?
If you republish your family tree from Family Tree Builder to your fmaily site ( I am puposefully not using the word upload- since uplaoding a Gedcom file does not replace a previously uploaded Gedcom file), then your tree will be updated exactly as you mentioned. The only thing that will not be updated are smart match rejections. The match will still be marked as pending on the site.
So the answer to my original question is no, if you don't use the local version of myHeritage (FamilyTreeBuilder) and you publish your tree using GEDCOM files, you will lose all your SmartMatches if you load a new GEDCOM.
So back to my original suggestion, that you use your own technology (SmartMatching) to allow sensible replacement of an uploaded GEDCOM with a new one without having to update all the Smart Matches. That is, you match the old gedcom to the new gedcom, and anything that is a strong match inherits the old Smart Matches.
I do see that this is an issue for users that upload Gedcom file trees, and replace them with new uploaded trees.
Since each new uploaded tree is a brand new tree, it will get its own new smart matches, and you will have to confirm or reject them from the beginning.
Please note that in general we do not support this method of working- it is advised that you publish your tree from Family Tree Builder. This will save all the information of the tree, even with each time that you publish it.
Hence my suggestion. SmartMatch could be used to update the online tree using using an uploaded GEDCOM. The SmartMatch technology is quite good, while the FamilyTreeBuilder program itself is not that strong. Your online technology could be agnostic with respect to the source database, which would make it more attractive.
Could you pass this suggestion on to the developers?