However I am experiencing some difficulty in getting the filters to do what I want. vis:

1) When one or more partners in a 'union' or marriage are filtered to some extent I want the marriage details also to be filtered. I believe this has been requested elsewhere. There is no 'inheritance' filter from individuals to families so the only way I've found is to select each such family in turn at set an explicit privacy filter. This is time-consuming and error prone and I suggest defeats the object of global filters by requiring manual intervention rather than automatic filtering.

2) I would like some living individuals to appear on the report but unchecking the 'apply privacy profile for living and deceased individual' box seems to have no effect whether or not 'public' is checked or not. I believe Anna reported this.

3) I would like children of a 'filtered' individual, whether they are alive or dead, not to be shown on the family page or SVG map but still be included the child counts for their parents. Currently if living children are filtered by deletion then only dead children are included in their parents count. This results in an untrue statement in the report.

4) If an individuals name has been blanked it is shown as <unknown>. I would prefer a distinction between unknown and filtered. i.e. show as <not disclosed>, <withheld> or <private> etc. In genealogy we strive to stick to the facts, in this case <unknown> is untrue.

I am interested to hear if and how others are using the privacy filters and their views on the above (plus any solutions!)

A 'quick fix' might be to flag individuals and families that have had a filter applied via properties in the Report Generator. Work-arounds could be be coded in the templates.

1. I can only agree. I must admit that I hadn't tried using the privacy filters in detail until now, but having attempted to use them I find them most confusing. If I set the filter to exclude living individuals from the report and the genealogy tree, they are excluded, but all the pedigree and marriage lines, and comments are still there in the SVG tree. There does not seem to be an option to 'exclude pedigree/marriage lines for living individuals'.
2. Agreed
3. Agreed. At the moment you can get the situation where the children of a marriage are living, and the dead parents' marriage reports 'They had no children'.
4. I cannot get a blanked individual to display as <unknown>, but otherwise I fully agree with Ron's point.

On a more general point regarding the privacy filters, some of the descriptions can be misleading. For instance: 'Delete.....' on the Privacy Profiles implies that this property is going to be permanently removed. A better description would be 'Hide' or 'Exclude from Report' or else make clear that the Privacy Filters only apply to the generated report and tree.

The privacy filter is an important feature.  I recognize the current design is complicated to use, and worse, does not work the way I wanted it to work.  I spent several hours with my brother Jean-Claude drafting different architectures of data/privacy filtering.  We concluded we need to re-write this module and include a Wizard to allow the user to create different Privacy Templates.  We want to do a good job on this because the privacy filtering will be used for many purposes, such as exporting to XML, export to Gedcom, export to metafile (EMF), and or course, generating a report.

Since GenoPro 2.0 is already late and we don't want to cut the corners, we will implement this module after releasing version 2.0.  The Privacy tabs (dialogs) will be removed from GenoPro in the next beta...

This is probably the best solution for the present. I believe it would be a mistake to release v2.0 with something that didn't work.

[ ] Delete All Living Individuals
[ ] Delete All Contact Information

The option to delete all living individuals will also removes any family without parents and children.

Using the [ ] Delete All Living Individuals checkbox achieves the required result, but unfortunately the report now states eg 'X and Y were married on (date). They had no children' even when there are living children. The report should state the number of children, but omit the names, or perhaps state 'They had n living children'. I can see problems where some children are living and some dead, and I have noticed a similar problem with siblings. For instance my wife's mother had 7 siblings, only one of whom is alive. The report states: 'She was the oldest of seven children.  She had four brothers and two sisters', and then names the dead siblings. It should state: 'She was the oldest of eight children.  She had four brothers and three sisters'.

Where one spouse is living and one dead, the SVG displays a marriage link with only the dead spouse shown - see below

You will also get odd results where a child of living parents has died.

Is there any simple way to replace the name of a living person with <Living> and to omit all other data on that person from the report, without the complications of the original Privacy Filter?

