How do I link cousins who married on the tree, without having duplicate grandparents show as data pr
The married couple here are cousins:
Their grandparents have duplicate profiles on the tree.
@Kevin De Lange I took a look at the link you included and the grandparents are not duplicated in this situation. I have similar situations in my family. As long as the ID’s for both of them are the same, it is displaying your family as it should be.
Patricia is correct and if you go to the pedigree chart for the Grandfather and change it to display his decendancy, you can see where his grandchildren are married to each other:
The only data problem on the grandparents is that the location where they were married has not been standardized yet0
Thank you for your response Patricia.
It's just that on the displayed graphic, it flags the double set as recurring profiles.
If this is normal, then I can comfortably ignore those flags.0
Thanks for your response Jeff.
Looking at it in descendancy view makes it ok, but it's in portrait pedigree view that the 'recurring person' flag shows...and that's my preferred default view.
Thanks for the reassurance though.
I'll fix the other data problems in short order0
Ok, that's weird. The profile and landscape pedigrees show the "Recurring person" data error but not on the person page. Of course you wouldn't want it on the person page, but I had not seen this before.
It may be new as there is something else weird about it. You can click on the data error mark to get the Data Problems fly-out that looks like this:
But if you actually select the "Show All" button, that Data Problem DISAPPEARS from the list!
Now if you go back to the first image above and click on the "Reoccurring Person" link, you get a fly-out that has a "Dismiss" button on it:
That button was a little flakey as well. I had to click on it 2 or 3 times before it brought up the reason for dismissal page.
I went ahead and Dismissed the inappropriately named "Data Problem" (which really is NOT a "Data Problem") for the grandfather. Even though it is a pedigree type issue, the dismissed item can not be seen as a dismissed item in the pedigree, you have to actually go to the person record itself in order to see it or undo the dismissal:
Looks like a great idea but there are the typical inconsistencies of a new feature in the implementation.
You might want dismiss the Recurring type error on the grandmother as well. I didn't change it.0
Most of your ancestors - are probably already in FamilySearch FamilyTree
you wont need to ADD many of your ancestors - you simply need to LINK to peopel already in the family tree database.
same goes for duplciation in ancstors based on cousin marriages - you would only need to add them once (if they aren't already in FS) and after that - simlply LINK to the record you already added. )
it is one single massive collaborative database we all share (BILLIONS of people)
each person - should (under perfect conditions) only exist in the database ONE time.0
Unfortunately, as Kevin has pointed out and I elaborated on above, when records are correctly recorded as unique entries in the tree, when there is inter-marrying in their descendants, They get flagged with DATA ERRORS in the pedigree views. This seems to be a new function as I've not seen it before.0
I believe this has shown up like this for quite some time - at least I first noticed it early last year, I believe. No, the data warning does not appear on the Person page. In the two instances I have had of this, I have just dismissed the possible data error warning whilst on the Landscape view page.0