Advanced Person_Privacy settings
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
#146 Advanced Person_Privacy settings
Two things about the $person_privacy settings:
1.
When adding new persons, it would be very nice to be
able to select one person and all his descendants and/or
close relations.
Sometimes a family member wants to be private and the
other members of his family as well.
Saves a lot of work.
The list can be made shorter as well.
Just name the person and one line with "and
descendants"
2.
The list can get rather long.
It would be nice, to have an option to sort the list by ID
or by name.
How about it?
Thnx,
Jans
Logged In: YES
user_id=152229
Umppfff....
That seems to be some work I will have to think about how
to add it.
I think for this I will need to understand how the relationship-
routines work... Jooohhnnn... ;-)
But it could be easier to add the following:
and descendants
and ancestors
Jans, what do you think about this solution?
bye, Kurt
Logged In: YES
user_id=921567
Hi Kurt,
Of course we all like to keep it as simple as possible :-)
But I think it does not make much sence to add the
option "and ancestors".
1. Mostly the ancestors are not not alive anymore and thus
most of the time "not private" (i.e. visable for all).
2. Let's take an example:
I have an aunt, she has a lot of children and so do all of them.
If my aunt wants to remain private and her children as well
(and spouses and their children, and so on), then I just would
have to select my aunt and select the option "and
descendants and family" (that is: if we would have that
option :-)
Logged In: YES
user_id=634811
I think the problem is one of speed/processing time.
in the descendancy tree if a person was private the
descendants would not display. But doing this on the search
results is much more complex. For every match returned by
the search php would have to construct the entire tree of
his ancestors for many generations to see if there was a
private person. This would have to be done for every person
in the indi list etc.
In short it would take forever.
Something similar was requested from John a while ago. That
specifically was that if a person was not private and he had
an ancestor who did not have a death date in the gedcom, the
ancestor still shows up as private. calculating this on the
fly could not eficiently be done.
John, Correct me if I am wrong
Logged In: YES
user_id=921567
Hi KosherJava,
I think there is still a missunderstanding.
I am specific talking about descendants of a certain person.
However, I see what you mean as well.
You mean: you descendants of one person. When you reach
a child, then you take his/her spouse and look for ancestors
again. And so on.
What if we would skip the last step?
If you take the example of my aunt again:
Search for descendants.
Put them in an array and their spouses as well.
Search for more descendants, etc.
Mark all as private.
Later you have to check the results (that's something you are
doing anyway).
If you still see some family members that should be marked as
private, do so by hand (same way as you are doing now).
Maybe the whole routine will not be as complete as it should
be, in this way. But I think it still saves a lot of time.
How about this?
bye,
Jans
Logged In: YES
user_id=634811
What this sounds like is a tool that would do this work once
and add the generated [] to the privacy.php
I guess the same could be done to make ancestors of a
certain person non private.
John?
Logged In: YES
user_id=152229
Hi all...
First I thought it would slow down and make problems and
this really could be.
But in this moment I had the idea that if we add "and
descendants" to the privacy to be private or hidden or
whatever and build the decendancy tree we could stop
building the branch if we find a privacy record which
says "and descendants are privat" by creating a global var
which is unset after the descendancy tree is built but until
finishing we look in the privacy routine for this var and if we
find it set to true the privacy functions can exit with
returning a result that hides all descendants from beeing
shown.
Don't know if this would also work for ancestors...
Yes Jans... That's not what you have meant but maybe later
there may be a reason to implement this and so I will also try
to think about the ancestors ;-)
I don't know if you all really understood what I mean, but I
do ;-)
And so I wrote this down to remember my idea :-)
As I have not a lot of time at this moment I will think about
and try to implement it after saturday.
bye, Kurt
Logged In: YES
user_id=300048
Others have wanted the ability to privatize an entire branch
of the tree to some users in their GEDCOM. So this would
require the ancestors option.
The next thing is that the processing would be extremely
slow because for every person whose descendants you want
to hide, you have to detect if the person you are viewing is a
descendant of that person.
For example, lets say that I want to hide myself and my
children and that I want to hide my brother-in-law and his
children. Everytime I want to list a person, I have to
discover if they are a descendant of me or if they are a
descendant of my brother-in-law. That requires two
relationship calculations. For every other individual whose
descendants you want to hide you add another relationship
calculation.
On descendancy and pedigree charts, you could do
somethings like Kurt suggests, but that doesn't help all of the
other pages.
The only practical way to do this would be to calculate all of
the descendants of a person and add each of them to the
privacy array.
--John
Logged In: YES
user_id=921567
OK John,
I think, with your latest comment, we are back where I
started.
My idea was to make it more simple to add more people to the
privacy list in just one move :-)
If it would take some calculation time, it does not matter,
because at that moment you are in the procedure of adding
people to the privacy list anyway.
Greetings,
Jans