Tuesday, June 2, 2009

Name counts for Newspapers

Bozeman Daily Chronicle on Ancestry.com Last Friday I was excited to see Ancestry.com had added a whole lot of new newspapers to its collection. I took especial notice of the Bozeman Daily Chronicle of Bozeman, Montana and immediately checked it out.

You’ll be happy to know that if you need the Daily Chronicle for 14 October 1926, you’re in luck because that is the only issue in Ancestry.com’s collection. I previously complained about Ancestry.com’s Salt Lake Tribune database. Number of issues at the time? Two. (I’m pleased to find as I write this article that they’ve beefed up the Tribune considerably. However, according to the card catalog, the database has never been updated. That may be why the additions were never announced on the New and Updated Databases page. But I digress…)

The new card catalog can be used to identify the leanest newspapers in the Ancestry.com collection. Sort by record count and page through to the end of the list.

Interestingly, all the sizes are multiples of 60. If one investigates the last newspaper in the list, one finds it is comprised of a single page from a single issue. One can also verify that the papers with size of 120 have but two pages. Continuing, one finds that the number of pages is equal to the reported size divided by 60.

Title Size   Pages
Chicago Daily News (Chicago, Illinois) 360 6
Weekly Evening Gazette (Reno, Nevada) 360 6
Decatur Daily Review (Decatur, Illinois) 360 6
The Daily Mail (Charleroi, Pennsylvania) 300 5
The Southern Immigrant (Cullman, Alabama) 300 5
The Hancock News (Hancock, Wisconsin) 240 4
The State Sentinel (Decatur, Illinois) 240 4
East St Louis Journal (East Saint Louis, Illinois) 240 4
Californian (Monterey, California) 240 4
Bulletin Sentinel (Decatur, Illinois) 120 2
Bridgeport Sunday Post (Bridgeport, Connecticut) 120 2
Weekly Decatur Magnet (Decatur, Illinois)   60 1
New York Times (April 15th, 1865)   60 1
The Mountain Democrat and Placerville Times (Placerville, California)    60 1

 

Why does Ancestry.com claim newspaper sizes 60 times larger than actually size?

You may recall we previously saw an anomaly in the new card catalog that led us to the assumption that the size displayed by the card catalog is a name count rather than a record count. (See “Extras in the Ancestry.com New Card Catalog.”) Ancestry.com needs to identify what they mean by “Size.”

So what is the probability that each page of these newspapers has exactly 60 names?

Not very likely, is it? In response to my article “Unbelievable Name Count Claims,” Paul Allen of WorldVitalRecords.com commented that vendors sometimes estimate the number of names in a database.

Name counts in OCR databases

Estimation is necessary for non-table-style databases such as books and newspapers because the index is an every-word index, obtained via OCR. OCR, optical character recognition, is a software process wherein a computer program attempts to read the images and create a matching document with all the words found on the image.

After the task of recognizing words, the computer still doesn’t know what the words mean. What you and I easily recognize as a person’s name is beyond the computer’s ability to identify with any degree of certainty. Thus, newspaper vendors must estimate the number of names present.

Obviously, some pages will have more and some less. To be sure, the subject of a news article will likely be named multiple times. Should a vendor attempt to count unique names? That will undercount the actual number of names. Should a vendor attempt to count unique people? Equating and differentiating people requires intelligence well beyond that of machines.

It would seem from our table above that Ancestry.com assumes an average of 60 names per page across all the pages of a newspaper. In my career, I’ve seen samples justifying higher numbers, when repeated names are included. Overall, I think 60 is very reasonable.

My recommendations to Ancestry.com and FamilySearch (and other vendors) are to be completely transparent in your size claims:

  • Don’t report a size number without identifying if it is a record count or a name count
  • Report record counts, name counts, and image counts
  • For table-style databases, report the actual number of names present
  • When an estimated count is published, designate it as such (I favor use of the approximation symbol (≈) to identify estimated numbers)
  • For estimated counts, document how the estimate was obtained

Ancestry.com’s New Newspapers

Here’s the entire list of new newspapers posted Friday:

