Showing posts with label FTM2017Hints. Show all posts
Showing posts with label FTM2017Hints. Show all posts

Friday, August 2, 2019

Social Security Death Index - Warning

As some of you know, I work off of Ancestry RECORD Hints, and find this works very well for me. I then will use the Web Merge feature of Family Tree Maker to get that data from the website, into my database. The REASON I do this is so that my database contains the exact information from that Record. Misspelling and all. When the Data is in my database, then I evaluate the information presented and mark the appropriate Fact as Preferred. Keep in mind, that I have already evaluated the Hint BEFORE I do the Web Merge, to make sure it is my person. This 2nd evaluation is to match this new information against the other information I already have.

Now, the reason for this blog post is to bring to your attention a problem that I have seen in a number of Records, but I will focus on ONE Record Group, the Social Security Death Index (SSDI) from Ancestry.

The issue: The Death Fact information.

I have seen this problem during the Web Merge of an SSDI Record, many times and have reported this as a Bug to Family Tree Maker. But, I wanted to see why the Web Merge was acting the way it was. The Root Cause of the problem (yes, I'll tell you in a minute), is the way that Ancestry handles this Record.

Here is a Hint, in my Ancestry Member Tree (AMT), for an Individual, for a SSDI Record:


This is a Quick Compare, in the AMT, with My information on the Right and the Record information on the Left. I only have the Year of the persons Death. The Record, in this Hint, had the Month and Date (all good) of the Death BUT is has a Death Location.

If I were to just accept that Hint, the Death Location would be Added to that Death Fact.

Here is the Issue:

If you Look at the RECORD, the Record has the Month and Year but NO Death Location. In this example, there is a Last Residence Fact, which is good, it includes the city, county, state, and Zip code. All good. BUT there is NO Death Location on that Record.

What information does the SSDI contain?

The SSDI contains the following information fields:ty number
Surname
Given Name
Date of Death
Date of Birth
Last Known Residence
Location of Last Benefit
Date and Place of Issuance
Note: the Date of Birth, nor the Date of Death items do NOT include the Location / Place. And, in the Web Merge, online or in Family Tree Maker, the Birth PLACE is not included. Only the Death Place (example in a minute)

My understand of the Last Know Residence and the Location of Last Benefit, is the last place someone lived, according to Social Security and where the Last Benefit was sent. Neither of them are noting the Place of Death.

In the Web Merge, in Family Tree Maker, as it the AMT Save Hint we see:


I will NOT accept that Place Name for the Death Fact, I must manually delete the Death Fact PLACE for an SSDI.

I caught this issue a while ago, but chose now to blog about it, when the SSDI claimed that my Grandfather Died in New Jersey. He did not, but the Last Benefit was sent to New Jersey.

My mothers SSDI claimed her last residence correctly, but the Last Benefit was sent to the same Place Name, but a different Zip Code. In this specific case, and the  reason why I enter those other Fact Names into my database, (deleting the Place of Death) is that it gave me a clue as to why my mother's estate did not include any Social Security benefits. It must have been sent to the Long Term Care facility, as part of their Contact. It IS useful information.

It is my opinion, that this is a BUG for Ancestry.com to resolve as well as Family Tree Maker to resolve.

IF the RECORD does NOT Contain the Place of Death, it should NOT be included in the AMT Merge, nor the Family Tree Maker Web Merge Feature.

____________________________________________________________
Copyright © 2019 by Cousin Russ

Monday, December 24, 2018

Tuesday, January 9, 2018

Which Hint Do You Merge

With the change in the Hinting system between Ancestry and Family Tree Maker, a little more care needs to be taken, when selecting a Hint that has a media file. I'll share my experience with this.

_______________________________________________________________
Copyright © 2018 by H R Worthington

Sunday, January 7, 2018

New Hinting System Observation

An observation on Hints in FTM2017 and the New Ancestry interface to Family Tree Maker




_______________________________________________________________
Copyright © 2018 by H R Worthington

Monday, January 1, 2018

Why I Use 5 Underscores for Unknown Names

Why, to get hints. Hopefully, will demonstrate that here.



_______________________________________________________________
Copyright © 2017 by H R Worthington

Wednesday, December 27, 2017

Doing a Web Merge from a Find A Grave Index Hint

My process for following a Hint from the Find A Grave Index collection from Ancestry


_______________________________________________________________
Copyright © 2017 by H R Worthington

Monday, December 25, 2017

Observation when doing a Web Merge on a Find A Grave INDEX Hint for Two People

An observation about Hints, when Two People have hints and One Person is selected, but the Web Merge includes two people. In this example, I had already merged the data from the Wife into FTM2017 from her Hint, so, his hint should no longer be there, as all of the information from that record is already in that database.





I will probably do this example again, to show the Hint issue. The point of this one, is to show that the Hint was followed for one person, the Husband, but the data from the Wife was included in the Web Merge. And that Hint should not have been there.to start with.
_______________________________________________________________
Copyright © 2017 by H R Worthington

Thursday, December 21, 2017

Observation when doing a Web Merge on an SSDI Record

Just some observations when doing a Web Merge, with FTM2017, with a Social Security Death Index (SSDI) Record. Specifically the Death Location fact, creating / using a Last Residence Fact, a State Issued Fact, and the use of the SSN.




_______________________________________________________________
Copyright © 2017 by H R Worthington

Tuesday, November 14, 2017

How to Un-Ignore a Shaky Leaf Hint for FTM2017?

After I posted the How to Ignore a hint in FTM2017, and was successful, I really did NOT what to ignore that hint. I spent some time trying to determine how to do this, and here is my result.



I will continue to look for a better answer, and I have provided Feedback to Family Tree Maker on this problem.
_______________________________________________________________
Copyright © 2017 by H R Worthington

Sunday, November 12, 2017

Why doesn't the IGNORE button Work ?

In response to a user report problem about the Ignore Button in FTM2017, Web Search Workspace. I'll try to explain how it works.


The IGNORE button is for Hints, not search results

_______________________________________________________________
Copyright © 2017 by H R Worthington

Tuesday, July 25, 2017

FTM2017 - No Hints from Ancestry

Just purchased or upgrade to FTM2017 and the People Workspace, Tree View has no Hints.



Simple answer, go to the Plan Workspace and Check the Sync Status:



The answer: You must have an Ancestry Member Tree (AMT) to receive Hints. Those AMTs are what provides us with the hints.

Upload and Line to Ancestry is the Answer. Be sure to check the settings of the Ancestry Member Tree as you upload and sync.

  • Public
  • Private
  • Private, not searchable by Ancestry
Are the options.

_______________________________________________________________
Copyright © 2017 by H R Worthington

Print Friendly