What is about the following idea: if privacy was set for an object (individual, marriage, etc.) it should be replaced by a 'dummy' entity, like an empty male object (no data, just keep the ID for referencing) in the reports/exports, etc?


Feri

Also a 'Keep year of births' option as well as 'Keep (full) date of births?

Alternatively is there a way to detect such individuals in the template script and then make the changes there?

The bottom line is the privacy filter will be redone.  These options are temporary to offer rudimentary privacy filtering.  I added the option to delete all date of births, to delete the day of birth (keeping year and month of birth), and keeping the full date of birth.

Dan, could you expand on this explanation? If you mean that GenoPro would display <living> or 'Not Disclosed' in the SVG tree as well as in the properties of the individual, then I believe this is exactly what we were suggesting for privacy reasons. However, if you mean that the main .gno or .xml file would be changed, then I understand why it cannot be done.

One problem now with the SVG report is that the marriage label still appears for blanked individuals and clicking on such a link results in a 'page not found' error. Perhaps instead we could have a flag to indicate that the name has been blanked by the privacy filter. The skin template code could then check this an display <living> or 'Not Disclosed' etc. (text determined by a parameter in Config.xml) to distinguish lving people with names witheld from those whose name is just not known. This flag could also be used to supress the marriage label if one or other partner had been blanked by the privacy filter.

Also because the 'privacy fliter' applies to all living indivduals it is not possible to allow the display of selected living individuals. e.g. myself!

I agree.  The new privacy filter will address those issues, including the ability to apply custom privacy filtering on a per-object (individual, family, picture, etc) basis.

At the moment, the privacy options are a temporary workaround until the new privacy filter becomes available.

I have also run the report in 15d with the option of deleting all living individuals, and not keeping names or dates, but in my browser I do not get a 'page not found' error - simply nothing happens when I click on a living individual or their marriage line in the SVG.

However, I notice that, contrary to 15c (as reported above), all living individuals are now shown in the SVG tree (albeit with no names or dates), and are listed as <Unknown> in the report (this ensures that the correct number of children and siblings are reported even when living). This is a big improvement.

As the <Unknown> designation has evidently been coded in the script for the report generator in place of the individuals names, if this is changed to <Living> or 'Not Disclosed' as previously suggested, this would meet the requirements for v2.0 and until the Privacy Filter is available.

If there is no date of birth for a living individual then my code can't distinguish between 'unknown' and 'living' so by default it uses the <Unknown/Living> name tag for these cases. For this reason when using my modified template it is best not to check the option 'delete all date of births' and so avoid <Living> being shown as <Unknown/Living> when the date of birth is not visible to the script. However I have introduced a Report parameter in Config.xml, LivingDoB, that allows you to suppress dates of birth on the report (set param to 'N' or 'None') or allows just the year of birth to be shown (set param to 'Year' or 'Y'). All name tags are in the Dictionary to allow users to change them.

To produce the name tags on the SVG report as well I had to adopt some devious means and it was necessary to introduce some 'template' individuals into the GenoPro file before generating the report so that the size and position of the <Living> and <Unknown/Living> tags could be determined. To prevent these individuals from displaying on the SVG graphic they must be hidden under a blank white text label and moved to the back in the z order so that they slide under other objects. They must also have fixed permanent ids so the code can find them. To simplify this process I have included a Template.ged file in the zip file that contains the necessary 10 'template' individuals covered by a text label at the correct z-order level. This .ged file can be imported into one of your GenoPro file's GenoMaps before generating the report and the inported objects deleted again after the report has been generated. The imported objects should be moved under existing content to avoid affecting the 'zoom to extents' SVG option. To change the name tags used on the SVG report you should change the .ged file before importing.

The 'template' individuals are marked as 'make label/exclude from report' but there is a bug (perhaps) in the Generate Report Privacy tab operation in that names for such individuals are also blanked unless the individual is marked as dead as well. I think 'label' individuals should be excluded from privacy operations.