#64 Some privacy problems


I closed two of Melizas bug reports here to combine
them to one.

We tried to check out the problems of Meliza today and
came to following solutions or better bugs:

We have a showstopper??? Or what was that called?

1. The MyGedView page shows different upcoming
events than the welcome page of the gedcom does.
Don't know if that is wanted but the MygedVoiew page
shows also data of people which it should not do
because of the relationship.

To say it with Melizas words:
The mygedview upcomming events shows all the people
to logged-in users even if they are outside the
relationship path.

2. PGV relationship verification does not handle correctly
IDs that include leading zeroes.

The problem is that Meliza uses a FTM gedcom. FTM
seems to add leading zeros to the ID-Number like
@I001@ S010@ @F03@ etc.

Nearly all routines seemt to work good with leading
zeros but not the relationship chek or the privacy.

Maybe it would be good to eliminate leading zeros in an
indi ID or fam ID or source ID or whatever, always
between two @ signs in the gedcom. This is something
for the import routine. Manually removing those leading
zeroes brings some more privacy. We tested that out!

3. Some tags in a gedcom like the DATA tag which is
the gedcom of Meliza do not seem to work with the
privacy in the timeline chart or the calendar.
Setting in the privacy file is:
$global_facts["DATA"]["show"] = $PRIV_NONE;
$global_facts["DATA"]["details"] = $PRIV_NONE;

This should work in all parts of PGV but doesn't seem to
work in the calendar and the timeline.

Don't know who wrote the calendar but I think the
timeline is part of John. The import is something for
Roland or Jeremy or John.

Meliza and me will answer all questions about these
probs and yopu can also see that on a testsite if you

How many testsites do we have for Meliza at the
moment ;-)


  • Meliza Amity

    Meliza Amity - 2004-03-27

    Logged In: YES

    3. The DATA fact is also a problem in On This Day, ... both in
    the Welcome and in the MyGedView pages.

    It is also included in the clippings cart entries of the person.

    It is also shown in the zoom in of the Name Box of the charts.

    The DATA facts are not shown, as expected on the individual
    details page.

  • Meliza Amity

    Meliza Amity - 2004-03-27

    Logged In: YES

    3. Also a problem in both upcomming events.

  • Phantomas

    Phantomas - 2004-03-28
    • priority: 5 --> 9
  • John Finlay

    John Finlay - 2004-03-29
    • assigned_to: nobody --> yalnifj
  • Meliza Amity

    Meliza Amity - 2004-03-31

    Logged In: YES

    4. I would not show on the Most Common Surnames names of
    live people, if they are not shown on other site pages (for
    instance to visitors).

    See Kurt's site for TestDATA.GED - meliza

  • John Finlay

    John Finlay - 2004-04-06
    • status: open --> open-fixed
  • John Finlay

    John Finlay - 2004-04-06

    Logged In: YES

    These privacy issues have been fixed in the latest CVS.


  • Meliza Amity

    Meliza Amity - 2004-04-06

    Logged In: YES

    Great work!

    2. The Most Common Surenames shows all the Surenames
    (also those of only live indi-s) to visitors although data of live
    people should only be shown to authenticated users.

    3. DATA without a DATE tag is included in the shown Gedcom
    data and in the downloaded Gedcom data.

  • John Finlay

    John Finlay - 2004-04-07

    Logged In: YES

    2. I think that the Common Surnames should include the
    surnames of people who are living. Having the surname listed
    is an essential way for search engines to lead people to your
    site. If someone is looking for a common surname that you
    have on your site, they will be able to find your site and know
    that you have information about that surname on it. Then
    for the information about private people they can contact
    you to find out more. But if the surname were never
    displayed they could never find it out.

    3. The DATA tag is not a valid tag that can be supressed by
    the privacy settings. Only level 1 tags can be supressed. So
    if you want the DATA to be hidden then you have to hide the
    SOUR that it is attached to.


  • Meliza Amity

    Meliza Amity - 2004-04-07

    Logged In: YES

    2. OK

    3. Thanks for your answer.

    I have some facts in FTM that I do not want to show to any
    Have recorded in FTM this data under Fact DATA.
    You state correctly that the level of my DATA fact is 2.
    I do not see the DATA fact in the Individual Page.
    Expected the same handling on the other pages.

    Is it possible to define the DATA fact's source in the privacy
    setting for all the individuals without stating separately the
    Indi ID?

    Added the OCCU fact also to the Global Facts suppression.
    I see the OCCU data in the Indi details' Gedcom data and in
    the Downloaded Gedcom file.

    $global_facts["DATA"]["show"] = $PRIV_NONE;
    $global_facts["DATA"]["details"] = $PRIV_NONE;
    $global_facts["OCCU"]["show"] = $PRIV_NONE;
    $global_facts["OCCU"]["details"] = $PRIV_NONE;

  • Meliza Amity

    Meliza Amity - 2004-04-12

    Logged In: YES

    Have created a RFE for the Gedcom Fact privacy issue.

    This item may be closed.

  • Boudewijn Sjouke

    • status: open-fixed --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks