Change "View My Relationship" link text to actual relationship.
"View My Relationship" links are very useful. They'd be even more useful if the link text instead gave the actual relationship, eg "Husband of my grandaunt". This would save a lot of clicks (though sometimes I'd still want to click through) and help with remembering older parts of the tree, as I'd see the actual relationship spelled out more often.
Thanks! Wonderful site.
Comments
-
I have heard that they do not write out the relationship in words because of the fact FamilySearch is worldwide and the language translation does not work well. Other cultures or languages do not have the 2 cousins 2x removed to translate correctly so the visual way works for all languages. It has been asked before and this language translation reasoning why it has not happened.
0 -
I have heard that they do not write out the relationship in words because of the fact FamilySearch is worldwide and the language translation does not work well. Other cultures or languages do not have the 2 cousins 2x removed to translate correctly so the visual way works for all languages. It has been asked before and this language translation reasoning why it has not happened.
0 -
This illustrates Cindy's comment fairly well I think:
Notice how some relatives are identified differently depending on whether they are male or female or depending on whether they are older or younger than you!
So in english, the term 1st Cousin could translate to one of at least 4 DIFFERENT relationship names in another language.
:-)
0 -
This illustrates Cindy's comment fairly well I think:
Notice how some relatives are identified differently depending on whether they are male or female or depending on whether they are older or younger than you!
So in english, the term 1st Cousin could translate to one of at least 4 DIFFERENT relationship names in another language.
:-)
0 -
Fair points, but FamilySearch does write out relationships in words, under "Relationship to [name]" after clicking "View my relationship".
1 -
We've been told in the past that it is a matter of processing power. Apparently checking relationships is very processor intensive so the program does not calculate this until the link is clicked. If it were to calculate the relationship every time a profile page is loaded (I have no idea how many tens of thousands of pages per second that is on a busy day), that would unacceptably slow down or even crash the system.
0 -
Where do you think it does not write this out? Here is a screen shot (if it will pass the censors) of the relationship to one of the husbands of one of my grand aunts.
0 -
And since I've told the world tree that I am married, it builds that into my relationship as well. This woman is my father-in-law's step mother.
0 -
What is being requested, as I understand it, is that instead of this:
We see this:
or this:
The question would be whether they could ever overcome the processing power limitation or whether they would continue to develop a feature that cannot be internationalized, even though they have used website language checking for this at least one other place I am aware of which is in messaging other users:
If set to English and I click another user's name I get:
and clicking on the words takes me to the relationship page. But if I am set to Norwegian I just get:
Where I need to actually click ("Vis slektskap" means "Show Relationship") and go to the relationship page where my relationship is shown graphically without any descriptive test:
I might check how I am related to another user like this once every few months so it is only rarely the program needs to make the calculation. If I am working on a family with a lot of merges and clean up to do, I can be changing profile pages every few seconds. Calculating my relationship that often would really burden the system.
2 -
The description of a relationship ("My 4th cousin twice removed" or "The wife of husband's grandfather") does require significant processing power to calculate. And there are many contexts in FamilySearch where the View Relationship button is shown on each item in a list, which multiplies the costs when showing a page with such a list.
As for internationalization, generating those relationship descriptions is more more difficult than simply translating the text. Different languages have entirely different ways of describing relationships. For quite a while, these relationship descriptions were shown only in English; in all other languages, users simply had to rely on the graphical visualization of the relationship. Over time, relationships descriptions became available in Spanish and Portuguese, and more recently in French, German, Italian, Russian, Korean, and Japanese. But I doubt that these descriptions will ever be available in all the languages that FamilySearch supports, especially since multiple new languages are added every year.
2