[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
paf-digest V1998 #60
paf-digest Tuesday, October 27 1998 Volume 1998 : Number 060
In this issue:
[none]
[PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
Re: [PAF] Non-member submission ...
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
Re: [PAF] More on; Family History Training Broadcast
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
[PAF] Re: Family History Training Broadcast
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
Re: [PAF] Non-member submission ...
Re: [PAF] More on; Family History Training Broadcast
[PAF] RE: TEMPLE READY HELP
See the end of the digest for information on subscribing to the PAF
or PAF-Digest mailing lists and on how to retrieve back issues.
----------------------------------------------------------------------
Date: Sun, 25 Oct 1998 08:44:34 -0800
From: rhaldy@juno.com (Richard L Halliday)
Subject: [none]
Friends on the PAF and Samuel-L lists;
These last two weeks, at the request of another agency, I have
been testing several genealogical programs as sources for TempleReady.
Since several of you work in Family History Centers, I am including a
summary of the results in the hope that it will help you when patrons try
to run TempleReady and encounter problems. I have tried to remain
impartial and to use neutral language as I do not want to offend anyone.
If I do offend, please accept my apology.
The four programs were not tested extensively. However, using
each one of them produced a distinctly different impression and some
differences were noted. Those impressions and differences are the source
of the following comments.
Due to the circumstances of the testing, no effort was made to
test PAF 3.0 except as a source of GEDCOM files. PAF 3.0 can produce a
GEDCOM file version 4.x or version 5.0. Unfortunately, the designers of
the program chose not to properly label those selections. Instead, they
offer the options to produce a GEDCOM file for PAF 3.0 or PAF 2.1 . . .
2.31. It is the PAF 3.0 choice which produces a GEDCOM ver 5.5 file and
the PAF 2.1 . . . 2.31 choice which produces the older GEDCOM ver 4.x
file. It is the GEDCOM version 5.5 file specification which accommodates
diacritics and sources.
Richard L. Halliday
rhaldy@juno.com
OBJECTIVE: Run TempleReady using GEDCOM files from PAF 3.0, Family
Origins 6.0, Family Tree Maker 5.0, Legacy 2.0 and The Master Genealogist
3.6a.
SUMMARY: Two GEDCOM files, versions 5.5 and 4.x, were generated by PAF
3.0 from a database which was previously used as a source for a PAF
Qualified GEDCOM file. This database consisted of two generations; a
total of 21 individuals and three marriages. The Notes and Sources were
deliberately omitted to reduce the possibility of problems. These files
were imported into the four genealogical programs listed above. A GEDCOM
file was generated by each of those programs, using the LDS options where
they were available.
After running these tests, I have concluded that The Master
Genealogist ver 3.6a and Family Tree Maker ver 5.0 are not suitable for
LDS genealogists who want to have the temple ordinance work performed for
them. Neither Legacy 2.0 nor Family Origins 6.0 appeared to offer the
full needed range of options for selecting Individuals, Couples or
Families which PAF offers.
All five of these programs claimed to produce a TempleReady
compatible GEDCOM file. All except Family Origins offered the option of
an ANSEL character set. It is the ANSEL character set which allows
GEDCOM ver 5.5 files to contain the diacritics used by most European
languages. The ASCII (American Standard Code for Information
Interchange) character set is a subset of ANSEL.
Family Tree Maker, a heavily promoted genealogical program, while
easy to use does not have a specific field for christening. This is a
particularly serious defect as the baptism of an infant is the primary
record of his origin in the centuries prior to the Twentieth.
Although the programmers of The Master Genealogist apparently
tried to accommodate the needs of an LDS researcher, they do not appear
to fully understand the different ordinances. Further, while the program
claims to accept GEDCOM files in versions 4.0 and 5.5, it did not work on
a simple GEDCOM 5.5 file. It did produce a three page report of
"problems" encountered by it. The Master Genealogist while very
versatile, is not easy to use.
Family Origins 6.0 successfully read the GEDCOM ver 5.5 file and
produced a GEDCOM file for TempleReady.
Family Tree Maker 5.0 successfully read the GEDCOM ver 5.5 file
and produces a GEDCOM file for TempleReady.
Legacy 2.0 successfully read the GEDCOM ver 5.5 file and produced
a GEDCOM file for TempleReady. It also put "Submitted 22 Oct 1998" in
the appropriate ordinance fields for each individual; marriage fields
were not checked.
The Master Genealogist 3.6a did not successfully read the GEDCOM
ver 5.5 file. Its effort to do so did produce a three page report of
"Unknown level 2 tag (skipped)". The offending tags listed were GIVN,
SURN, and PEDI. It also did not recognize USA in the address of the
submitter. It complained about the missing level 2 tag "TIME", which was
followed by a time (hh:mm:ss). The Master Genealogist 3.6a was
successful in importing a GEDCOM 4.x version of the same data. It then
produced a GEDCOM file for TempleReady.
The Master Genealogist is a very complex program. It offers more
options than any of the other programs tested. The fields to be used for
a particular database can be selected from a long list. This program is
not easy to use; some of the choices are confusing. For example, it
offers a field for Sealed to Child and another one for Sealed to Parent.
A summary of the test results of the subject programs follows.
PAF 3.0 produced a GEDCOM ver 5.5 file which was correctly
processed by TempleReady. As I expected from previous experience with
this particular database, TempleReady found the records of two previously
performed ordinances. A detailed examination of the TempleReady Report
and a cursory examination of the TempleReady submission file disclosed no
problems.
Family Origins 6.0. generated a "TempleReady" GEDCOM file which
was run through TempleReady v2.41. The resulting report was compared to
one produced 5 May 1998 by PAF 3.0 and TempleReady. The results appeared
to be correct in all respects. A cursory examination of the submission
file disclosed no problems.
Family Tree Maker 5.0. was used to generate a "TempleReady"
GEDCOM file which was run through TempleReady v2.41. TempleReady crashed
and reported the following error in the GEDCOM file. "Error 4937. An
individual or family pointer does not match. Record number: with
pointer: SUBM in path SUBM". This was under Windows 95. No other
program was running at this time.
Legacy 2.0 was used to generate a "TempleReady" GEDCOM file which
was run through TempleReady v2.41. The resulting report was compared to
one produced 5 May 1998 by PAF 3.0 and TempleReady. The results appeared
to be correct in all respects. A cursory examination of the submission
file disclosed no problems. Legacy 2.0 was the only program tested which
offered the option of inserting the caption "Submitted" followed by the
date in the ordinance fields. After the GEDCOM file was made, a few
ordinance fields in the database were checked. "Submitted 22 Oct 1998"
had been entered in them.
The Master Genealogist ver 3.6a was used to try to import a
GEDCOM version 5.5 file. It could not handle that file even though it
specifically listed version 5.5 as an option. When the GEDCOM ver 4.x
file was used, the importation appeared to be successful. TMG was then
used to generate a "TempleReady" GEDCOM file which was run through
TempleReady v2.41. The results were correct except that the submitter
from the original database was included as the child in a family (Family
1). This problem was detected while running TempleReady. I was unable
to use the TempleReady editor to delete this individual. I was able to
exclude the spurious individual by submitting only Families 2, 3, & 4.
The resulting report was compared to one produced 5 May 1998 by PAF 3.0
and TempleReady. The results were correct. A cursory examination of the
submission GEDCOM file disclosed no problems.
Richard L. Halliday
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 22:30:18 +0200
From: Ed Rogers <zulander@netsonic.fi>
Subject: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
This is a multi-part message in MIME format.
- --------------47D48FB1C7F4DDC49EC8C707
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
- --
,/%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%\,
$ Ed "Pooka/Zulander" Rogers $
#( http://www.netsonic.fi/~zulander/ )#
#( Learning Revolutionist & Internet Specialist )#
$ ed.rogers@bigfoot.com ICQ: #1087909 $
`\%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%$@#%/'
- --------------47D48FB1C7F4DDC49EC8C707
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <paf-owner@rehtori.kasanen.fi>
Received: from rehtori.kasanen.fi (majordomo@rehtori.kasanen.fi [193.65.180.248])
by nalle.netsonic.fi (8.8.7/8.8.7) with ESMTP id HAA11299
for <zulander@netsonic.fi>; Mon, 5 Oct 1998 07:13:01 +0300
Received: (from majordomo@localhost)
by rehtori.kasanen.fi (8.8.6/8.8.6) id GAA22627;
Mon, 5 Oct 1998 06:56:37 +0200
Date: Mon, 5 Oct 1998 06:56:37 +0200
From: paf@rehtori.kasanen.fi
Message-Id: <199810050456.GAA22627@rehtori.kasanen.fi>
To: owner-paf@rehtori.kasanen.fi
Subject: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]
>From paf-owner@rehtori.kasanen.fi Mon Oct 5 06:56:34 1998
Received: from virtual.netsonic.fi (root@virtual.netsonic.fi [195.10.151.6])
by rehtori.kasanen.fi (8.8.6/8.8.6) with ESMTP id GAA22624
for <paf@rehtori.kasanen.fi>; Mon, 5 Oct 1998 06:56:33 +0200
Received: from mars.netusa1.net (mars.netusa1.net [205.139.170.12])
by virtual.netsonic.fi (8.8.5/8.8.5) with ESMTP id HAA06477
for <paf@innernet.org>; Mon, 5 Oct 1998 07:12:55 +0300
Received: from bbrindle (kok-04-78.netusa1.net [206.150.220.78])
by mars.netusa1.net (8.8.8/8.8.8) with SMTP id XAA27952
for <paf@innernet.org>; Sun, 4 Oct 1998 23:00:32 -0500 (EST)
Message-ID: <003e01bdf013$f99e7c00$4edc96ce@bbrindle>
From: "Bruce and Regine" <bbrindle@netusa1.net>
To: <paf@innernet.org>
Subject: Does anybody know?
Date: Sun, 4 Oct 1998 22:55:17 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_003B_01BDEFEA.0E3238C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
This is a multi-part message in MIME format.
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi!
Does anybody know if it is possible to go from Family Tree Maker to =
Temple Ready?
How does one prepare names for Temple work from Family Tree Maker?
I had to go ahead and tell the patron to re-enter her data on PAF.
Is there another way?
Regine
Peru, IN
bbrindle@netusa1.net or tchantches@mailexcite.com
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi!</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>Does anybody know if it is possible =
to go from=20
Family Tree Maker to Temple Ready?</FONT></DIV>
<DIV><FONT size=3D2>How does one prepare names for Temple work from =
Family Tree=20
Maker?</FONT></DIV>
<DIV><FONT size=3D2>I had to go ahead and tell the patron to re-enter =
her data on=20
PAF.</FONT></DIV>
<DIV><FONT size=3D2>Is there another way?</FONT></DIV>
<DIV><FONT size=3D2>Regine</FONT></DIV>
<DIV><FONT size=3D2>Peru, IN</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"mailto:bbrindle@netusa1.net">bbrindle@netusa1.net</A> or =
<A=20
href=3D"mailto:tchantches@mailexcite.com">tchantches@mailexcite.com</A></=
FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV></BODY></HTML>
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0--
- --------------47D48FB1C7F4DDC49EC8C707--
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 18:08:10 -0500
From: "w m mahan" <wmmahan@comsys.net>
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
I think that any GED file will run in Temple ready. I would try it. If
not GED com the information to the Paf program and go from there. But the
GED file should run. The old 2.31 PAF GED files will run Diana In
Indiana
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 18:58:56 EST
From: Ltbcad02@aol.com
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
In a message dated 10/25/1998 02:30:03 PM Central Standard Time,
zulander@netsonic.fi writes:
<< Hi!
Does anybody know if it is possible to go from Family Tree Maker to =
Temple Ready?
How does one prepare names for Temple work from Family Tree Maker?
I had to go ahead and tell the patron to reenter her data on PAF.
Is there another way?
Regine
Peru, IN
bbrindle@netusa1.net or tchantches@mailexcite.com
>>
The Church requests that no Temple Submissions should be made without
proxies. This would then not advise Temple Submission by nonmembers.
The Church requests that such submissions be made instead to Ancestral
File.
That being said, it is possible to export records from Family Tree Maker to
PAF. Once in PAF, you will need to edit the locality fields (Almost always)
before you create a Temple Submission or and Ancestral File Submission.
But it is not necessary to reenter the data. Do not have them include. The
Fact fields will not transfer. So when importing, do not have error messages
written to the note fields unless you want to do the excess note edits or not
include the notes when you make the submission. I find that it is better to
let it write the errors to the *.LST.
Hope this helps.
Donna in Corpus Christi
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 18:36:18 -0700
From: Peter Van Schaik <peter.van.schaik@T8000.com>
Subject: Re: [PAF] Non-member submission ...
>The Church requests that no Temple Submissions should be made without
>proxies. This would then not advise Temple Submission by nonmembers.
>The Church requests that such submissions be made instead to Ancestral
>File.
Sorry to disagree on this point; Any one can submit names to the general
temple file if they desire to do so. As long as they follow the steps and
rules outlined in the temple ready program.
It is correct that no nonmembers should submit names to the temple family
file without having some family members or friends whom are members do the
work (be the proxies).
Groetjes from...............Peter!!!!!!
Genealogy: First a commandment, then a curiosity, then an interest,
then an addiction"
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 20:52:38 -0500 (EST)
From: Cheryl Singhal <csinghal@CapAccess.org>
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
- --------------47D48FB1C7F4DDC49EC8C707
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-ID: <Pine.SUN.3.91-FP.981025204644.12386C@cap1.capaccess.org>
On Sun, 25 Oct 1998, Ed Rogers wrote:
RE getting to Temple Ready from FTM:
This will sound harsh and hard-hearted, but facts are facts and this
particular one impacts the issue: If your patron isn't fully competent
and hasn't yet read the manual for FTM re-entering the data in PAF is the
only way to fly.
If, however, your patron has a clue, and HAS read the manual, he/she
simply SELECTS the persons to include in the GEDCOM and saves the GEDCOM
as a GED 4.0 file -- All they have to do is pick the right choice off the
menu. (I have been the unhappy recipient of roughly 8 GEDCOMs from FTM
users who seem unable to do this, however, so I don't hold out much hope.)
Once they've got the GEDCOM, Temple Ready can read it.
Now, the issue of whether FTM will mark these persons as submitted is not
part of the scope of this reply. I don't remember what Richard Nowlin
just said about that. (g)
Temple Ready cannot/willnot read a file with an .FTW or .FTM extension.
The user has to read the instructions to create a .GED file.
Yet another reason I like PAF.
Cheryl
- --------------47D48FB1C7F4DDC49EC8C707
Content-Type: MESSAGE/RFC822
Content-ID: <Pine.SUN.3.91-FP.981025204644.12386D@cap1.capaccess.org>
Return-Path: <paf-owner@rehtori.kasanen.fi>
Received: from rehtori.kasanen.fi (majordomo@rehtori.kasanen.fi [193.65.180.248])
by nalle.netsonic.fi (8.8.7/8.8.7) with ESMTP id HAA11299
for <zulander@netsonic.fi>; Mon, 5 Oct 1998 07:13:01 +0300
Received: (from majordomo@localhost)
by rehtori.kasanen.fi (8.8.6/8.8.6) id GAA22627;
Mon, 5 Oct 1998 06:56:37 +0200
Date: Mon, 5 Oct 1998 06:56:37 +0200
From: paf@rehtori.kasanen.fi
Message-Id: <199810050456.GAA22627@rehtori.kasanen.fi>
To: owner-paf@rehtori.kasanen.fi
Subject: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]
>From paf-owner@rehtori.kasanen.fi Mon Oct 5 06:56:34 1998
Received: from virtual.netsonic.fi (root@virtual.netsonic.fi [195.10.151.6])
by rehtori.kasanen.fi (8.8.6/8.8.6) with ESMTP id GAA22624
for <paf@rehtori.kasanen.fi>; Mon, 5 Oct 1998 06:56:33 +0200
Received: from mars.netusa1.net (mars.netusa1.net [205.139.170.12])
by virtual.netsonic.fi (8.8.5/8.8.5) with ESMTP id HAA06477
for <paf@innernet.org>; Mon, 5 Oct 1998 07:12:55 +0300
Received: from bbrindle (kok-04-78.netusa1.net [206.150.220.78])
by mars.netusa1.net (8.8.8/8.8.8) with SMTP id XAA27952
for <paf@innernet.org>; Sun, 4 Oct 1998 23:00:32 -0500 (EST)
Message-ID: <003e01bdf013$f99e7c00$4edc96ce@bbrindle>
From: "Bruce and Regine" <bbrindle@netusa1.net>
To: <paf@innernet.org>
Subject: Does anybody know?
Date: Sun, 4 Oct 1998 22:55:17 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_003B_01BDEFEA.0E3238C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
This is a multi-part message in MIME format.
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi!
Does anybody know if it is possible to go from Family Tree Maker to =
Temple Ready?
How does one prepare names for Temple work from Family Tree Maker?
I had to go ahead and tell the patron to re-enter her data on PAF.
Is there another way?
Regine
Peru, IN
bbrindle@netusa1.net or tchantches@mailexcite.com
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi!</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>Does anybody know if it is possible =
to go from=20
Family Tree Maker to Temple Ready?</FONT></DIV>
<DIV><FONT size=3D2>How does one prepare names for Temple work from =
Family Tree=20
Maker?</FONT></DIV>
<DIV><FONT size=3D2>I had to go ahead and tell the patron to re-enter =
her data on=20
PAF.</FONT></DIV>
<DIV><FONT size=3D2>Is there another way?</FONT></DIV>
<DIV><FONT size=3D2>Regine</FONT></DIV>
<DIV><FONT size=3D2>Peru, IN</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"mailto:bbrindle@netusa1.net">bbrindle@netusa1.net</A> or =
<A=20
href=3D"mailto:tchantches@mailexcite.com">tchantches@mailexcite.com</A></=
FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV></BODY></HTML>
- ------=_NextPart_000_003B_01BDEFEA.0E3238C0--
- --------------47D48FB1C7F4DDC49EC8C707--
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 18:51:07 +0000
From: "Alice Harris" <akh@molalla.net>
Subject: Re: [PAF] More on; Family History Training Broadcast
Do you know if this will be a tv or a radio broadcast?
> For all that ask for more info on this broadcast, ie. who is allowed to
> attend?
> This is from the FHC memorandum for september;
>
> Family History Training Broadcast
> On Sunday, 8 November 1998, the church will broadcast a family history
> training program at 6.00 P.M. and again at 8.00 P.M. mountain standard
> time (MST).
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 23:50:26 EST
From: TQME2@aol.com
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
One other related action should be considered when going from any genealogy
program, other than PAF (2.31 or 3.0M), to TempleReady. The action is that
the Temple Names Preparation feature in PAF 2.31 or Preparing Names for
TempleReady in PAF 3.0M should be used as a second screening of the data prior
to using TempleReady. The data file used as input to TempleReady then comes
from PAF. That means whatever non-PAF genealogy program one uses, you should
also have and use a copy of PAF and use a GEDCOM file of the data intended for
TempleReady for input to PAF. This promotes greater accuracy for the work
going to the temple and is a double check on exactly what the submitter wants
to have happen. However, occasionally there may be some data problems
stemming from the various GEDCOM versions. PAF 2.31 will ignore some data in
GEDCOM files which have been made using GEDCOM versions above 4.0.
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 22:02:54 -0700
From: Peter Van Schaik <peter.van.schaik@T8000.com>
Subject: [PAF] Re: Family History Training Broadcast
At 06:51 PM 10/25/98 +0000, you wrote:
>Do you know if this will be a tv or a radio broadcast?
Family History Training Broadcast
On Sunday, 8 November 1998, the church will broadcast a family history
training program at 6.00 P.M. and again at 8.00 P.M. mountain standard
time (MST).
The program will be broadcast through the church's satelite system.
Among those invited to attend the broadcast are ;
- -Family History Center directors and staff.
- -Stake and Ward family history consultants.
- -Family records extraction directors and staff.
- -Missionaries with family history assignments.
- -AND ALL OTHER INTERESTED PERSONS!!!!!
(Capital letters and ! marks and below comment added by yours truly)
Make sure you contact your stake people ,so they can do the necessary
preparations to receive this broadcast.
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 25 Oct 1998 21:01:27 -0800
From: Velda Welton <wv001@csufresno.edu>
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ...
>The Church requests that no Temple Submissions should be made without
>proxies. This would then not advise Temple Submission by nonmembers.
>The Church requests that such submissions be made instead to Ancestral
>File.
What does this mean? Non-members frequently submit to the IGI by way of
TempleReady. Is this any different than extracting names from public
records that end in the IGI.
In most of the discussions I feel like there is confusion between a Family
Name file and a Temple file and frequently there is confusion between
submitting an Ancestral file and a Temple file.
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Mon, 26 Oct 1998 08:08:28 -0800
From: rhaldy@juno.com (Richard L Halliday)
Subject: Re: [PAF] [Fwd: BOUNCE paf@rehtori.kasanen.fi: Non-member submission from ["Bruce and Regine" <bbrindle@netusa1.net>]]
On Sun, 25 Oct 1998 18:08:10 -0500 "w m mahan" <wmmahan@comsys.net>
writes:
>I think that any GED file will run in Temple ready. I would try it. If
not GED com the information to the Paf program and go from there. But
the GED file should run. The old 2.31 PAF GED files will run Diana In
>Indiana
Unfortunately, not all GEDCOM files are the same. Not only are there
several different GEDCOM file formats, but some genealogy programs
produce GEDCOM files with faults in them and some use non-standard tags.
In particular I have just had problems with GEDCOM files which
TempleReady had trouble with. A summary report follows:
From: rhaldy@juno.com (Richard L Halliday)
Friends on the PAF and Elijah-L lists;
These last two weeks I have been testing several genealogical
programs as sources for TempleReady. Since several of you work in Family
History Centers, I am including a summary of the results in the hope that
it will help you when patrons try to run TempleReady and encounter
problems. I have tried to remain impartial and to use neutral language
as I do not want to offend anyone. If I do offend, please accept my
apology.
The four subject programs were not tested extensively. However,
using each one of them produced a distinctly different impression and
some differences were noted. Those impressions and differences are the
source of the following comments.
Due to the circumstances of the testing, no effort was made to
test PAF 3.0 except as a source of GEDCOM files. PAF 3.0 can produce a
GEDCOM file version 4.x or version 5.0. Unfortunately, the designers of
the program chose not to properly label those selections. Instead, they
offer the options to produce a GEDCOM file for PAF 3.0 or PAF 2.1 . . .
2.31. It is the PAF 3.0 choice which produces a GEDCOM ver 5.5 file and
the PAF 2.1 . . . 2.31 choice which produces the older GEDCOM ver 4.x
file. It is the GEDCOM version 5.5 file specification which accommodates
diacritics and sources.
Richard L. Halliday
rhaldy@juno.com
OBJECTIVE: Run TempleReady using GEDCOM files from PAF 3.0, Family
Origins 6.0, Family Tree Maker 5.0, Legacy 2.0 and The Master Genealogist
3.6a.
SUMMARY: Two GEDCOM files, versions 5.5 and 4.x, were generated by PAF
3.0 from a database which was previously used as a source for a PAF
Qualified GEDCOM file. This database consisted of two generations; a
total of 21 individuals and three marriages. The Notes and Sources were
deliberately omitted to reduce the possibility of problems. These files
were imported into the four genealogical programs listed above. A GEDCOM
file was generated by each of those programs, using the LDS options where
they were available.
After running these tests, I have concluded that The Master
Genealogist ver 3.6a and Family Tree Maker ver 5.0 are not suitable for
LDS genealogists who want to have the temple ordinance work performed for
them. Neither Legacy 2.0 nor Family Origins 6.0 appeared to offer the
full needed range of options for selecting Individuals, Couples or
Families which PAF offers.
All five of these programs claimed to produce a TempleReady
compatible GEDCOM file. All except Family Origins offered the option of
an ANSEL character set. It is the ANSEL character set which allows
GEDCOM ver 5.5 files to contain the diacritics used by most European
languages. The ASCII (American Standard Code for Information
Interchange) character set is a subset of ANSEL.
Family Tree Maker, a heavily promoted genealogical program, while
easy to use does not have a specific field for christening. This is a
particularly serious defect as the baptism of an infant is the primary
record of his origin in the centuries prior to the Twentieth.
Although the programmers of The Master Genealogist apparently
tried to accommodate the needs of an LDS researcher, they do not appear
to fully understand the different ordinances. Further, while the program
claims to accept GEDCOM files in versions 4.0 and 5.5, it did not work on
a simple GEDCOM 5.5 file. It did produce a three page report of
"problems" encountered by it. The Master Genealogist while very
versatile, is not easy to use.
Family Origins 6.0 successfully read the GEDCOM ver 5.5 file and
produced a GEDCOM file for TempleReady.
Family Tree Maker 5.0 successfully read the GEDCOM ver 5.5 file
and produces a GEDCOM file for TempleReady.
Legacy 2.0 successfully read the GEDCOM ver 5.5 file and produced
a GEDCOM file for TempleReady. It also put "Submitted 22 Oct 1998" in
the appropriate ordinance fields for each individual; marriage fields
were not checked.
The Master Genealogist 3.6a did not successfully read the GEDCOM
ver 5.5 file. Its effort to do so did produce a three page report of
"Unknown level 2 tag (skipped)". The offending tags listed were GIVN,
SURN, and PEDI. It also did not recognize USA in the address of the
submitter. It complained about the missing level 2 tag "TIME", which was
followed by a time (hh:mm:ss). The Master Genealogist 3.6a was
successful in importing a GEDCOM 4.x version of the same data. It then
produced a GEDCOM file for TempleReady.
The Master Genealogist is a very complex program. It offers more
options than any of the other programs tested. The fields to be used for
a particular database can be selected from a long list. This program is
not easy to use; some of the choices are confusing. For example, it
offers a field for Sealed to Child and another one for Sealed to Parent.
A summary of the test results of the subject programs follows.
PAF 3.0 produced a GEDCOM ver 5.5 file which was correctly
processed by TempleReady. As I expected from previous experience with
this particular database, TempleReady found the records of two previously
performed ordinances. A detailed examination of the TempleReady Report
and a cursory examination of the TempleReady submission file disclosed no
problems.
Family Origins 6.0. generated a "TempleReady" GEDCOM file which
was run through TempleReady v2.41. The resulting report was compared to
one produced 5 May 1998 by PAF 3.0 and TempleReady. The results appeared
to be correct in all respects. A cursory examination of the submission
file disclosed no problems.
Family Tree Maker 5.0. was used to generate a "TempleReady"
GEDCOM file which was run through TempleReady v2.41. TempleReady crashed
and reported the following error in the GEDCOM file. "Error 4937. An
individual or family pointer does not match. Record number: with
pointer: SUBM in path SUBM". This was under Windows 95. No other
program was running at this time.
Legacy 2.0 was used to generate a "TempleReady" GEDCOM file which
was run through TempleReady v2.41. The resulting report was compared to
one produced 5 May 1998 by PAF 3.0 and TempleReady. The results appeared
to be correct in all respects. A cursory examination of the submission
file disclosed no problems. Legacy 2.0 was the only program tested which
offered the option of inserting the caption "Submitted" followed by the
date in the ordinance fields. After the GEDCOM file was made, a few
ordinance fields in the database were checked. "Submitted 22 Oct 1998"
had been entered in them.
The Master Genealogist ver 3.6a was used to try to import a
GEDCOM version 5.5 file. It could not handle that file even though it
specifically listed version 5.5 as an option. When the GEDCOM ver 4.x
file was used, the importation appeared to be successful. TMG was then
used to generate a "TempleReady" GEDCOM file which was run through
TempleReady v2.41. The results were correct except that the submitter
from the original database was included as the child in a family (Family
1). This problem was detected while running TempleReady. I was unable
to use the TempleReady editor to delete this individual. I was able to
exclude the spurious individual by submitting only Families 2, 3, & 4.
The resulting report was compared to one produced 5 May 1998 by PAF 3.0
and TempleReady. The results were correct. A cursory examination of the
submission GEDCOM file disclosed no problms.
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Mon, 26 Oct 1998 19:19:20 EST
From: aaberg3@juno.com (Robert M Aaberg)
Subject: Re: [PAF] Non-member submission ...
May I add this info to the msg below. I a member and former FHC
Director, made a very recent disk which I sent to the temple to have
added to my family file. They have a new rule--no more on file family
files. Cards are made and the members must take them with them. This
way they get rid of all the sorting and filing. You take with you what
ordinances that you want to get done, or you can send them with another
member to do.
On Sun, 25 Oct 1998 18:36:18 -0700 Peter Van Schaik
<peter.van.schaik@T8000.com> writes:
>>The Church requests that no Temple Submissions should be made without
>>proxies. This would then not advise Temple Submission by nonmembers.
>>The Church requests that such submissions be made instead to
>Ancestral
>>File.
>
>Sorry to disagree on this point; Any one can submit names to the
>general
>temple file if they desire to do so. As long as they follow the steps
>and
>rules outlined in the temple ready program.
>It is correct that no nonmembers should submit names to the temple
>family
>file without having some family members or friends whom are members do
>the
>work (be the proxies).
>
>
> Groetjes from...............Peter!!!!!!
>
> Genealogy: First a commandment, then a curiosity, then an
>interest,
> then an addiction"
>
>============================================================================
>For assistance and help for the PAF Mailing List please contact
>ed.rogers@bigfoot.com or http://www.innernet.org/paf/
>============================================================================
>
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Mon, 26 Oct 1998 20:15:00 EST
From: aaberg3@juno.com (Robert M Aaberg)
Subject: Re: [PAF] More on; Family History Training Broadcast
On Sun, 25 Oct 1998 18:51:07 +0000 "Alice Harris" <akh@molalla.net>
writes:
>Do you know if this will be a tv or a radio broadcast?
It's on TV but you must have dish for satelite.
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Tue, 27 Oct 1998 00:29:56 -0700
From: Peter Van Schaik <peter.van.schaik@T8000.com>
Subject: [PAF] RE: TEMPLE READY HELP
Hi , I found a simple solution wich we use in our center after these and
faulty disk complains.
I wrote a little batch file which first does a "scandisk" and then looks
for all *.sub files on that disk.
Any person with basic DOS knowledge could do this. Maybe there is somebody
out there that can make it even better, I am allways looking for easier and
better!!!!
In your word processor create a file and save it as check.bat
Type the following text in this file.
save it.
Include this in your menu program .
rem batch program check.bat
echo off
cls
echo .
echo This will check your TempleReady disk for errors
echo .
echo If a file named "yourname.rec" with today's date beside it appears,
echo your disk is ready to send to the temple.
echo "yourname" is the name that you used to name your submission file.
echo .
echo If the list shows any bad files or units your disk is NOT
echo ready to send to the temple.
echo If NO files are found ,your disk is NOT ready to send to the temple.
echo .
echo PUT YOU DISK IN THE A OR B DRIVE
echo (A) Drive A - Checks the disk in A
echo (B) Drive B - Checks the disk in B
choice /c:ab
IF ERRORLEVEL 3 GOTO end
IF ERRORLEVEL 2 GOTO b
IF ERRORLEVEL 1 GOTO a
:A
dir/p a:\*.*
chkdsk a:
pause
GOTO end
:B
dir/p b:\*.*
chkdsk b:
pause
GOTO end
:end
c:
At 09:31 PM 10/26/98 -0800, you wrote:
>>
>>I have personally found that the more diskettes people have, the more
>>confused they become.
>>
>I agree!
>The temple (Oakland) has asked us to help the patrons to identify the right
>disk to take to the temple. More and more people are showing up at the
>temple with the wrong disk and the temple computer can do nothing with it.
>What a disappointment!
>
>
Groetjes from...............Peter!!!!!!
Genealogy: First a commandment, then a curiosity, then an interest,
then an addiction"
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@bigfoot.com or http://www.innernet.org/paf/
============================================================================
------------------------------
End of paf-digest V1998 #60
***************************
To unsubscribe to PAF-Digest, send the following command to
majordomo@innernet.org:
unsubscribe paf-digest
At this point there is no direct method to receive back issues other than
to email ed.rogers@bigfoot.com. Happy PAF'ing!