Genealogy Database Title Posted
Deming Headlight, The (Deming, New Mexico) 5/29/2009
Star Herald (Scottsbluff, Nebraska) 5/29/2009
Bozeman Daily Chronicle (Bozeman, Montana) 5/29/2009
Dundee Record (Dundee, New York) 5/29/2009
Daily Journal (Herrin, Illinois) 5/29/2009
Boone Svenska Herald (Boone, Iowa) 5/29/2009
Cherokee Daily Times (Cherokee, Iowa) 5/29/2009
Dyersville Commerrial (Dyersville, Iowa) 5/29/2009
Evening Journal Farm Edition (Washington, Iowa) 5/29/2009
Gladbrook Tama Northern (Gladbrook, Iowa) 5/29/2009
Grinnell Herald Register (Grinnell, Iowa) 5/29/2009
Hopkinton Leader (Hopkinton, Iowa) 5/29/2009
Humboldt Republican (Humboldt, Iowa) 5/29/2009
Jewell Record (Jewell, Iowa) 5/29/2009
Lake City Graphic (Lake City, Iowa) 5/29/2009
Leon Journal Record (Leon, Iowa) 5/29/2009
Lone Tree Reporter (Johnson, Iowa) 5/29/2009
Manchester Democrat Radio (Manchester, Iowa) 5/29/2009
Manning Monitor (Manning, Iowa) 5/29/2009
Marshall County Time (Marshall, Iowa) 5/29/2009
North Iowa Times (McGregor, Iowa) 5/29/2009
Sac Sun (Sac County, Iowa) 5/29/2009
Schaller Herald (Schaller, Iowa) 5/29/2009
Story City Herald (Story City, Iowa) 5/29/2009
The Alabama Courier (Athens, Alabama) 5/29/2009
Bruce News-Letter (Bruce, Wisconsin) 5/29/2009
Green-Bay Intelligencer (Navarino, Wisconsin) 5/29/2009
The Fairfield Daily Ledger (Fairfield, Iowa) 5/29/2009
Indiana Progress (Abbeville, Alabama) 5/29/2009
The Western Telegraph (Rossville, Ohio) 5/29/2009
Chicago Heights Star Sports (Chicago Heights, Illinois) 5/29/2009
Belmont Gazette (Belmont, Wisconsin) 5/29/2009
Oconomowoc Democrat (Oconomowoc, Wisconsin) 5/29/2009
Yellow River Lumberman (Necedah, Wisconsin) 5/29/2009
Oconto County Enterprise (Oconto, Wisconsin) 5/29/2009
Du Buque Visitor (Du Buque, Wisconsin) 5/29/2009
Winnebago Anzeiger (Menasha, Wisconsin) 5/29/2009
The Maiden Rock Press (Maiden Rock, Wisconsin) 5/29/2009
The Rice Lake Times (Rice Lake, Wisconsin) 5/29/2009
The Benton Advocate (Benton, Wisconsin) 5/29/2009
The Revealer (Bloomington, Wisconsin) 5/29/2009
The People's Champion (Ellsworth, Wisconsin) 5/29/2009
Prison Press (Waupun, Wisconsin) 5/29/2009
The Fairchild Graphic (Fairchild, Wisconsin) 5/29/2009
Fox Lake Representative (Fox Lake, Wisconsin) 5/29/2009
The Wisconsin Standard (Geneva, Wisconsin) 5/29/2009
Voice-Herald (Hales Corners, Wisconsin) 5/29/2009
The Breeze (Pardeeville, Wisconsin) 5/29/2009
Beloit Journal, of Politics, Literature, and General Intelligence (Beloit, Wisconsin) 5/29/2009
Agitator (Wellsborough, Pennsylvania) 5/29/2009
Arizona Silver Belt (Miami, Arizona) 5/29/2009
Charleston Daily Mail (Charlestown, West Virginia) 5/29/2009
Fort Dodge Messenger And Chronicle (Fort Dodge, Iowa) 5/29/2009
Horicon Argus (Horicon, Wisconsin) 5/29/2009
Lockhart Post-Register (Lockhart, Texas) 5/29/2009
Marble Rock Journal (Marble Rock, Iowa) 5/29/2009
Monroe Sentinel (Monroe, Wisconsin) 5/29/2009
Mt Pleasant News (Mt Pleasant, Iowa) 5/29/2009
Natrona County Tribune (Casper, Wyoming) 5/29/2009
Neenah Bulletin (Neenah, Wisconsin) 5/29/2009
Newcastle News-Journal (Newcastle, Wyoming) 5/29/2009
Northwestern Record (Sheboygan Falls, Wisconsin) 5/29/2009
Reedsburg Herald (Reedsburg, Wisconsin) 5/29/2009
Richland County Observer (Richland Center, Wisconsin) 5/29/2009
Mt Ayr Journal (Mount Ayr, Iowa) 5/29/2009
Fayette Journal (Fayetteville, West Virginia) 5/29/2009
Lebanon Daily News (Lebanon, Pennsylvania) 5/29/2009
West Eau Claire Argus (West Eau Claire, Wisconsin) 5/29/2009
Milford Mail (Milford, Iowa) 5/29/2009
Terril Record (Terril, Iowa) 5/29/2009
Lake Park News (Lake Park, Iowa) 5/29/2009
Spirit Lake Beacon (Spirit Lake, Iowa) 5/29/2009
Adams County Free Press (Corning, Iowa) 5/29/2009
Desert Hot Springs Sentinel (Desert Hot Springs, California) 5/29/2009
Aiken Standard (Aiken, South Carolina) 5/29/2009
Tyrone Daily Herald (Tyrone, Pennsylvania) 5/29/2009
Daily News (Huntingdon, Pennsylvania) 5/29/2009
Tyrone Star (Tyrone City, Pennsylvania) 5/29/2009
Evening Chronicle (Marshall, Michigan) 5/29/2009
Sioux County Capital (Orange City, Iowa) 5/29/2009
Alton Democrat (Alton, Iowa) 5/29/2009
Boyden Reporter (Boyden, Iowa) 5/29/2009
Sioux Center News (Sioux Center, Iowa) 5/29/2009
Hospers Tribune (Hospers, Iowa) 5/29/2009
Ireton Ledger (Ireton, Iowa) 5/29/2009
Maurice Times (Maurice, Iowa) 5/29/2009
Sioux County Index (Hull, Iowa) 5/29/2009
Avalanche (Lubbock, Texas) 5/29/2009
Laredo Times (Laredo, Texas) 5/29/2009

