Thursday, September 29, 2016

Find A Grave Global Cemetery Meetups Planned

Find A Grave global cemetery meetupsAs they did last year, Ancestry is organizing Find A Grave cemetery meetups this year, for 7-9 October 2016. Attend one of the locations already on the calendar, or organize your own at a local cemetery that needs photographs. As I write this, the map already shows 119 events at cemeteries in the United States, 13 in Europe, 8 in Australia/New Zealand, and one in Manila. (I wonder if anyone has organized one for the cemetery at Haunted Mansion, Disneyland? Sign me up!)

Don’t forget that after Ancestry.com bought Find A Grave, they created an iPhone app. Ancestry has prepared a PDF download with tips on finding your ancestors’ cemeteries.

For connecting via social media, use the hashtag #FGDay. For more information, visit http://www.ancestry.com/cs/find-a-grave-community-day.

Tuesday, September 27, 2016

Ancestry Insider is a #RootsTech Ambassador

RootsTech 2017 is February 8-11, 2017 in Salt Lake City, Utah.

I’m pleased to accept the invitation to be a RootsTech 2017 Ambassador.

Registration is now open for RootsTech 2017. According to the message from RootsTech:

Registration is now open for RootsTech, the world’s largest genealogy and technology conference in the world. Happening February 8–11, 2017, at the Salt Palace Convention Center in Salt Lake City, Utah, RootsTech 2017 will empower you to celebrate your family across generations using the newest technologies available.

For a limited time, the full RootsTech conference pass is available at a discounted price of $159. Regularly priced at $269, that’s over $100 in savings!

The Ancestry Insider is a RootsTech 2017 ambassador.The RootsTech session schedule is available to help you make your decision regarding attendance. There are over 200 choices. Unfortunately, RootsTech hasn’t yet released the lineup of keynote speakers. They tend to space those announcements out. I’m not certain if it is because they are still arranging speakers or if they do it just to get more press coverage. My experience is that people tune you out when you do that. I’ll try to wait and combine two or three announcements together so you don’t start tuning them out. In that spirit:

Registration is also open for the Innovator Summit and Family Discover Day. All combined, the three conferences, last year had 28,000 attendees.

Family Discover Day is for members of The Church of Jesus Christ of Latter-day Saints. It takes place on Saturday, 11 February  2017. It is free but registration is required. It includes talks from Church leaders; classes for families, youth, and young single adults; and evening entertainment. Event details, including speakers and classes, will be made available soon.

Innovator Summit is a one day conference designed for entrepreneurs and software developers. Associated with the summit is the Innovator Showdown, a contest to see who can come up with the best app or device that solves a real world family history industry need, or uses family history data or services to solve a need in another industry. The showdown awards $100,000 in cash and prizes. The submission deadline is 1 December 2016. The winners will present onstage and be selected by judges and live audience voting at RootsTech 2017 on Friday, 10 February 2017. Go to RootsTech.devpost.com for more information.

Thursday, September 22, 2016

Linda K. Gulbrandsen and FamilySearch Partners – #BYUFHGC

Linda Gulbrandsen addresses the 2016 BYU Conference on Family History and GenealogyThis article will be of interest mostly to members of The Church of Jesus Christ of Latter-day Saints.

Linda K. Gulbrandsen of FamilySearch gave a presentation titled “New Possibilities with FamilySearch Partners” at the recent 2016 BYU Conference on Family History and Genealogy. She is an executive account manager for FamilySearch in the Partner Services Division.

“Partners are very important to us,” Linda said. She talked about how consultants could use tools from FamilySearch partners to help get Church members interested in family history and temple work. She referenced Mike Sandberg’s talk at RootsTech 2016 (see “Begin at the Beginning: Helping Others to Love Family History”) and showed how his approach can be augmented with the inclusion of partner offerings.

The question arises as to when to introduce partner offerings. That depends, she said. Perhaps the person or family needs to start right into FamilySearch.org. For others, the proper approach may be different. In some cases, the consultant may wish to use the app prior to visiting the member. The app gallery (at FamilySearch.org/apps) has over 120 apps for desktop, mobile, and web. Any of these may be helpful.

Linda presented several scenarios, each with an applicable partner app. For a family with young children, she showed Little Family Tree. For other scenarios she showed Relative Finder, MooseRoots, and Hope Chest.

“We have these partner tools that can be helpful in so many ways,” Linda said.

Wednesday, September 21, 2016

John Huff and FamilySearch Family Tree – #BYUFHGC

John Huff at the BYU Conference on Family History and GenealogyJohn Huff of FamilySearch gave a presentation titled “Making Data Decisions in Family Tree” at the recent 2016 BYU Conference on Family History and Genealogy.

The goals and principles behind New FamilySearch (NFS) were to improve the accuracy, quality, and pace of genealogy work; to reduce duplication of data and effort; to preserve all contributions; to allow only the contributor to change their information; and to encourage addition of sources.

