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?
I wonder what the base for matching is. In the attached picture you can see a match with 70% reliability. The only match is Gender and Last Name (and perhaps No Spouses and No Children). The Birth and Death Dates are far apart.
SmartMatch Settings doesn't provide any parameters affecting the validity of a match.
I would suggest that a user could request match on: First Name (at least partially), Last Name (exact or sounding alike), Birth and Death Date ( Year or exact).
Furthermore I would suggest that it should be possible to exclude matches below a certain percentage (either fixed (80%) - or user specified)
Has there been any progress on this? It seems to me that SmartMatching has become less smart over the past few months.
As other are experiencing I am getting regular matches which have good name agreement - for example I have had several today for Samuel Rudd but the dates are wildly off (200 years), as well as the firstnames of wife, parents and children.
I too recall having the ability to relax/tighten the Smartmatching but can't find the setting now. I was previously satisfied with the default setting but as I said, it is currently considerably time wasting.
I have a backlog of several thousand matches to which I have gradually been inroads - not much chance of making much progress with a slack matching algorhythm.
The only commonalities are the date span and the first name, Elizabeth. Nothing else matches, not surname, not married name, not husband first name, not parents, not siblings, not children etc. !
Sorry, but I have to ask why am I being sent this?
I have over 3,000 SmartMatches in over 500 matching trees. How many of those are of the quality of the above match which tells me that Elizabeth Betts (Morris) is a SmartMatch to Elizabeth Rhodes (Noffsinger) - with matches of that quality (and new ones appearing on a daily basis) I will never get through oall of the SmartMatches I have.
Has the SmartMatch algorhythm been changed recently? I just don't recall having such bad matches in the past.
Good luck on sorting this out. I will send some other examples as I come across them if you like.
Viewing a tree -> Select "Edit Profile" -> Select "Events" -> Select "Add/Edit Events"
I get the possibility to add "Fact Photos". So far so good. But I only get an option to add new photos, but in some situations I would like to reuse already uploaded pictures. e.g. a picture of a church - for Birth, Confirmation, Marriage aso.
If several persons have had their ceremonies in the same church I would end up having a lot off copies of the same picture - when I only need one picture in the Album.
Please implement the option to reuse the same photo. I can be done as it it possible to pinpoint several persons from the same picture - thus relating the same photo to several persons
The Relationship Report is incredibly useful. With over 2,000 people on my tree, it's easy to get lost in the crowd. I just wish it were more readily accessible by having it included in the pop up baloon next to Family Tree, Profile, Photos and Timeline (or in place of Timeline, which I don't use it as often). Bonus points for letting the user choose the shortcuts he'd like to see.
I would like to be able to select where I want the "My Heritage" folder located. By default it is placed in the "My Documents" folder but as I keep all my Family Tree stuff in a separate folder I would like to move the My Heritage folder into it. I can do it now but when I start My Heritage and open my project it immediately creates a new "My Heritage" folder in My Documents.
I also want to be able to set where I want the backups to go. Each time I have to tell My Heritage where I want the back up stored. I have a separate partition for All my backups and then this partition is set to backup to a Removeable drive.
Meetup.com uses them. Pretty slick interface. It will surely help you gauge how much support there really is for each suggestion. And it will certainly free your support team from answering each and every single suggestion.
I propose a "Confidential Field" for each person in the tree which is viewable only by the site administrator. This is the reason: Suppose person A says, "Don't post my birthday on the site." Sometime later, person B says, "I know person A's birthday." Having forgotten what person A told me, I post his birthday and make him mad.
If there was a field attached to him which only I could see, I would put a note saying, "Mr. A doesn't want his birthday posted."