Monday, June 1, 2009

New features coming to FamilySearch Indexing

Current About popup from FamilySearch Indexing Tuesday, 26 May 2009, FamilySearch announced that new features were coming to FamilySearch Indexing. Friday, they announced a delay in the downtime previously scheduled for 1 June 2009.

New features in FamilySearch Indexing

Several new features are included in the upcoming FamilySearch Indexing version 1.7.

Tip of the Day. A popup titled “Tip of the Day” will come up when you start FamilySearch Indexing.

 Passwords. You can choose a password that doesn’t include a symbol. However, passwords still require at least one numeral.

Project Preferences. You can select preferences for the indexing projects you wish to index:

  • the difficulty level and
  • the languages you can read.

Project Selection Dialog Box. The Download From... Project Selection dialog box (below) includes three new features.

ProjectSelection

  • The project Selection dialog box will have the option to show only those projects that match your preferences.
  • The Project Selection dialog box will also display the difficulty level of each project.
  • Double-clicking a project will be a short-cut that will download a batch.

Batch Sharing. This feature allows someone to view a batch you are working on so they can help you. For example, if you have a question that you need someone in Support to help you with, you could share the batch with them. Or you could share the batch with a friend who could help you with the handwriting. However, only the original indexer can save changes to the batch.

Prior to sharing a batch, you should save your work. Then click on File and Share Batch. FamilySearch Indexing will display a message reading

Contact the person you want to share this batch with and give him or her the following number: XXXXX.

