Recently I came across an interesting web site, called Mapire, which displays historical maps of the Hapsburg Empire. The maps currently correspond to three military surveys carried out in the time periods 1763-1787, 1806-1869, and 1869-1887. These periods cover different geopolitical periods, when the areas under control were variously called the Hapsburg Empire, the Austrian Empire, the Austro-Hungarian Empire. The military maps were created at a scale of 1:28,800. What’s really neat about the maps on Mapire, is that they are all synced to current digital maps, so when you zoom in on one of the military maps, it shows on the left side of the window, while the current digital map is shown on the right. An example, for the town of Kańczuga:
Cadastral Maps, another kind of state-created map, were created at a scale of 1:2,880, or ten times the resolution. This site does not yet have Cadastral Maps, although some Cadastral Maps for the Galicia region can be found in the Gesher Galicia Map Room.
One of my earliest posts on this blog was about Find A Grave and how it could be used to help you with your genealogy research.
It’s long bothered me that they had no mobile app that could be used on my cell phone. Certain since BillionGraves launched back in 2011, the lack of a mobile app has been glaring.
Last year Ancestry.com purchased FindAGrave, and people have been wondering what was going to happen to the service. The first big change luckily is a good one, the launch of a mobile app!
The app is focused on searching for cemeteries and graves. It doesn’t yet have any way to manage the memorials you’ve created on FindAGrave.com, or Virtual Cemeteries. One very important feature it has integrated, however, is finding nearby graves that people have requested photos of, allowing you to submit photos through the app.
One thing you might notice in the screenshot above is that it allows you to ‘Add GPS’ to a grave. While Find A Grave has never death with GPS before, it seems they are now moving in BillionGraves’ direction by supporting, at least in a small way, GPS coding of graves.
Do you use Find A Grave? Do you use BillionGraves? Are you planning on downloading this app? Have you already? Share your thoughts on grave-focused sites and apps in the comments below.
Recently I was asked about ordering a copy of an ancestor’s Social Security application. The application, called an SS-5 Form, is usually used for genealogy to get the names of the applicant’s parents. If you don’t know the birth date of a relative, it can also be used for that purpose, although that information is available in the public SSDI databases (and parents names are not).
The SSDI
The Social Security Death Index (SSDI) is a database of deaths recorded by the Social Security Administration. It’s official name is actually the Death Master File (DMF). When published online for genealogy purposes it is referred to as the SSDI. According to FamilySearch, the SSDI includes an increasing percentage of recorded deaths as time goes on from 1962 (when the index started):
The index includes about 50 percent of deceased persons from 1962 to 1971 and about 85 percent of the deceased persons from 1972 to 2005. It also includes a few deaths from 1937 to 1961.
That said, the database itself shows something a bit different. If you search for all deaths in the database from 1937 to 1961, there are 740,152 results. That’s a bit more than ‘a few’. What’s going on here? Even weirder, if you search for records before 1937 (when SS started) there are also records (a bit over 2500). Something is obviously wrong with these records. Keep these imperfections in mind when using the data. If you’re wondering why the percentage increases, it’s because not every working person was registered in the early days of the system. As time went on, more people participated in social security, and thus more people are also recorded in the SSDI.
So assuming your relative is among those recorded in the SSDI, how do you find their record, and assuming you find it, how do you get the record? One thing first…
Restrictions on Usage
You might have read that congress has criticized the online publication of social security numbers and accused online companies that do so of making identity theft easier. I have argued in the past that in fact that is backwards, but putting that aside, some online services have put restrictions on access to SSDI data, such as not showing anyone who died in the past 10 years, etc. Recently a law was passed making it impossible to order SS-5 Forms for anyone who died in the previous 3 years. The law also effects the publication of new deaths to the SSDI, but won’t kick in until March (see this article at the Legal Genealogist for more information on that).
Whether 3 or 10 years, however, that doesn’t affect genealogists at all due to another government policy change. Back in 2011, the Social Security administration changed the access rules, where before you could order a complete SS-5 form for any deceased person born more than 70 years ago, they increased it to anyone born more than 100 years ago. Additionally, if the death of the application cannot be proved, then full records are not available for 120 years after the applicant’s birth.
So it’s currently January 8, 2014. That means if the person is known to be dead (i.e. you have a death certificate, or their death is recorded in the SSDI) then they need to have been born before January 8, 1914 if you’re going to be able to get a full record that shows the applicant’s parent’s names. If they don’t show up in the SSDI and you don’t have a record of their death (but you do have a social security number), then they have to have been born before January 8, 1894 if you want to get the applicant’s parents names.
Don’t Order Records That Won’t Help
Keep in mind one important thing. If the person was born more recently than 100 years ago, you can still order a copy of the SS-5. The Social Security Administration will happily take your money and send you a copy of the record, however, they will block out the names of the parents in the copy they send you (making the record mostly useless for genealogical purposes).
Searching the SSDI
To find a person’s social security number (and at the same time confirm that they are deceased according the Social Security Administration) you can search the SSDI on several sites. One good site is FamilySearch’s SSDI search page. Another public search page is Mocavo’s SSDI Search page. I will say that I believe FamilySearch’s to be the most up-to-date database, and they also post what date the database was updated – as of today it was updated with data up to November 30, 2013 – less than two months ago. Indeed my grandfather who passed away in September is listed in the FamilySearch database, but not in the Mocavo one.
Ordering Records
So let’s say the relative you’re researching was born more than a hundred years ago. You find their Social Security number, either through the SSDI or through other means. How do you order a record? Well that’s actually easy. You just go to the Request for Deceased Individual’s Social Security Record page, pay your $27 and order the record.
Interestingly for two dollars more you can order the record even without the Social Security number. This is odd because searching for the record without the number would seem much more difficult and more costly than $2.
A Final Thought on the Restrictions
As I mentioned, my grandfather passed away in September. If I wanted to order his SS-5 form, according to the 2011 regulations I wouldn’t be able to order his un-redacted SS-5 form until he would have been 100, which in his case is not too far away – he was 98 – so July 2015. However, because of the new law recently passed, I can’t order the SS-5 at all until 3 years have passed, so September 2016. An extra year and a bit. In general, however, the restriction is likely to be on the 100-year regulation.
Everyone now needs to wait 3 years on ordering an SS-5 now, but if a relative passed away at the age of 80, you’d have to wait 20 years before you could get the un-redacted SS-5 form with the name of the relative’s parents on it. If your relative died before 2011 and you had ordered the records before the regulatory change then, you could have ordered the same SS-5 Form immediately, and received it un-redacted (since the relative was over 70).
I see now that the software I use to prevent spammers might have been a little too aggressive in preventing users from commenting on this site. If you’ve had trouble commenting on this site in the past, I’m very sorry. I ask that you please try again, as I’ve tried to adjust the software. If you still have problems, please send me a note either by using the Contact form, or by e-mailing me at [email protected]. Hopefully this will not be a problem in the future.
Ancestry.com has released the third version of their Family Tree Maker (FTM) application for the Mac (yes there was an older version a decade or so ago, but I’m ignoring that). The first version was released in 2010, and in fact was the subject of the very first post on this blog. It was actually the subject of several posts, as I tested it out to see if it made sense to switch from using Reunion to FTM Mac. In the end I decided against switching, due to several reasons. The most important reason was simply that he software seemed a little too buggy at the time.
Another issue which bothered me, which seems minor, was that you could not take a single photo and use it to create multiple head shots to represent many different people in your tree. For example, if you have a single family portrait representing a branch of your tree that has ten individuals in it, in Reunion you could add the same photo to all ten people’s records, and then crop it to show just the individual you want. In fact, you could add the same photo twice to a record, and crop it differently each time. This is useful if you want to put in a full photograph with background as part of that person’s multimedia record, but want a simple cropped headshot for the person when showing them in a tree, for example.
One thing that bothered many Mac users with the initial version, was that it wasn’t based on the then current Windows version (FTM 2011) but on an older version (FTM 2010). Even then, the features of FTM for Mac were not on par with FTM 2010 for Windows. There was a time when this kind of thing was common for Mac users, but it’s fairly rare nowadays. To add insult to injury, Ancestry charged more for the Mac version with less features than the Windows version.
The second version of FTM for Mac was released in 2011. It brought one major feature with it, TreeSync, which allows you to sync your tree in FTM with a tree on Ancestry.com. A pretty big feature. It always makes me wonder when they release minor updates or even major updates like the new version 3, however, that they always add ‘Improved TreeSync’ as a feature of the update. Clearly there were some problems with the implementation of TreeSync in FTM for Mac 2. FTM for Mac 2 kind of felt like FTM for Mac 1 was a beta version, and this was the real version 1. It was better, but still not up to par with the Windows version, and still more expensive.
Now FTM for Mac 3 has been released. The big differences are not in the features it seems. The big difference is in the beginning of treating Mac users on a more equal footing with Windows users. For the first time, the price of FTM for Mac is the same as the Windows version – $39.99 (currently on sale for $29.99). Also for the first time, FTM for Mac shares the same file format as the current Windows version. That is the most significant change to me. Now people on Mac and Windows can exchange their full data files without having to do any kind of conversion (earlier version came with a Windows application for converting the Windows files – but if you had the Windows file already and you were on a Mac – no luck) or by using GEDCOM. This version is still not at feature parity to the current Windows version (FTM 2014) but at least it seems like they’re setting the groundwork for that in the future.
One test I tried with this new version was to try to import a FTM 2012 Windows file. Oddly it started the import process, but then quit in the middle and said the file wasn’t supported. This brought back memories of past experiences with the older version where the error messages seemed bizarre. Why should it even try to import the file if it’s not compatible? Why it wouldn’t do a version check before doing the import is beyond me.
Although the file formats are now the same, it seem FTM Mac 3 still cannot import older files from Windows. I think it actually might be able to import really old FTM for Windows files (up to version 16 from 2008), but none from the more recent generation of the software.
My next test will be to see if I can sync a tree from a cousin who uses FTM on Windows through Ancestry.com. It’s unlikely I will switch from Reunion to FTM for Mac 3, especially with my pet-feature of cropping multiple faces out of a single photo still missing, but I am looking forward to trying to collaborate with my cousin through TreeSync. We’ll see how that goes…
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.