Official statement on the future of Personal Ancestral File (PAF)
David March 31st, 2008
Today FamilySearch has released news regarding future support for PAF. The decision to not expand PAF’s functionality to interface with the new FamilySearch doesn’t come as a surprise to me. The Church isn’t in the business of commercial software. Did you know that the Windows version of PAF was adopted from a previous version of Ancestral Quest? (See Information for Users of PAF) In addition, years ago the Church has opened up the PAF API to commercial developer to create add-on applications, such as PAF Insight. The new FamilySearch will have public APIs so that these competing commercial products will have access as well as PAF add-on products so that users most comfortable with the existing PAF interface can continue to use it for years to come.
From Gordon Clark, Family and Church History, LDS Church,
The Future of PAF
Personal Ancestral File (PAF) is a free genealogy software program offered by FamilySearch. PAF has amassed millions of users since its introduction in 1997. Over the years, many other genealogy software programs have been introduced by commercial companies. Most of these programs offer additional features while often supporting the GedCom and PAF file formats.
The last major release of the program was PAF v5.2 in 2001. Since then, FamilySearch has been developing a web-based genealogy system that will allow the general public to create, search, manage, and share their family histories completely online. This online system will also replace TempleReady, a software program used exclusively by Latter-day Saints to prepare records for temple ordinances. The first phase of the new system (referred to as New.FamilySearch) is being rolled out to members of The Church of Jesus Christ of Latter-day Saints. Once the system is complete, it will be available for free to the general public and in multiple languages.
PAF does not currently support two way data transfers to the new online system. However, data in PAF can be exported to the new online system by creating a GedCom file of the PAF data and then importing the file into new online system. In the future two way data transfers between PAF and the new online system will be accomplished via a third-party add-on utility.
PAF users can continue using PAF until the new online system is available to them. Once the new system is available, PAF users will have several options available to them:
Upload their current GedCom file one time and thereafter work exclusively from the new online system.
Continue using PAF and exporting any new data via a GedCom file to new online system. This option will require any data that is added to the new online system by others, to be manually entered back into your PAF if you want to have that information on your computer.
Purchase a third-party add-on utility for PAF that enables data transfers between PAF and the new online system, or
Purchase a third-party full-featured software program that supports automatic data synchronization with the new online system.
There are benefits for users who wish to use both the new online system and one of the full-featured software programs. These programs will allow users to:
Work offline and then enable genealogical data to be automatically updated and reconciled with the online system.
Maintain a working copy of your genealogy file on your own computer hard drive, and
Use additional or advanced features that will not be offered in the online system.
The decision is much easier for those who are just beginning their family history and those who do not have an electronic file of their family history—they will simply be able to build their family histories completely online. No other software will be needed.
[…] is dead! LDS Tech: Official statement on the future of Personal Ancestral File (PAF) FamilySearch has been developing a web-based genealogy system that will allow the general public to […]
This is great news. I’m excited for our temple district to come online soon. I’m a little disappointed that it appears the only way to get data back out is through commercial third party applications.
Guess I’ll have to read more about the public APIs.
Yeah, I get the impression that the Family History department wants to move everyone over to the new FamilySearch site, rather than to keep them using PAF. But for those that strongly prefer keeping PAF, they will be able to purchase other software to allow them to keep their data in sync. Ohana Software is working on this add-on right now, calling it Family Insight. From what I understand, those people who have a license for PAF insight will be able to download this software as well under the same license.
“Upload their current GedCom file one time and thereafter work exclusively from the new online system.”
If any of you have even a moderately large gedcom, and you do this, you will soon regret it…:-(
Hundreds of hours of work could result from this…
As stated early in the article, “the Windows version of PAF was adopted from a previous version of Ancestral Quest.”
Ancestral Quest (AQ) has been updated through the years since that happened in 1999. And AQ is being upgraded again to allow direct access to the new FamilySearch. The current version of AQ (version 12) can directly read and write to a PAF 5 database, so a PAF user could use AQ as an add-on to PAF 5. This means that a PAF user will be able to use AQ to directly connect his/her PAF data to the Family Tree of new FamilySearch. Because PAF is so similar to AQ, a PAF user will feel like he/she is using an upgraded version of PAF when using AQ 12.
Note that AQ is a full-featured program, and can replace PAF 5. But because of the ability for AQ to read and write the PAF 5 database directly, it can also be used as an add-on to PAF if the user prefers to continue to use PAF 5 itself.
@Fred
I agree that you wouldn’t want to just upload your entire GEDCOM file all at once. This phrasing is a bit misleading to assume that this can be easily done in one step. Every bit of data in your local file that already exists with new FamilySearch (NFS) will have to be combined manually, so introducing a lot of duplicate records is just a lot of work that can be avoided. There is a way to safely upload your data as a GEDCOM. To do so you will need to carefully compare your personal data with that on NFS, and then create small GEDCOM files for only the records that are different or new.
Since this process will certainly be tedious to do manually, I’m hoping to see 3rd party applications that can do this comparison much more automatically. I know that there are a number of software vendors who are registered as developers on the NFS API, and I’m sure that they are actively working on these types of issues.
To avoid additional duplication in NFS, any gedcom information added to NFS is requested to be searched for name by name before uploading to NFS and a statement that that has been done is electronically signed by the contributor. Also, NFS is for deceased individuals, only not the living, so complete family trees are not visible to anyone but the contributor.
I don’t know where this blog got their information, but, the above article is not in any Church Family History department announcement at this time. The official document on the subject says this about whether PAF is dead and the future of PAF:
PAF Is Still Needed
PAF is one of the genealogy database programs that can produce GEDCOM files, which can be uploaded to the new FamilySearch.
While there are no plans to further develop PAF, it remains a dependable and easy-to-use program. Users of PAF can receive support by telephone or e-mail, as well as through the knowledge base in the Product Support area of http://www.familysearch.org. Local support may also be available at a family history center or from a family history consultant. There are also inexpensive utility programs that provide enhancements. These include PAF Companion, PAF Insight, and PAF Wiz.
If a PAF user later decides to switch to a different program, his or her data can be exported as a GEDCOM file and then imported to any commercial genealogy database program that uses GEDCOM. Some of these programs have the ability to import a PAF file directly so the data does not have to be reinput, but simply loaded into the new program.
PAF and the New FamilySearch Are Complementary Products
PAF stores a wide range of data with sources and voluminous notes. With it, users can perform advanced searches of data and can print a variety of reports, including books. PAF has a built-in “Print-to-file” (RTF) feature, which allows users to create electronic copies of reports and charts that can be sent as e-mail attachments. If a free PDF writer such as PrimoPDF or CutePDF is installed on the computer, PAF can use it to create PDF copies of reports and charts that could then be e-mailed or even posted to a Web site. PAF has a Preview feature that allows users to see a report before they print it. Users can also link multimedia files to their PAF data. Many of the personal genealogical databases on the Internet were created using PAF.
The New FamilySearch Will Play a Different Role
The new FamilySearch will replace TempleReady.
I too am not surprised that the Church has chosen not to upgrade PAF. Back in 1997, the Church wanted to be get as many people as possible involved in Family History and temple work quickly. So, providing “free” software was a great way of getting that done. Since that time many PAF users have purchased several commercial add-ons to give them more usable features.
Today, there are several third-party full-featured software programs on the market. One of the developers working with the Church to provide automatic data synchronization with new FamilySearch is RootsMagic. ( http://www.RootsMagic.com ) The developer has been demonstrating this synching for several months now at conferences including the ones at BYU. So I can share with you that I have been beta testing this integration and find it to be extremely fast and efficient. It is not tedious at all, nor will I ever have to upload a gedcom of my data. RM will upload and download my data as needed. The other great thing for PAF users is that RM will automatically open a PAF file and allow the user to do the same automatic integration with nFS! Check out RM’s website and see the array of features that are in the current version as well.
@Joy
This announcement came from Gordon Clark, who I believe is one of the Product Managers for NFS. This statement was read at the FamilySearch Developers Conference which I attended on March 12 in Provo. He resent it to the developer distribution list for the NFS API on March 31, which is when I added this quote to my blog.
Perhaps the reason why this same announcement doesn’t appear on any official FamilySearch news sites is because there aren’t any “registered” 3rd party applications which can provide this functionality yet. Obviously Gordon Clark thinks that this is important information to get out to the public, which is why he has sent this out to the development community first… those who will be building these 3rd party tools.
@SueM
There will be a number of 3rd party tools which will be able to synchronize with NFS, including RootsMagic, as you mentioned. There are quite a few others as well, which is all due to the webservices API that the FamilySearch developers have created. It will be exciting to see all of the tools that will be created to take advantage of this functionality. For those who have genealogy web sites, PhpGedView will have this NFS integration with version 4.2 (currently at 4.1.3).
I have heard about this Beta product for over a year. This announcement does not indicate a launch date. Does anybody have any idea? I’d like to be part of the beta. Can I join?
I hope this isn’t another mormon urban legend….I’m sure it’s true, but I’d like it to happen sooner, rather than later. And what constitutes a moderately-sized GEDCOM file? 1000 names, 10,000 names, 100,000 names?
Does anybody know how much sharing of information can be done? Can I share my info “living” info with siblings, parents, or is only “dead” relative information shareable?
@Mormon Heretic
So many questions! The new FamilySearch isn’t in beta any longer, but it is being phased in regionally (see current status). As a genealogy consultant in my stake and having attended a special training session at the Salt Lake Genealogy Library, I now have access to the new FamilySearch at http://new.familysearch.org. In the online training for this, they say that a maximum size GEDCOM which they recommend is less than 100 records.
Regarding living individuals… there is actually a complex set of rules regarding how the system tracks living data, but in a nutshell… no, you won’t be able to see the living data for distant relations or unrelated individuals. (That is why it is still important to keep copies of your data in PAF or other genealogy program)
I am following this with great interest as a ward family history consultant. I have served in Utah and the Washington, D.C. suburbs and worked in a Family History Center for a dozen years. Based on my experience, I wonder who will benefit from the online NFS and, even worse, who will be left behind. In our Utah ward, my wife and I work with senior citizens, older members who don’t have internet, older computers barely able to run PAF 5.2, who have difficulty learning to “double click” the mouse. These are stalwarts in the Church that I think are going to be left behind. Our members count on the ward family history consultants to help them with PAF. We also take them to the Family History Centers to use PAF Insight and Temple Ready. How will ward family history consultants deal with numerous third-party tools and add-ons. Our young, quick-minded, and easily taught ward members are not the ones with the time and the inclination to do family history. I know the Family Search website has millions of users and billions of hits, but the LDS members seem to be submitting the same individuals over and over again for ordinances. Having attended two meetings of introduction and explanation with the developers, I still don’t understand how the new system will eliminate duplication of ordinances. Will there be fuzzy logic and other tools that are more effective to indicate ordinance work has all ready been done and block duplicate submissions, or is this still the decision of the patron? Is there more detailed information for the concerned LDS user or must we sit and wait and see what comes out of all of this?
@John
The NFS isn’t going to completely eliminate duplication of ordinances, but will make it much easier to identify duplicate records associated with the same individual. Then if one set of these combined records has ordinance work done, it is assumed that this work is complete for each of these combined records.
If you are a consultant or priesthood leader, you can register for online training at http://consultant.familysearch.org or through the help links in NFS. Some training modules specific to NFS won’t be available to you until you are actually registered as a user for NFS.
There are several sites that have published additional NFS training, including the Mesa, Arizona Family History Center. (scroll down to PowerPoint training)
@John S. Beardall
I too have been concerned with the subject for several years and have had many conversations with nFS Managers and other in the Department about the future of PAF. It would seem that one person’s mind has been made-up, but this is not a consensus.
I would like to talk with you privately at my special E-mail address (single use only) and by the correct person at
paf_dead_no at cox dot net
Please put your name in the Subject, all others will be deleted.
David–thanks for the info. So Utah isn’t on the map! I guess they want to try it on smaller groups before they unleash it here, eh?
I have about 10,000 records in my PAF. Some of these are due to me merging with my wife’ family, and some of my cousins families, so the relatives are either distantly related, or perhaps not very related. What do you recommend I do with my GEDCOM for the new website?
Also, I was going to register on the new site, but I can’t remember my member record #, so I’ll have to get it Sunday at church. Is it still a good idea for me to register?
@Mormon Heretic
We are being told here in Utah to expect it by the end of the year, but that assumes that they can work through some of the bigger bugs that they have been experiencing with the new site. (If you go to http://new.familysearch.org and click on News and Updates, you’ll see all of the changes that they have continued to introduce since it was first released)
With 10K names, you definitely don’t want to just load it into NFS and hope for the best. You will be combining records for a very long time, especially if very much of that data already exists in Ancestral File or Pedigree Resource File! The other issue is a matter of how clean your records are. If you are using PAF reports, PAF Insight, and PAF Pal to be sure that place names are complete and consistent, you will be much farther ahead when you are ready to start loading your data into NFS.
I suspect that most of the information is available in the Pedigree Resource File–nearly all of my research has been done on the church websites. I’ve used PAF Insight for the temple info, but wasn’t aware of the other products. My place names are pretty good, but I’m sure not perfectly clean.
So, I’m still not sure what you think is the best approach. It sounds like you’re saying I should clean up my data the best I can, before I launch into the new website. With 10K names, that will take quite some time, as the Ancestral File and Pedigree Resource File aren’t really clean data sources either. Does my reasoning sound logical? Am I missing anything?
@Mormon Heretic
Other than cleaning up your data and working through it little by little once you start using NFS, I don’t have any other recommendations.
From those people that I have been in contact with who are actually using this system, they are consistently happy with it but recognize that there are still areas of improvement. The slow and methodical approach necessary to compare and combine your personal data with NFS data will continue to be improved, particularly for those who are open to using 3rd party tools when they become available. But even best of these tools won’t be a “silver bullet” by doing all the work for you.
There isn’t anything that precludes people happy with PAF to continue using it and manually comparing individual records with NFS or bringing their data to a Family History Center for assistance when they are ready to check for ordinances. (This approach is still better than the current one of manually checking Temple Ready.)
Most LDS members have created their PAF files by downloading from church databases; IGI, Temple Records, Ancestral File, and the Pedigree Resource File. Since newFamilySearch (nFS) combines all of these databases with LDS Membership information, then combines duplicate individuals into folders and links families into pedigrees, members will find that most of the information in their PAF file is already in nFS. At the present time nFS does not want any duplicate individuals contributed by GEDCOM’s. You have to certify that you have checked your GEDCOM and that you are only contributing new individuals when you submit a GEDCOM file. We are encouraged to wait for software to sync our existing data with nFS.
There are many web sites where information can be found about nFS, including Church sites. You can go to FamiySearch.org and click on “Product Support” and type in questions about nFS and get your questions answered. Many of the future enhancements to nFS are available for review at familysearchlabs.org You can also go to lds.org and select “Serving in the Church” then “Family History” for more information and if you are a Priesthood Leader or a Family History Consultant you can register for e-mail updates and to receive an advanced account 90 days prior to your temple district coming online.
newFamilySearch accounts are not available to members unless their temple district is using the new software, so you may need to wait before you will be allowed to register at new.familysearch.org for an account.
Directors of Family History Centers and some trained Family History Consultants may have early access to newFamilySearch and can show you the program if you go to your local Family History Center.
Hi Mormon Heretec -
I’ve been working online with New Family Search for a month now.
It looks like they already started it off with tons of stuff from the old Family Search, IGI and LDS Church Files.
Odds are you won’t need to upload any GedComs. In fact - I’m seeing that for common big family trees there is a lot of duplication.
Because of the massive duplication already in NFS - we are being told to limit new GedCom uploads to only 10 records each.
[…] expert, DearMYRTLE, raised a concern about my previous quote regarding PAF. She did some research into whether my sources were considered […]
I for one am on the NFS, and am NOT happy with it. It’s no better than the betas they had out a while ago. I am 25 years old, and very tech savy. I just can’t figure out why they do the things they do. I’ve read on some blogs that the NFS people are guessing that 30 percent of NFS submissions are duplicates.
-The software has bellls and whistles in all the wrong places
-The limitations are noticable, and frustrating
-The data set is incredibly error-laden
-The users don’t know what they’re doing and combine wrong people (don’t even think about trying to separate people, uff!)
-Currently there is no good way to source the data
-There is no way to rank or grade the authenticity of the data
-You can never delete erroneous and misleading information
-If you do spend the hour or two to seperate two incorrectly merged people, the suggestions to merge them just come right up again for your cousin or someone to merge them again
-The printing functions are impossible
-The pioneer stock and royalty are so duplicated that it takes several minutes to load each individual
-The temple work suggestions are almost always wrong (would they be in the LDS databases if the temple work wasn’t done? No, 99.9% of the time.)
Abandon my PAF 5.2 database in favor of NFS? I think not.
And by the way, the only people who are “consistently happy” with NFS that I’ve met are the ones who haven’t got a clue about what they’re doing.
The real genealogists of the church are up in arms about the problems with NFS. People are confusing inspired mandate to reduce duplication with inspired software developers.
NFS will probably just turn out to be a mess of bad information, just like the Ancestral File, the Pedigree Resource File, and the International Genealogical Index. For all of our sakes, I hope they get their act together and fix this thing.
I am really impressed with NFS. I realize it is not fully developed, but we have to remember it is still a very new program.
I find it very easy to combine names and yes, I did make a mistake in doing so once… but it was very easy to separate the name back off again. I found no problem doing so.
The many duplicate names are not the fault of NFS, but a result of many people doing temple ordinances and NOT having NFS earlier.
I love the ease of clearing names for temple ordinances. The prospect of having a handle on all of these names in one huge database and the freedom to work with it. I also understand the need to not delete information. I find the support excellent when I have had some problems.
There are issues being worked on by the developers, such as large files where there are many duplicates. My wife has one family member with 102 duplicates.. this is very hard for the system to handle.
I hope we will remember that there are many working on the issues and that this is the Lord’s work. We ought to be praying that they are inspired to resolve any issues so that the work may go forth even faster.
The software has been easy to use and quick to learn. And although there are suggesions I have made and others I know as well, I want to say I love it and it has renewed my interest and intensity in finding and submitting these names to the temple.
One last comment for now.. I love the way we can separate ordinances, by using the reserve list and then when done doing what we can do, we can turn the rest back to the temple. This comes in very handy when I want to do 50 baptisms with our youth group, but I can’t do 50 endowments when my temple is 4-1/2 hours away.
@Daniel
It is good to hear of those who are having success with NFS. I would tend to agree that many of the problems that are being blamed on the NFS data have actually existed for years but only until now has the extent of this problem been made readily visible to genealogists.
Even with the value provided by NFS, there will always exist a need for PAF and similar programs. However the need to easily synchronize data between NFS and PAF-like programs will become more apparent as NFS finally replaces existing LDS applications in all locations.