Give this number to the person you want to help you. That person views your batch by taking the following steps:

  • Open the FamilySearch Indexing application.
  • Click the File menu, then select View Shared Batch…
  • Enter the sharing number and click OK.
  • To display the latest data typed and saved by the indexer, click on the File menu, then click Retrieve from Server.

Icons to Mark a field or record unreadable previously had a red slash Image Type. Image Type will be the first field in every batch. You will select the description of each image (such as Normal, Blank, or Duplicate) from the list provided.

New Icons. The icons used to mark a field or record unreadable will have a blue question mark on them instead of a red slash.

A new Header tab will join the other tabs in the data entry Header Data Tab. A new tab in the data entry area will enable indexers to enter information that applies to an entire document just once. Not all batches will include this tab, but if it is included, it will open first when you download a batch. I believe this is a feature available in Ancestry.com’s World Archives Project.

Mid-batch Quality Check. Click the Quality Checker tab before getting to the last field of the last record and you can see and correct all errors up to that point. You won’t be warned, however, about empty required fields until you do the final quality check.

Fields Marked for Review. To mark fields for review, you can choose to display either the red wavy line as in the past, or the colored background. (Is that what the Ancestry.com World Archives Project uses?) You can also change the color and transparency.

You can read more in the Help article, “FamilySearch Indexing: What’s new in indexing for release 1.7.”

Click the Start Indexing button on the FamilySearch Indexing web page
Click the Start Indexing button on the
FamilySearch Indexing web page if you
have problems after the upgrade.

Downtime postponed

Along with the new features, FamilySearch announced an associated downtime when the new features would be rolled out. Friday, they announced that the downtime previously scheduled for 1 June 2009 from 9 AM to 5 PM (MDT) would be delayed for as much as a week. FamilySearch will post a notice during the week giving at least 24 hours warning before the downtime actually occurs.

