Technically, she's your aunt but she is outside of your bloodline although she still belongs to the main tree. Let's say you have the wife of you uncle in your tree. That would be more effective than going through thousands of records manually and search for information that is worth to be added to your own tree. It might be permitted to export their GEDCOM files or parts of it so that you can import them into your webtrees installation as an additional tree and have webtrees check the merged tree for duplicates. There are groups of researchers that use webtrees to create separate trees from multiple church books for a specific region and offer this information to their members or even to the public.If at some later point in in time you find the missing link between your tree and that other tree you can merge them. dozens or hundreds of them I would create a second tree for them. These individuals would exist in your tree, but someone walking up and down your tree would never find these individuals. If this is about a few persons only cou could add one of them to your tree as an unlinked undividual and then add his relatives. Create an additional tree when you suspect that one of the individuals in your tree is related to someone with the same name from the same village, but for the time being you have no evidence for that relationship.which you might want to test before you implement them to your productive tree. Create an additional tree to play or experiment with webtrees or to train your co-workers.I can think of several other use cases for maintaining multiple trees in one webtrees installation, e.g. You can of course merge the first tree and the second tree without creating that backup tree, but you cannot import AND merge your cousin's tree in one step. You could then export your own tree and import it again to webtrees as a third (or backup) tree to see what happens when you merge the first and second tree. You would then import his/her tree into webtrees as a second tree and maybe check the details, apply a few corrections so that places, sources, etc. Let's assume the only duplicates are those great-grandparents. Think of a situation where by research you find a second cousin which means you and him/her share the same great-grandparents and that cousin provides you with his/her GEDCOM file. On the other hand merging trees with only a few duplicates can be easy. They might share ~50% of their trees and after merging these trees you would have to manually merge all these duplicates. Think of a brother and a sister both married and having kids and both maintaining their own family trees on different websites. Merging trees can cause intensive work in case you have a lot of duplicates because after merging the trees you will want to merge the duplicates as well.
0 kommentar(er)
