The Ultimate Splitting tool described on Sources – Adventures in Extreme Splitting adds person name(s) and event to the name of the split Master Source, which, in many instances, will be identical to other Master Sources.split from a common lumpy Master Source.Īn example of a small database, starting with lumpy sources: State.Should these sources return to the database through collaboration with another party, SmartMerge will merge the persons but not the sources because of this differing white space. Sources that have outer white space following the Master Source Text or Comments lose that on export or transfer via drag’n’drop.Thus, the same source assigned to two different persons will have different Master Source names. When imported into RootsMagic via its Share Data utility, that becomes the Master Source name. Sources added to a person within FamilySearch Family Tree have their name prefixed by the person’s name.Under what conditions can such practically identical sources arise that RootsMagic’s Source AutoMerge does not recognise them? It is more forgiving than the built-in Source AutoMerge yet does not corrupt the core properties of the final, common Master Sources. there are white space differences around or within Source Text or Comments but the non-blank texts are otherwise identical.The script below offers an external Source AutoMerge that does not mind if: Source Templates – Merge Duplicates addresses the first barrier for Source AutoMerge. Thus it fails to merge sources that are practically identical and that we would wish were merged. The RootsMagic Source List window has an AutoMerge function that can merge Master Sources that are identical in every respect, including the pointer to the Source Template and the name of the Master Source.
0 kommentar(er)
