I had been asked, in the Legacy Test mailing list, whether
the Families app for iPhone, iPod Touch, and iPad, supported
the Privacy model for Legacy?

I have done some fairly simple testing of how the Families
app handles Legacy privacy settings.  The testing was done
only on an individual marked "Private" then again on the
same individual marked "Invisible."

To lay some groundwork for my evaluation of how the Families
app handles "private" and "invisible" individuals I re-read
the definitions of "Private" and "Invisible" in the Legacy
Help Index.  In each case the Legacy Help Index stated that
marking an individual as either "Private" or "Invisible"
effected only how that individual was dealt with in Reports
or Web Pages.

The Families app does not produce reports, or web pages, and
is intended only as a portable means of carrying Legacy data
on an iPhone/iPod Touch/iPad.  Although the Families app can
display what it terms an "Individual" screen for a person,
and allows editing of the data presented on that screen,
Privacy Settings are not presented, nor editable.  Therefore
my only concern with privacy issues in relation to the
Families app was whether individuals marked as either
"Private" or "Invisible" within Legacy retained that status
when data was passed to the Families app, then back to
Legacy.  I checked that status both in the Privacy Settings
for the test individual, and within Reports and Web Pages
created from data that had been passed to the Families app,
then back to Legacy.

Before marking anyone as either "Private" or "Invisible" I
first exported the test database to Families and checked
that the individual chosen for testing was visible.  I also
checked that the test individual was marked as "Not Private"
in Legacy, and that they appeared normally on Reports, and
in Web Pages.  Once that baseline was established I did the
following tests:

*INDIVIDUAL MARKED "PRIVATE"*

1.  Opened a database in Legacy, selected an individual,
opened their Individual Information window, clicked on
Privacy Settings and selected "Private."

2.  Closed the Individual Information window, opened a
Family Report that would include that individual I had
marked as "Private," and viewed the report.  I confirmed
that person was presented as "Private (details suppressed
for this person)", though their parents were included, as
well as their spouse and children.

3.  Produced a Web Page that would include the test
individual.  Confirmed that the test individual appeared
only as "Private" on the Web Page, and did not appear on any
list of individuals.

4.  Synced the test database to the Families app and
confirmed that the test individual appeared in the database.

5.  Synced the test database back to Legacy under a
different file name from the original test database, and
confirmed that the test individual was still marked as
"Private."

6.  Produced a Family Report, confirmed that the test
individual appeared on that report as "Private (details
suppressed for this person)".  Also confirmed that the test
individual appeared only as "Private" on the Web Page, and
did not appear on any list of individuals.

*INDIVIDUAL MARKED "INVISIBLE"*

1.  Opened a database in Legacy, selected an individual,
opened their Individual Information window, clicked on
Privacy Settings and selected "Invisible."

2.  Closed the Individual Information window, opened a
Family Report that would include that individual I had
marked as "Invisible," and viewed the report.  I confirmed
that person was not shown in any way, though their spouse
and children were displayed.

3.  Produced a Web Page that would include the test
individual.  Confirmed that the test individual did not
appear on the Web Page.  As the individual selected for the
test happened to be the primary person for whom the Web Page
was created, there was no pedigree chart available on this
Web Page.

4.  Synced the test database to the Families app and
confirmed that the test individual appeared in the database.

5.  Synced the test database back to Legacy under a
different file name from the original test database, and
confirmed that the test individual was still marked as
"Invisible."

6.  Produced a Family Report, confirmed that the test
individual did not appear on that report.  Also confirmed
that the test individual did not appear on a Web Page
created from the newly synced database.

It is my opinion that the Families app supports the privacy
model from Legacy.

JohnZ
Mesa, AZ



Legacy User Group guidelines:

   http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

   http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

   http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp

To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp


Reply via email to