What ended up happening was frustration over duplicates that couldn’t be combined, confusion over using the system, continuation of the “mine” versus “ours” mindset, limits on what could be fixed, collaboration difficulties, and problems introduced by centralized, automated changes.

There were data issues. Some of the records came from Ancestral File and the merge algorithms used back in its time had “splinched” persons [think “Frankenstein monsters”]. There was overwhelming duplication which led to IOUSes (individuals of unusual size). These were terrible for the system. [You may recall when NFS was deployed in Arizona the IOUSes caused the system to continually crash.]

Combines caused problems. There was no attribution for who did the combine. It was much easier to combine than to separate. [I think it could take 10 hours to undo a bad 10 second combine.] Combining multiple persons into one created merge magnets that attracted further combines. FamilySearch found one with more than 50 persons combined together.

FamilySearch had to sit down and decide what to do. They decided to change some of the goals and mindset. The principles of Family Tree are similar to NFS, but FamilySearch really wants sources. And rather than keep every alternative value for an event, they would keep only one conclusion. They would provide better tools for the community to provide evidence and clean up the data. They would allow errors to be fixed and bad changes to be fixed as easily as it was to introduce them. They wanted to provide attribution of changes and impede bad ones.

To build a better tree, you need to act as a community. Be courteous, kind, cheerful, and patient. Be respectful of others. Leave things in a better state than you found them. Communicate and collaborate. Add an email and make it visible. Use the messaging system. If contributors won’t respond to messages, after making efforts to contact them, go ahead and make changes—based on evidence.

Only make changes that you know. Knowing means the best conclusion of the community. If you don’t know something, don’t add, edit, or delete. [I would add to that, if you don’t have evidence and proof.] Before making changes, review the reason statements, sources, discussions, notes, and memories. Contact contributors. Don’t mark persons as dead unless you know they are dead. Don’t add persons you aren’t sure existed. Put them in a personal tree. Keep notes of relevant person IDs when making merges; have the end in mind before starting the merge.

If you want to help people not make changes to your stuff, the best defense is a good offense. Provide good reason statements. There is a great article: “Reason statements for adding, editing, and deleting information” in the FamilySearch Help Center. [I half-way disagree with John’s appraisal. The first half is great. The second half is a great collection of unhelpful reason statements “I attached this birth certificate because it provides evidence about his birth.” As an alternative, I would direct you to a similar article in the wiki: “How to Write Effective "Reason" Statement in the FamilySearch Family Tree.” Or see this article in the FamilySearch blog: “Tips and Tricks: Writing a Good Reason Statement for Changing a Record.” But I digress…]

Search records, including partner websites. FamilySearch provides hints. They work very hard to make the hints good. John thought the accuracy to be about 99%.

Use the watch list. You can filter your watch list by name or ID or location. Search for “DEL” to see all the deletions. You can sort in all sorts of ways. The watch list can also show the changes that were made, including hiding those made by yourself. You can filter to those made by a particular user. You can filter by anything on the page because it actually does a word search.

Use the Possible Duplicates feature. If you indicate a person is not a match, Family Tree will no longer show it as a possibility, but it can be seen under the Not a Match link. Use Dismiss Suggestions and Dismiss Problems. If you see exact duplicate conclusions (such as alternate name), delete all but one.

FamilySearch doesn’t yet have a good answer for how to solve edit wars. They are going to come up with a solution, but there are other things that must be done first. If someone gets abusive, contact support. If you desire to change a read-only person, contact support and request a change. If you find living persons marked deceased, contact support to fix it.

We are working on a way to allow you to share a group of private persons, John said.

It is rare that you need to delete persons. Delete only those who truly never existed. [You can delete persons you create that haven’t been changed by others. Otherwise, contact support.] If you find a person wrongly deleted, it can be found in the change history of the surviving record or if you have the ID.

Deleting relationships is the secret weapon to fixing up family messes. Delete relationships instead of persons. Clean up after yourself. Don’t orphan the persons or they’ll never show up again.

There are a set of cases where you can’t merge. The most common are persons with unknown sex, persons who would have too many things like comments, a few IOUSes, or restricted persons, like Read Only persons.

Remember that the only thing that will be available 100 years from now will be the data, not the system.

Tuesday, September 20, 2016

MyHeritage Provides FamilySearch Source Button

Click to view an infographic
Click to view an infographic

FamilySearch announced last week that MyHeritage is providing a button to create a source in FamilySearch’s Family Tree. When viewing a MyHeritage historical record the button is available below the record details.

A single click or tap of the button creates a source in Family Tree. To associate the source with the correct person in Family Tree, you must have initiated the search from the person’s Family Tree page.

Ancestry.com features similar functionality: Attach the record to a person in an Ancestry Member Tree, link that person to a person in FamilySearch Family Tree, and transfer the source. This feature is available only to members of The Church of Jesus Christ of Latter-day Saints.

For more information about the MyHeritage button, see “Family History Easy Button: Create New Sources in Family Tree from MyHeritage” on the FamilySearch blog.