Yesterday’s New FamilySearch (NFS) rollout news was so riddled with problems, I finally scrapped it. Today, we try again. Apparently, not all the rumors circulating right now are sanctioned. I don’t know if that means the information is incorrect, or just not yet officially announced. I’m still waiting on clarification from FamilySearch.
To keep track of the varying stages of rollout in the different temple districts, and the various flavors of rollout, I’ve created a new table format. For the remaining temple districts in the red zone, here’s my new table. When I can, I’ll get this copied to my regular page, “Temple Districts Using New FamilySearch.” I’ve added lots of question marks to reflect current uncertainties.
|Temple on NFS||Consultants on NFS||Members on NFS|
|Idaho Falls||45||Yes||By end of July||18-Jun-2009||?|
|Logan||43||Yes||2-Jun-2009||8-May-2009 (All)||02-Jun-2009 (5) |
Total (29 stakes)
|Mt. Timpanogos||61||Yes||8-Jun-2009||26-May-2009 (60) |
|Read-only (60) |
|St. George||44||Yes||23-Jun-2009||8-May-2009||Read-only ?|
Numbers in parentheses refer to the number of stakes.
* Recently updated
† Highland Utah Stake
That leaves just two temple, the Provo temple and the Jordan River temple, that have not yet entered the transition to NFS. And only one temple, Draper, can’t process Family Ordinance Requests (FORs). I’ve updated my map to reflect the current situation, with just two red dots left.
When I can, I’ll get this updated at “Temple Districts Using New FamilySearch.” Do I have the dates correct for your temple starting to use NFS internally? What about consultants in Jordan River and Provo? Can you register in NFS? Full-access or read-only? Let me know. Keep everyone informed by sending your news to AncestryInsider@gmail.com .