Usually, when a new version of FamilySearch Indexing is available, it will download to your computer automatically. But if it doesn’t, you may experience problems using FamilySearch Indexing. During this week, or the first time you index after this week, if you experience problems, close FamilySearch Indexing, go to the FamilySearch Indexing web site (http://indexing.familysearch.org) and click the Start Indexing button (see illustration above or to the right). This should download the new version 1.7 to your computer if it hasn’t already. This will fix any problems associated with using the old version on your computer after FamilySearch headquarters is using the new version.

Friday, May 29, 2009

Ancestry.com Passes 8 Billion Records

Scientists and computer users use metric prefixes in which k means a thousand and M means a million. A few isolated groups, such as the energy industry, used the Roman numeral M for one thousand long before the metric system came along. For a million, they use MM, a thousand thousands (although MM actually means two thousand). It’s very confusing.

Especially when both systems are intermixed, as they are in Ancestry.com’s May Update.

But I digress…

Ancestry.com hit a big milestone this month. They surpassed 8 billion records. Notice they didn’t use the sometimes-inflated measure of name counts. Eight billion records is pretty darn impressive. Here’s a break down by category. The M means millions, the B means billions.

Titles

Images

Records

Birth, Marriage & Death

38.9 M

1,100 M

Census & Voter Lists

27.7 M

900 M

Court/Land/Probate

3.4 M

12 M

Directories & Member Lists

7.6 M

2,100 M

Family Trees

0 M

1,400 M

Immigration & Emigration

31.6 M

180 M

Military

80.6 M

125 M

Newspapers & Periodicals

42.5 M

2,400 M

Pictures, Maps & References

2.1 M

32 M

Stories, Memories & Histories

6.1 M

105 M

TOTAL

240 M

8.3 B

 

Over the past three years, the number of records in the census & voter list category has grown from under 750 million to over 900 million. Ancestry.com points out that they have also been upgrading their census collections. I have to point out that much of that has occurred in cooperation with FamilySearch.

Record growth in Ancestry.com census and voter lists

Over the same time frame, Ancestry.com has increased their vital record collection by an impressive 350 million records. Neither Ancestry.com nor FamilySearch have mentioned any deals on vital records, but I notice quite a few new vital record collections are from FamilySearch. Look for sources mentioning “Intellectual Reserve,” the intellectual property arm of FamilySearch sponsor, the Church of Jesus Christ of Latter-day Saints. See, for example, “Norway Births and Christenings, 1600s-1800s”, Marriages, Netherlands Births and Marriages, Denmark Births and Marriages, …

But I digress…

Record growth in Ancestry.com vital records

The growth of immigration records from a little over 110 million records to 180 million records has been stretched over all three years.

Record growth in Ancestry.com immigration records

While no graph was supplied, Eric Shoup reports that during the same period users have contributed “10MM trees online and 1 billion people.”

Shouldn’t that be 1MMM people?

Regardless, congratulations to Ancestry.com!

Wednesday, May 27, 2009

Boise and Mount Timpanogos Districts

According to the New FamilySearch (NFS) Utah and Idaho Release website, Family History Consultants for the Church of Jesus-Christ of Latter-day Saints in two additional districts have received word that NFS is soon coming to members of the Church in their districts:

  • Boise Idaho
  • Mount Timpanogos (American Fork) Utah

Consultants in these two districts join those in St. George Utah and five stakes in Logan Utah in the advance preparation for the rollout of NFS.

Ever fiddling with the rollout mechanics, text for the Mount Timpanogos invitation letter looked like this:


22 May 2009

To: Family History Consultants in the Mount Timpanogos Utah Temple District

During the past two years, the Church has been introducing a new process for preparing ancestral names for the temple, which includes the new.familysearch.org Web site. After making some changes to the system to support the large number of expected new users, we have begun introducing the new process in Utah and Idaho.

Please accept a special invitation to begin using the new.familysearch.org Web site before it becomes available to the members in your ward and stake. As a family history consultant, you are a member’s primary source of individual family history instruction and help. In this role, you will be a key contact for members who may have questions about this new process to prepare ancestral names for temple ordinances. We will notify priesthood leaders in your stake at a later date with specific information about the release of new.familysearch.org to the members.

We have prepared some new online training courses for you that are designed to help you prepare to help the members of your ward and stake. The information for accessing these courses may be found on the Utah and Idaho release section of consultant.familysearch.org. This release section will be a valuable resource to you throughout your preparations to help members. You will be able to see up-to-the-minute information on preparation resources, helpful tips for using the new.familysearch.org, and regular updates in the progress of the release to stakes in Utah and Idaho.

We encourage you to visit consultant.familysearch.org, and click on the Click Here to go to the Utah and Idaho Instructions button. Then follow the simple instructions to prepare for the release of the new process in your stake. Go back often for updates.

Please encourage any consultants in your ward and stake who have not already done so to go to consultant.familysearch.org, click on the Click Here to Register button, and complete the registration form as instructed so that they too may have early access to new.familysearch.org and begin preparing to help the members in their ward.

If you have questions or problems with this process, please contact FamilySearch.

Sincerely,

FamilySearch
support@familysearch.org
Toll-free: 1-866-406-1830

Tuesday, May 26, 2009

Acronym glossary?

I recently received this request:

Dear Mr. Insider:  I have a modest suggestion.  Although I'm pretty familiar with genealogy terminology, I was stumped for a while about the meaning of FOR in your "Rollout" legend.  Can I suggest that you provide an explanation of acronyms or other terminology utilized in the newsletter that might not be readily understandable to new subscribers?

Thanks for providing a valuable and interesting service to us all.

Jay Deverich
Irvine, CA

Dear Jay,

Thanks for the feedback. I recognize that if I’m not careful, my articles can be problematic for readers for several reasons:

My goal is to make all my articles accessible to all my readers. The editorial approach I have chosen to accomplish this goal is to

  • Never use an acronym in an article without spelling it out the first time it is used in the article. You may tire at the constant repetition, but most of you understand that new readers and new genealogists are joining us all the time. The exception will be in headlines and graphics, where the acronym may be used first and subsequently defined in the text.
  • Provide hyperlinks for concepts that may not be common knowledge, for the reasons listed above. For technical subjects, more likely than not the links will go to Wikipedia. Some of you have expressed concerns about my use of Wikipedia. For technical topics, you have the assurance that I have read the article and consider it a valid explanation. Where I haven’t liked the Wikipedia article, I have found and linked to a better explanation. The only change that I maybe should make is to link to the version of the Wikipedia article that I reviewed. Then if subsequent edits turn the article into something unacceptable to me, my links would still take you to the version I reviewed.
  • Provide supplemental explanations. If you read me long enough, you’ll experience a time where all or part of an article was introductory-level material you already knew. Again, new readers are joining all the time, necessitating a certain amount of review all the time. Explanations may involve basic information about the Church of Jesus Christ of Latter-day Saints. Such information is intended to make member-focused articles accessible to you, my many friends who are not members of my Church.

All that is good and proper in the abstract. The reality is that most of the time articles take far too long to compose. (I sometimes take an hour a paragraph! Can you believe that?) Consequently, I often write in a hurry and neglect to follow my own rules.

Jay, I regularly receive feedback like yours that I’ve missed an acronym, or I’m talking about something without giving the proper background.

I appreciate that feedback very much. Whenever I have time, I go back and fix the archived articles. Please keep those corrections coming.

Signed,

-- The Ancestry Insider

Monday, May 25, 2009

Using Product Support to learn about the Family Tree Project

Screen images illustrating use of Product Support Help

Follow the steps below, as illustrated above, to use FamilySearch Product Support Help to learn more about the Family Tree Project. Start at www.familysearch.org .

  1. Move the mouse pointer to the word “Help” on the FamilySearch web page. (This is called hovering.) Notice a drop-down menu appears with two items: Help and Product Support.
  2. Click on Product Support to go to the Product Support page.
  3. Click in the box in the middle of the page. Then type “Family Tree Project”. Of course, if you were interested in a different topic, one could type a different subject or question.
  4. Click the Ask button under the box.
  5. Look at the Search Results. Underneath each result is a “Published” date (formatted ambiguously, unfortunately). Look for the set of articles published “5/22/09” or scan through the results for the article titled, “Introduction to the Family Tree Project.”

While the dates are currently “Published 5/22/09”, that could change; when I started this article the articles were “Published 5/12/09”. But if you find the Introduction article, you can use the links in the articles to move about the set.

In an accompanying article, we’ll explore what new discoveries I found while learning about the Family Tree Project.

Family Tree Project to eliminate temple duplication

Detail from FamilySearch FamilyTree project For members of the Church of Jesus Christ of Latter-day Saints without access to New FamilySearch (NFS), read-only access to the Family Tree project of FamilySearch Labs will eliminate duplication of temple ordinances of Church members’ ancestors. This according to recent public postings by FamilySearch in the Product Support pages of www.familysearch.org . One such post states,

The Family Tree project is replacing the International Genealogical Index (IGI) as a resource to verify that temple ordinances are complete. … At first, as the Family Tree project is made available to Church members along the Wasatch Front, those members will have read-only access…. Members will not be able to change data or clear names for submission to the temple using the Family Tree project.

(Members of the Church believe that families can be “sealed” together for eternity and actively research their genealogies for submission to the faith’s temples for posthumous execution of these ordinances. The Church teaches that after death spirits of the deceased can choose to accept or reject the ordinances performed on their behalf.)

While most areas of the Church are using NFS and Family Tree to submit ordinance requests, members in Idaho and Utah not on NFS continue to use an old system that relies on consulting the IGI to prevent re-submission of completed ordinances. Unfortunately, the IGI does not include ordinances submitted through NFS. (See “New FamilySearch and IGI are not talking.”) Since NFS and Family Tree include information from both the old and new systems, Family Tree can be checked to prevent duplicate ordinance requests.

Giving members in Idaho and Utah read-only access to NFS data via Family Tree is a clever way, it seems to me, of preventing duplication if the NFS rollout isn’t completed quickly. Somebody’s got their thinking cap on and deserves congratulations.

Re-tasking Family Tree as a tool to prevent ordinance duplication is a change from Family Tree’s original mission.

The Family Tree project is redesigning the look of the new FamilySearch Web site. You are invited to preview and give feedback on this new look while it is still being developed. (Source) When the Family Tree project is made available for full use to all Church members, it will become part of the new FamilySearch, and members will have full use of all features. (Source)

No indication was given for when read-only access to Family Tree will start. In an accompanying article, I show how to find the set of articles containing the posts quoted. That article shows indications that the set of articles was posted and updated within the month.

Friday, May 22, 2009

Mid-May releases of NFS and Family Tree

Well, the middle of the quarter has arrived, so it is time for new releases to New FamilySearch (NFS) and Family Tree. And unlike many past quarters, the releases have come at or near the mid-quarter date, 15 May 2009.

What's New in New FamilySearch

New FamilySearch

As always, the new.familysearch.org sign-in page contains a link to view a list of the updates in New FamilySearch. The “What’s New” document itemizes these changes:

GreenBulletYou’ll recall that IOUSes—individuals of unusual sizehalted the rollout of NFS in February 2008. When the rollout resumed in April 2008, the number of records that could be combined was limited to prevent the creation of IOUSes. In this release, the number of records that can be combined together has been increased from 85 to 150.

Does this mean the IOUS problem has been fixed? I don’t think so. While nearly doubling the number of duplicates allowed, in my opinion this isn’t a fix. I need to be careful here, lest I digress too far. I intend to do an entire article some time showing that the NFS architecture is the right architecture, but should never have been the dumping ground for millions of secondary source records.

See… Already I’m digressing.

No, I’m guessing this change is an intermediate milestone that shows progress is being made towards a complete solution, and that FamilySearch has increasing confidence that the New FamilySearch website can handle more than it currently handles.

GreenBulletRootsMagic 4 has been certified to reserve temple ordinances and print Family Ordinance Requests. Interested parties are directed to www.rootsmagic.com/fs/ and www.familysearch.org/eng/affi liates/index.html .

GreenBulletThe User’s Guide has been updated to clarify the Helper feature of NFS, as I previously reported in “NFS’s Helper Feature.” If you use the Helper feature to help someone not registered as an NFS user, then any changes made will identify the full name of the person helped and your contact name. Moral: unless you’re prepared to be contacted about the changes you make, don’t help someone not registered in NFS.

GreenBulletChanges have been made to the User’s Guide explaining what, if any, information from LDS Church membership records can be viewed in NFS:

  • You can view the names and genders of your current spouse, parents, other direct ancestors, and children. I guess it goes without saying that you can see your own name and gender.
  • For children younger than 18 years of age, you can also see birth dates. Again, I guess it goes without saying that you can see your own birth date.
  • For individuals known to be deceased, you can view name, gender, birth date, and death date. Marriage information can be viewed when both parties are deceased.

GreenBulletThe User’s Guide has been changed, instructing users not to add living relatives who are members of the Church except in minimal situations necessary to link yourself to deceased individuals. Use PAF or a similar program to track information about living relatives.

GreenBulletInformation about Family Tree has been added to Chapter 1 of the User’s Guide. Several additional changes concerned temple submissions.

What's New in the Family Tree

Family Tree

There’s two new links on the Family Tree home page:

  • Register for the new FamilySearch…
  • News and Updates…

I’m not certain what the purpose is for the ellipses (three periods) on the ends of the links. In menu systems, an ellipsis alerts you that you’re going to get an intermediate window prior to execution of the menu item.

Indeed, I do get an interstitial pop-up when I click either of these links. It’s one of those Windows Vista popups of which Apple Computer makes so much fun. I’ve updated Adobe software since the last time I ran Family Tree and I think it is the new Adobe software, not the new Family Tree, that is causing this problem:

Windows Vista complains about Adobe DLM

Unfortunately, this popup seems to pull the Family Tree window back to the top, so if you click on the Register link, the registration window is left underneath. It took me several clicks on Register before I noticed the small registration window underneath the Family Tree window.

The News and Updates link opens up (after the Vista popup) a “What’s New in the Family Tree” document. According to this document, there are but two new features in the May 2009 release of Family Tree. Can you guess what they are?

I’ll give you a hint.

I just covered them.

Next week we’ll scour product help for any additional public information about these latest releases of New FamilySearch and Family Tree. Stay tuned…