two things I noticed about private (living) individuals -
1. the names of living spouses shows up on a deceased individual's page. I would've thought that would've been hidden as well. I realize if you click on them it will give you a warning that their info is not available but I thought it wouldn't even show their name in the dead spouse's page.
2. if you have a deceased person as the starting person for a pedigree chart, the little left arrow by his/her box will show the names of living spouse and children to navigate to. Again, I would've thought these would be hidden.
Tom
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see the spouse name showing up next to the Marriage information for a dead individual with a living spouse. This is bad. It will be fixed in the next version.
The names showing up in the in the child descendents box on the pedigree chart has already been fixed for the next release.
A beta of the next release should be available next week.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-09-04
It also seems that living people show up in the family list. They are not shown in the individual list, but do in the family list.
Tom
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please could someone explain the
$CHECK_MARRIAGE_RELATIONS = true; //-- check related by marriage relationships concept.
I have set up a user for my cousin. With this set to false he can see my details, but not my husbands. Setting this to true he seems to be able to see all my husband's cousins and nephews etc.
I fact I couldn't find any living relations of my husbands the user could not see.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The $CHECK_MARRIAGE_RELATIONS tells whether the get_relationship function should add the current nodes spouse to the list of people to check.
There is always a path back to the spouse through the children but it takes an extra step to get to them.
Perhaps I should explain the algorithm used to calculate relationships.
There are two people (person1 and person2) and you want to find a path from the one to the other. There can be many paths. Some longer than others. We stop when we find the first one (not guarenteed to be the shortest path though should be pretty close and depends on age).
We use a sorted stack to choose who is the next person to check. As people are added to the stack they are assigned a weight. The person with the lowest weight floats to the top of the stack and he is the one who gets popped off next. So we start by adding person1 to the stack with a weight of 0 and a path-length of 1.
When a person is popped off the stack (let's call them currentP), we first check to see if currentP is the same as person2. If there is a match then we can stop. Then we check to make sure they are not greater than the maximum allowed path length. If they are not then we compare the age of currentP and person2 and assign weight offsets to following the path of the father, mother, sibling, or child.
This is where is gets complex. For example if currentP was born in 1970 and person2 was born in 1930 then it would be smarter to check the parents before the children, spouse, and siblings of currentP. The path to follow children, spouse, and siblings of currentP will get a higher weight offset than the parents so that the parents float to the top.
Once we have calculated the weight offsets, we check the parents. If we haven't allready visited the parents then we add them to the stack with a path-length = 1+currentP's path-length and a weight = currentP's weight + the weight offset we calculated for parents. We then do the same for siblings and children.
Spouses are different because they are only added to the stack if $CHECK_MARRIAGE_RELATIONS is true.
However, it would still be possible to get to the spouse by going through the children but this adds an extra length to the path. If a spouse gets on the stack, then their parents and siblings could also get on the stack. This is where you have to carefully set $MAX_RELATION_PATH_LENGTH.
The default for $MAX_RELATION_PATH_LENGTH = 6 which I have found to be too high. A value of 3 is probably more what you are looking for and will be the default in the next version.
So if you want your cousin to be able to see your husband but not your husband's parents or siblings you could either set $CHECK_MARRIAGE_RELATIONS = true; and set a $MAX_RELATION_PATH_LENGTH = 5;
or you could set $CHECK_MARRIAGE_RELATIONS = false; and $MAX_RELATION_PATH_LENGTH = 6; (assuming you have children the path can follow)
I hope this long explaination helps.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
two things I noticed about private (living) individuals -
1. the names of living spouses shows up on a deceased individual's page. I would've thought that would've been hidden as well. I realize if you click on them it will give you a warning that their info is not available but I thought it wouldn't even show their name in the dead spouse's page.
2. if you have a deceased person as the starting person for a pedigree chart, the little left arrow by his/her box will show the names of living spouse and children to navigate to. Again, I would've thought these would be hidden.
Tom
I see the spouse name showing up next to the Marriage information for a dead individual with a living spouse. This is bad. It will be fixed in the next version.
The names showing up in the in the child descendents box on the pedigree chart has already been fixed for the next release.
A beta of the next release should be available next week.
--John
It also seems that living people show up in the family list. They are not shown in the individual list, but do in the family list.
Tom
I've addressed privacy in the family list in the next version as well.
--John
Please could someone explain the
$CHECK_MARRIAGE_RELATIONS = true; //-- check related by marriage relationships concept.
I have set up a user for my cousin. With this set to false he can see my details, but not my husbands. Setting this to true he seems to be able to see all my husband's cousins and nephews etc.
I fact I couldn't find any living relations of my husbands the user could not see.
The $CHECK_MARRIAGE_RELATIONS tells whether the get_relationship function should add the current nodes spouse to the list of people to check.
There is always a path back to the spouse through the children but it takes an extra step to get to them.
Perhaps I should explain the algorithm used to calculate relationships.
There are two people (person1 and person2) and you want to find a path from the one to the other. There can be many paths. Some longer than others. We stop when we find the first one (not guarenteed to be the shortest path though should be pretty close and depends on age).
We use a sorted stack to choose who is the next person to check. As people are added to the stack they are assigned a weight. The person with the lowest weight floats to the top of the stack and he is the one who gets popped off next. So we start by adding person1 to the stack with a weight of 0 and a path-length of 1.
When a person is popped off the stack (let's call them currentP), we first check to see if currentP is the same as person2. If there is a match then we can stop. Then we check to make sure they are not greater than the maximum allowed path length. If they are not then we compare the age of currentP and person2 and assign weight offsets to following the path of the father, mother, sibling, or child.
This is where is gets complex. For example if currentP was born in 1970 and person2 was born in 1930 then it would be smarter to check the parents before the children, spouse, and siblings of currentP. The path to follow children, spouse, and siblings of currentP will get a higher weight offset than the parents so that the parents float to the top.
Once we have calculated the weight offsets, we check the parents. If we haven't allready visited the parents then we add them to the stack with a path-length = 1+currentP's path-length and a weight = currentP's weight + the weight offset we calculated for parents. We then do the same for siblings and children.
Spouses are different because they are only added to the stack if $CHECK_MARRIAGE_RELATIONS is true.
However, it would still be possible to get to the spouse by going through the children but this adds an extra length to the path. If a spouse gets on the stack, then their parents and siblings could also get on the stack. This is where you have to carefully set $MAX_RELATION_PATH_LENGTH.
The default for $MAX_RELATION_PATH_LENGTH = 6 which I have found to be too high. A value of 3 is probably more what you are looking for and will be the default in the next version.
So if you want your cousin to be able to see your husband but not your husband's parents or siblings you could either set $CHECK_MARRIAGE_RELATIONS = true; and set a $MAX_RELATION_PATH_LENGTH = 5;
or you could set $CHECK_MARRIAGE_RELATIONS = false; and $MAX_RELATION_PATH_LENGTH = 6; (assuming you have children the path can follow)
I hope this long explaination helps.
--John