Showing posts with label Genealogy. Show all posts
Showing posts with label Genealogy. Show all posts

Thursday, March 7, 2013

The Ultimate Family Tree



307506_stock-photo-triple-generation-family-tree


Recently +Dick Eastman reported that Family Tree by familysearch.org is now live and available to all users.

As you likely know, FamilySearch is a free website that is packed full of genealogical information. Now they offer us something new.

Usher in the Family Tree. Previously only available to members of the LDS Church, this project will result in one tree – for free! Any given person should only be found on the tree once (ideally, where they belong).

After taking a look at the Family Tree, it is clear that this is going to be an enormous undertaking. At this time there is no way to upload data to the Tree – all information must be input manually. But the interface isn’t complicated – it’s simply a matter of inputting the vital information of your ancestor; a quick search is then performed to see if they already exist; if they do, you select them, if not you add them – and presto! There you have it. A search can then be conducted to check for duplicates, which are reviewed and merged by the user.

The one thing that does concern me is a seemingly utter lack of control. Anyone can manipulate and change the data. There is an option to view a history of changes, so the information is still there. There’s also a place to cite sources, but those can easily be deleted as well.

Take, for example, the case of my great great grandfather, Jonathan Russ. He died in 1863 at Fort Delaware after being taken prisoner at the Battle of Gettysburg. This has been verified by the Veteran’s Administration and the National Cemetery Administration; there was only one Confederate soldier matching his statistics. The 1870 census shows his wife as having five children – two of whom were born after his death. So, his death date on Family Tree has been set to a date that would fit with these births – even though the evidence is clearly indicates otherwise. Will sources be enough for someone who doesn't want to believe them?

With no control, will this situation be what we can expect? Only time will tell. A unified family tree certainly seems to be a lofty goal – but it’s likely one that the LDS, with their years of experience – can reach.

FamilySearch.org is owned and operated by the Church of Jesus Christ of Latter Day Saints.

Thursday, January 31, 2013

So much to learn

I spent the better part of the day planning and thinking how to handle a project I am working on. It really made me realize how much I have to learn.

But! I am determined. I registered for a class on brick walls with Family Tree University. It’s a power course. I’m in dire need of ideas!

Off to read!

Family Tree University is a part of the +Family Tree Magazine family

Wednesday, January 30, 2013

Volunteer Genealogy


I just finished another pro bono report for a client. He told me, “You have done more than what you've agreed. This is great.”

There is something very rewarding about helping someone resolve a problem they have been struggling with for so long.

While I wasn’t able to draw any decisive conclusions (courthouse fires – Ugh!), I certainly believe I was able analyze what data is currently available and draw a reasonable, well thought out conclusion as to the most likely parentage for this particular gentleman. I was also able to locate some records that they hadn’t seen before, and make recommendations as to other avenues of research they might consider.

Of course, with each of the pro bono cases I have worked on I have found myself so engaged in the project that I went beyond the allotted time. Well, it’s good practice, good customer service, and quite frankly – enjoyable!

Have you ever found yourself so caught up on in someone else’s work that you forgot your own?

Monday, January 28, 2013

Working today

Today was a day of work.

I a bit of did pro bono work for a client. Both the surname and given name were extremely common and made for a lot of digging and a lot of throwing away. Eventually, though, I was able to pinpoint the right family, and I believe I have given them enough information to further their search for a while.

I've decided that there never will be one perfect genealogy software, as much as I would like there to be. I've tried Legacy 7.5, MyHeritage Family Tree Builder (definitely a winner in the free category), MagiKey and their census tracker (too complicated in the end), and RootsMagic, which I have been actively using. They each have features I wish the others had.

So, I tried out something new today. It's called Evidentia. It's not a database, however - its job it to provide you a place to gather, catalog, and analyze data from any given document. It provides a framework to help ensure compliance with the Genealogical Proof Standard (GPS).

There's a 30 day free trial so I'll post my thoughts on it after the end of the Family History Writing Challenge.

Sunday, January 27, 2013

Ancestry.com source citations

In the genealogical community there's a bit of a saying - if it isn't documented then it didn't happen.

+Ancestry.com is a wonderful and amazing resource that allows family historians to not only research their ancestry but share their work with others. Unfortunately, all too often the work is incorrectly cited, if it provides any sources at all. Therefore many professional researchers will often ignore this information altogether.

In my work, however, I have decided not to ignore this information. Just because I can't verify it doesn't mean it's not correct, and I feel I would be doing my clients a disservice by not sharing all data I have found, no matter the source. The caveat here is that I cite this information extremely well, and reiterate to the client that I found no supporting documentation for the claim.

Do you share undocumented work with your clients as a way to offer them clues for future work? Or do you ignore this work entirely, opting to use only information you were able to locate records for yourself?

If you do use it in a report, how do you cite it?