This is a snippet of the Source linker? It has been acting very erratic lately, so I think programmers are working on it. And you are seeing some code residue not meant to be seen, at least not yet.
Usually there might be a relationship shown after the name, but not a hyperlink. Looks like in future the relationship may be a hyperlink to a help page. The help page could be language localized.
The hyperlink tries to redirect using https, but fails anyway.
Somewhere there's a lost and lonely node waiting for somebody to find it and lead it back to it's owner.
"Pay no attention to that man behind the curtain."
@LDS Search Test
Can you give us the ID number for Mary Prenton? We would be glad to look at this. What source are you finding this weird notification?
Thank you for contacting FamilySearch.
We are here to help you in any way we can and want your experience with FamilySearch to be a positive one. Best wishes and success in continuing your family history research.
Mary Prenton is LDFX-YXB
Item shown is from Source Linker for England and Wales Census 1881
I had a similar one for a family in the 1920 US census a few days ago.
G82N-SY2 and his family.
I observe in the Family Tree Data Model https://www.familysearch.org/developers/docs/guides/FamilyTree-data-objects that there is no provision for relationships other than Couple and Parent-Child.
This is clearly an ommission. Many sources contain relationships such as Grandfather, Grandmother, Grandson, Granddaughter as well as the Aunt and cousins indicated above. It is reasonable to presume that there will also be an Uncle in a source document somewhere.
We can see the Brother and Sister relationship in Source Linker, so it is clear that it exists. Yet the Data model section for a Person shows only Couple and Child-and-Parents. So it seems that the Data Model needs to be corrected to reflect the additional known working relationships.
At the same time, the sources section of the Data Model can be corrected to add the other extended family relationships.
@LDS Search Test , all other relationships are elaborations of couple and parent-child. And that is why it is sometimes necessary to use a placeholder profile for the person between a known child and grandparent.
It seems to be working OK in this record:
I caught this bug today:
Thank you for posting this. The engineers are working on this but in the mean time try this.
Here is an idea to try (because I like to think like a detective) It appears that Anne Weil is a cousin to Madeline or George and she is living with them in the 1940 census. If you can identify Anne Weil and go to her person page and maybe attach that 1940 census to her maybe that would clear up that weird notification.
Here is a link to some possible Anne Weil's born in New York between 1900 and 1915 https://www.familysearch.org/tree/find/name?self=Anne%7CWeil%7C0%7C0&gender=female&birth=New%20York%7C1900-1915%7C0%7C0
Maybe that will help.
Thank you for contacting FamilySearch. It has been a pleasure helping you. Best wishes as you continue finding records for your family.
@CHold I'm fairly sure that the problem was not about understanding the relationship. Rather, it was why the relationship was presented as (Http://familysearch.org/types/relationships/Cousin?rel=FemaleCousin) instead of simply (Cousin). In my follow up comments to the original posting I wondered whether this was due to change that removed the target of the URL shown. Unless this is escalated to a level that has access to that information we will remain (Http://familysearch.org/types/mindstates/Confused?state=InTheDark)
I have now seen several of these URLs in lieu of label.